|
![](/i/fill.gif) |
>>> Ah, so your /real/ problem is a crappy text editor.
>>
>> The /real/ problem is that there is no way of knowing what encoding a
>> given text file has. So it's not safe to use non-ASCII characters in a
>> text file. Which is why character entities were invented in the first
>> place...
>
> Use an editor that places a BOM at the start of UFT-8 files and bob's
> your uncle.
In other words, "there is this informal undocumented /convention/ that
if a file starts with a BOM [even though UTF-8 does not require such a
mark, since there /is/ no byte order], then it is presumed to contain
UTF-8".
I wonder how widely implemented this undocumented feature is?
Post a reply to this message
|
![](/i/fill.gif) |