文件(夹)名避免使用的字符 Characters to Avoid in Directories and Filenames

Characters to Avoid in Directories and Filenames

Your web files will be viewed by numerous users who use a wide variety of operating systems (Mac, PC, and Linux for instance) and devices (desktops, tablets, and smartphones are some examples). Therefore, it is essential to play it safe and avoid common illegal directory and filename characters.

Naming conventions are important in web folders as well as for downloadable files such as PDFS, Word documents, and Excel spreadsheets.

Do not use any of these common illegal characters/symbols:

# pound	< left angle bracket	$ dollar sign	+ plus sign
% percent	> right angle bracket	! exclamation point	` backtick
& ampersand	* asterisk	‘ single quotes	| pipe
{ left bracket	? question mark	“ double quotes	= equal sign
} right bracket	/ forward slash	: colon
\ back slash	blank spaces	@ at sign

Also, keep these rules in mind.

• Don’t start or end your filename with a space, period, hyphen, or underline.
• Keep your filenames to a reasonable length and be sure they are under 31 characters.
• Most operating systems are case sensitive; always use lowercase.
• Avoid using spaces and underscores; use a hyphen instead.

what-characters-are-safe-in-cross-platform-file-names-for-linux-windows-and-os

Windows: anything except ASCII's control characters and \/:*?"<>|
Linux, OS-X: anything except null or /

On all platforms it is best to avoid non-printable characters such as the ASCII control-characters.

Windows

In Windows, Windows Explorer does not allow control-characters or \/:*?"<>| You can use spaces. If you use spaces, you will often have to quote the filename when used from the command line (but GUI apps are unaffected so far as I know). Windows filesystem such as NTFS apparently store the encoding with the filename, but UTF-16 is standard.

Linux, OS-X

In Linux and OS-X only / of the printable ASCII set is prohibited I believe. Some characters (shell metacharacters like*?!) will cause problems in command lines and will require the filename to be appropriately quoted or escaped.

Linux filesystems such as ext2, ext3 are character-set agnostic (I think they just treat it more or less as a byte stream - only nulls and/ are prohibited). This means you can store filenames in UTF-8 encoding. I believe it is up to the shell or other application to know what encoding to use to properly convert the filename for display or processing.

Conclusion

So you could probably safely use something like ✣ (if it weren't so hard to type)

过滤windows文件名非法字符
windows现在已知的文件名非法字符有 \ / : * ? " < > |

	private static Pattern FilePattern = Pattern.compile("[\\\\/:*?\"<>|]");
	public static String filenameFilter(String str) {
		return str==null?null:FilePattern.matcher(str).replaceAll("");
	}