> On Tue, Jan 04, 2005 at 20:29:00 -0500, Mikhail Teterin wrote:
> > I was just hit by this problem trying to compiled OOo-1.1.4 against the
> > latest expat-1.95.8.
> >
> > http://www.openoffice.org/issues/show_bug.cgi?id=37309
> > http://www.openoffice.org/issues/show_bug.cgi?id=36860
> >
> > The best fix for it, in my opinion, is not to re-encode the file in UTF8
> > as the bug's summary seems to suggest, but change the encoding attribute
> > of the file:
> > --- i18npool/source/localedata/data/gl_ES.xml Fri Aug 27 06:24:18 2004
> > +++ i18npool/source/localedata/data/gl_ES.xml Tue Jan 4 19:48:27 2005
> > @@ -1,3 +1,3 @@
> > -<?xml version="1.0" encoding="UTF-8"?>
> > +<?xml version="1.0" encoding="iso-8859-1"?>
> > <!DOCTYPE Locale SYSTEM 'locale.dtd'>
> > <Locale version="1.2">
> >
> > Unless the same file has to incompatible 8-bit encodings, there is no
> > need to use UTF -- it only makes the file harder to read for people and
> > for computers.
>
> For people it may be true in this case, for computers it shouldn't make
> no difference. Additionally, one may always run a recode on the file for
> human reading/editing. We keep all files in UTF-8 encoding, so handling
> is identical for all locales.
So, the same for computers, but harder for people. Sounds like my way is
better. UTF-8 only makes sense, when charsets need to be mixed -- not in this
case.
The uniformity here is hardly advantageous -- these files are, by their very
nature, maintained by different people, who will certainly be using older
software for the next few years and should not be gratuitiously required to
install recoders. The newer software will have no problems my way or yours.
I urge you to reconsider.
Yours,
-mi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]