| Date: Sat, 17 Feb 2007 18:12:58 +0100
| From: Brian Foster <blf at blf.utvinternet.ie>
|[ ... ]
| I concur with Kae's point here: Until you can simply
| cat(1) the file and see what you _should_ see, things
| are not set up correctly. [ ... ]
apologies, that isn't quite what I meant to say:
if the files in question are UTF-16, then on a
typical Linux system (often UTF-8 nowadays), the
above check clearly “won't work”. the above test
is best applied when the terminal's encoding is
compatible (read: identical unless you know what
you are doing) with the file's.
however, as Kae has pointed out, vim(1) at least
should be able to deal with the situation even if
the files are, as I (now) suspect, UTF-16LE (esp.
if you are using a UTF-8 terminal window).
Experienced (>25 yrs) kernel/software Eng: | Brian Foster Montpellier,
• Unix, embedded, &tc; • Linux; • doc; | blf at utvinternet.ie FRANCE
• IDL, automated testing, process, &tc. | Stop E$$o (ExxonMobile)!
Résumé (CV) http://www.blf.utvinternet.ie | http://www.stopesso.com
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!