Geek Answers Handbook

How to "force" an ISO-8859-1ness file?

I remember when I used a website in Japan - where there are three different character encodings in the currency, the developers had a trick to "enforce" the source file so that it always opens in their IDE in the correct encoding.

What they did was put a comment at the top of the file containing the Japanese character, which existed only in this particular character encoding - it was not in any of the others! This worked great.

I remember this because now I have a similar, albeit English-speaking, problem.

I have files that MUST be ISO-8859-1, but continue to open in my editor (Bluefish 1.0.7 on Linux) as UTF-8. This is usually not a problem EXCEPT for the pound (£) characters and something else. Don't get me wrong, I can fix the file and save it again as ISO-8859-1, but I want it to always open as ISO-8859-1 in my editor.

So, are there any hacky characters, as I mentioned above, for this? Or any other methods?

PS. Unicode supporters / evangelists should not waste time turning me because I am already one of them! This is an early system that I inherited: - (

SFC. Please do not say “use another editor”, because I am an old fart and install in my own way :-)

+5
2

, £, ISO-8859-1 (.. 0xA3), UTF-8, , , UTF-8. ( , £ .)

, UTF-8; , £. , " " - ! , , £ , ASCII, UTF-8, £, UTF-8, , £ , .

, , ISO-8859-1 , . , UTF-8 Shift-JIS, , , .

Windows, , , , 1252 . ( , ISO-8859-1, .)

, , , . vim:

# vim: set fileencoding=iso-8859-1 :

/. . , , ...

, ISO-8859-1, , UTF-8, , .: -)

+3

ÿ (0xFF) . UTF8. BBEdit Mac ISO-8859-1. , .

0

More articles:


All Articles