Fix fr_FR accounts

[Didier Vidal]

[...]
> 
> I believe this is the wrong approach.  In g2 we should be shipping utf-8
> encoded versions of these account trees, not older iso-8859-x encodings
> that require converting upon each use.
> 
> David

I don't understand your concern, David.
Converting will not have to be done by Gnucash developers. It's handled
by libxml2. You cane safely assume that all strings inside gnucash are
utf8.
Shipping an XML file with an arbitrary encoding is perfectly OK as long
as the encoding is specified in the header.

Some could fine more aesthetic to ship only utf8 XML and translation
files. I don't understand the rationale. Shipping arbitrary encodings
proves and tests that gnucash is a good citizen in the internationalized
applications world and supports any locale. It will require a number of
years more before all the systems and files have transitioned to utf8,
and that the encoding mess can be forgotten.

libxml contains also a number of converters, and is even not dependent
on the glibc install for most frequent encoding systems.

Didier.
> 
>