As far as I could tell, everything was working well. In Ubuntu, looking
at an ISO8859-1 encoded file with less when LANG=fr_FR.UTF-8 gives
signs instead of e acute, whereas looking at an UTF-8 encoded file shows
the e acute. So I could check that the iconv step had done what was
expected.
Af
Thanks a lot!
I'll try it.
Regards.
--
José Carlos Carrión Plaza
El 01/07/18 a las 10:34, Edmond Orignac escribió:
To convert an existing ISO8859-1 message catalogue to UTF-8, the
procedure (using fr_FR as example) is as follows.
1) create a directory fr_FR.UTF-8 and the subdirectories
ap
So, did everything work pretty well after this conversion? What about
fonts/font.aliases? I would think those would need to be changed to use
iso10646 fonts, right?
-jon
On 07/01/2018 02:34 AM, Edmond Orignac wrote:
To convert an existing ISO8859-1 message catalogue to UTF-8, the
procedure
To convert an existing ISO8859-1 message catalogue to UTF-8, the
procedure (using fr_FR as example) is as follows.
1) create a directory fr_FR.UTF-8 and the subdirectories
app-defaults backdrops config dtsr msg palettes types
2) copy the messages in ISO-8859-1 under the fr_FR.UTF8/msg d
