El dom, 05-05-2013 a las 13:49 +0100, Rupert Swarbrick escribi?:
> Rupert Swarbrick <rswarbrick at gmail.com> writes:
> > Robert Dodier <robert.dodier at gmail.com> writes:
> >> On 2013-05-04, Raymond Toy <toy.raymond at gmail.com> wrote:
> >>
> >>> But sbcl (1.0.49) prints ?? for "?". Same results for when I use
> >>> LANG=es_ES:UTF-8.
> >>
> >> Shouldn't that be es_ES.UTF-8 ? (Period instead of colon.)
> >
> > Yep, probably. Either way, I think this should probably be fixed in the
> > current parse-info branch. Basically, it just seems we weren't
> > transcoding the .info files correctly. Not entirely sure why it failed
> > but, since we were rebuilding the .info files anyway, I changed things
> > so that we copied across the .texi files, transcoding as we went.
>
> Huh, it turns out that I was being dense. The doc/info/es/Bugs.es.texi
> file had been saved in utf-8 format rather than latin1, which
> (unsurprisingly) lead to breakage. Fixed now.
>
> Rupert
Thanks Rupert, Ray and Robert for your efforts on localization.
I'd like to help with a minimal contribution to this thread.
As far as I know, and if I am not mistaken, both latin1 and utf-8 use
the same character encoding for non special characters. I think that it
doesn't matter if files are saved in any of these encodings as long as
you don't use special characters. In fact, time ago we had some files in
info/es saved in latin1 while others were in utf-8. Now, all of them are
saved in utf-8.
The error reported above is due to a typo when writing the word
'par?metros', it should be 'par@'ametros'. For the same reason, the
German word 'Teilausdr?cke' should be fixed as 'Teilausdr@"ucke'.
Sometimes we forget that we are writing a texinfo document.
I am not an expert in character encoding, but I suspect that using only
non special characters is safer, at least for european languages.
--
Mario