The default would normally depend on the character content of the file, ranging from ASCII for basic English to Windows Latin-1 (Win 1252) or ISO Latin -1 (ISO 8859-1) to UTF-8 for other content.
Can someone please tell me what it is?Īpps like TextEdit and Mail have settings that let you determine the encoding of text produced. But surely this can be controlled independently? There must be a system configuration value somewhere that specifies file encoding default. In other locales that are not English-based, I believe the default file encoding is UTF-8. (I know, I've tested this by changing the file encoding manually and having it overwritten again by the plugin: works correctly.)Īs a simple example, just `touch somefile` from terminal creates a file in Cp1252 - I'm obtaining that info by opening in jEdit by the way (anyone know of something better?). I don't want to be restricted to only ASCII by default, and it is causing me problems with certain software (a Firefox plugin) that creates text files, passing in UTF-8 encoded content, which is then mangled because the file encoding itself is still Cp1252. The file itself, not the characters written to it. That is, the FILE encoding in the file metadata - the Byte Order Mark I believe. However, as I believe is expected, OS X (and Windows for that matter) will create files by default with character encoding of Cp1252 (Latin-1). My language and locale are set to Australian English. This is driving me nuts, on both my Windows box and Snow Leopard I figure much more chance of finding the answer for OS X.
0 kommentar(er)
