5 ms·
"Optional (but recommended) UTF-8 BOM." Why? Everyone else I've seen is not recommending the BOM and trying to get rid of them. They cause issues in various sy
by Ndymium 5y ago
"Optional (but recommended) UTF-8 BOM."
Why? Everyone else I've seen is not recommending the BOM and trying to get rid of them. They cause issues in various systems and you could just infer UTF-8 from the file extension.
- pfusik 5y agoThere are still many Windows programs that default to current Code Page instead of UTF-8. I prefer to have the encoding explicit in the file contents rather than rely on some external file type configuration. This is just a loose recommendation, cito does accept files without the BOM.
- tialaramex 5y agoBut are these "many Windows programs" appropriate ways to edit code in Ć ? It seems to me that if you say Ć program text is UTF-8 then that is an explicit encoding, and that if you feel it isn't explicit enough, an actual way to write out the encoding unambiguously is needed instead, which a BOM doesn't provide. I am a little concerned by the wording "cito does accept files with the BOM". The BOM was chosen because it's a zero-width non-breaking character and so doesn't really mean anything, if cito thinks it means something, that's likely to be a problem elsewhere. For example if I concatenate two related Ć files, that ought to be fine, but I wonder if there's a BOM in the second file its presence in the middle of the concatenated file causes trouble.
- pfusik 5y agoLet's discuss it in https://github.com/pfusik/cito/issues/30 https://github.com/pfusik/cito/issues/30