[ILUG] Editing ISO8859-15 (Windows) encoded text files

[John Honan]

Thanks for all the replies. Just an update on my investigations; I'm fairly
sure now the encoding is CP1252 (Windows-1252) and not ISO8859-15 as I
originally thought.

The leafpad / mousepad text editor detects and saves this codepage intact.
The Kate text editor won't detect the codepage, but does allow me to change
it to CP1252 once I've loaded the file (Under tools/encoding) - Or there's a
command line option; "Kate -e cp1252 myfile.txt" which forces the codepage.

I noticed that any HTML files I've created with windows are encoded using
CP1252, in fact they have a "charset=windows-1252" metatag in the HTML
header section. But I'm starting to feel that UTF8 is a more universal
codepage, and will make the files more portable. I've found a way of
converting CP1252 encoded files to UTF8;

iconv -f windows-1252 -t utf-8 source_file.html -o converted_file.html

Of course, I'd also have to change the HTML header tags to indicate UTF8
encoding. Now I just have to test how UTF8 encoding affects .NET source
files!

2008/7/9 Michael Armbrecht <michael.armbrecht at gmail.com>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> The editor I usually use to fix these kind of issues i jEdit
> (http://jedit.org/). It's written in Java, so many people don't like
> it because it's slow to start up.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: http://getfiregpg.org
>
> iD8DBQFIc/thAFJ1A7kUUhoRAv2gAJ9vxXcpwqYmJgBtbccj6Ls+0Rl7MQCfcbYn
> P0vAd8pp7wjpzeUEDlpCA/k=
> =nN8l
> -----END PGP SIGNATURE-----
>