12:10 p.m.
Hello,
I was admiring the new translation and trying to read it (without really
speaking italian) when I discovered some encoding issues. It looks like UTF8
chars handled by a non utf-ready tool.
After some investigation, it's possible that the corruption comes from the
po file itself. I'm really not sure dudes. I'm such a disaster with encoding
issues, my machine is badly configured and it's even possible that the po
file is clean but my less is broken.
For the web page, I'm rather sure there is an issue.
Mt.
--
Everything should be made as simple as possible but not simpler.
-- Albert Einstein
1:01 p.m.
Alle 19:10, giovedì 12 agosto 2004, Martin Quinson ha scritto:
Hello,
I was admiring the new translation and trying to read it (without really
speaking italian) when I discovered some encoding issues. It looks like
UTF8 chars handled by a non utf-ready tool.
In the Html you can see things such as:
"Perché" instead of "Perché"
After some investigation, it's possible that the corruption comes
from the
po file itself.
[...]
it's even possible that the po file is clean but my less is
broken.
The PO itself is clean. Recode doesn't complain. Try "LANG=C less
<file>" and
you will see that the PO is really UTF-8.
Likely, some tool dealing with manpages expect them to use the ISO-8859-1
charset. I already had a similar experience: one UTF-8 page looked fine when
viewed directly (man ./foo.1), but when insalled and viewed with "man 1 foo"
it showed the same problem.
The files could be recoded to either ISO-8859-1 or ISO-8859-15, but the real
problem lies elsewere.
Cheers,
Danilo
--
Danilo Piazzalunga <danilopiazza(a)libero.it> +--------------------+
GPG Key available at http://pgp.mit.edu | Linux User #245762 |
Fingerprint: D018 815E 8C7F 2AE2 5565 | ICQ #105550412 |
0C36 B5F6 DB20 B800 CB9F +--------------------+
3:29 a.m.
On Thu, 12 Aug 2004, Danilo Piazzalunga wrote:
Alle 19:10, giovedì 12 agosto 2004, Martin Quinson ha scritto:
> Hello,
>
> I was admiring the new translation and trying to read it (without really
> speaking italian) when I discovered some encoding issues. It looks like
> UTF8 chars handled by a non utf-ready tool.
In the Html you can see things such as:
"Perché" instead of "Perché"
Yes, it seems mpod2html assumes that the input document is in iso-8859,
and works with the eyes closed :(
> After some investigation, it's possible that the corruption
comes from the
> po file itself.
[...]
> it's even possible that the po file is clean but my less is broken.
The PO itself is clean. Recode doesn't complain. Try "LANG=C less
<file>" and
you will see that the PO is really UTF-8.
Likely, some tool dealing with manpages expect them to use the ISO-8859-1
charset. I already had a similar experience: one UTF-8 page looked fine when
viewed directly (man ./foo.1), but when insalled and viewed with "man 1 foo"
it showed the same problem.
The man pages also appear with the utf codes. I've tried to install them,
and to open the file directly, and both fail.
The files could be recoded to either ISO-8859-1 or ISO-8859-15, but
the real
problem lies elsewere.
The easiest (and fastest) solution would be (as you say) to recode the po
file to the encoding on which the final documents should be (and mantain
the translation with the recoded po).
But this is a temporal solution. When we have the first non-european
translations this problem will be back.
I think that the real issue is that the programs that deal with the
translated documents don't have encodings support. The binary translation
seems to work well, althought its po is also in utf (gettext rocks ;)
An intermediate solution could be to add an option to po4a-translate to
specify the encoding in which you want the output document to be. This
would be also interesting for the translation of files gettextized with
the po4a script (the generated po could be in utf, since it mixes files
of different formats and maybe different encodings) and you want some
output files in different encodings.
This would be very rudimentary (but necessary?) to specify an output
encoding for each language...
This would also take to a redesign of the po4a config files, since we need
to specify more information there. This could be done together with the
TransTractor redesign explained in the "Future directions" section. Well,
we should leave all this for a future release... but we should begin
thinking about it ;)
Regards,
Jordi Vilalta
4 a.m.
On Fri, 13 Aug 2004, Jordi Vilalta wrote:
On Thu, 12 Aug 2004, Danilo Piazzalunga wrote:
> Alle 19:10, giovedì 12 agosto 2004, Martin Quinson ha scritto:
>> Hello,
>>
>> I was admiring the new translation and trying to read it (without really
>> speaking italian) when I discovered some encoding issues. It looks like
>> UTF8 chars handled by a non utf-ready tool.
>
> In the Html you can see things such as:
> "Perché" instead of "Perché"
Yes, it seems mpod2html assumes that the input document is in iso-8859, and
works with the eyes closed :(
Now I've watched the POD file specification:
http://search.cpan.org/dist/perl/pod/perlpodspec.pod
http://search.cpan.org/dist/perl/pod/perlpod.pod
There seems to be a =encoding command. Maybe this should be added by the
Pod module, taking the result of TT::get_out_charset()
I've tried adding it manually and this is the mpod2html response:
*** ERROR: Unknown command 'encoding' at line 14 in file html/tmp/po4a.7.pod
And here's the pod2man one:
po4a.7.pod:14: Unknown command paragraph "=encoding utf-8"
Is this an unsupported feature or am I doing something wrong? :S
Regards,
Jordi Vilalta
10:46 a.m.
On Fri, Aug 13, 2004 at 11:00:14AM +0200, Jordi Vilalta wrote:
On Fri, 13 Aug 2004, Jordi Vilalta wrote:
http://search.cpan.org/dist/perl/pod/perlpodspec.pod
http://search.cpan.org/dist/perl/pod/perlpod.pod
There seems to be a =encoding command. Maybe this should be added by the
Pod module, taking the result of TT::get_out_charset()
I've tried adding it manually and this is the mpod2html response:
*** ERROR: Unknown command 'encoding' at line 14 in file html/tmp/po4a.7.pod
Yeah. We may have to trick here.
The easiest solution is that you provide your patch about names to Marek,
and report that the encoding needs love too. You may get him fix his
package.
If it doesn't work, as you said, we can force the encoding to iso for now.
That's crude but effective as long as it's possible.
You may consider patching that part of the html generator, if it's not too
long.
Or we may stop generating html. What a pitty.
And here's the pod2man one:
po4a.7.pod:14: Unknown command paragraph "=encoding utf-8"
Is this an unsupported feature or am I doing something wrong? :S
This is a very new feature. Which version of perl do you use?
Mt.
--
Si vous pensez que l'éducation coûte cher, essayez l'ignorance.
-- Albert Einstein
12:16 p.m.
On Fri, 13 Aug 2004, Martin Quinson wrote:
On Fri, Aug 13, 2004 at 11:00:14AM +0200, Jordi Vilalta wrote:
> On Fri, 13 Aug 2004, Jordi Vilalta wrote:
>
> http://search.cpan.org/dist/perl/pod/perlpodspec.pod
> http://search.cpan.org/dist/perl/pod/perlpod.pod
>
> There seems to be a =encoding command. Maybe this should be added by the
> Pod module, taking the result of TT::get_out_charset()
>
> I've tried adding it manually and this is the mpod2html response:
>
> *** ERROR: Unknown command 'encoding' at line 14 in file html/tmp/po4a.7.pod
Yeah. We may have to trick here.
The easiest solution is that you provide your patch about names to Marek,
and report that the encoding needs love too. You may get him fix his
package.
I'll do it now
If it doesn't work, as you said, we can force the encoding to iso for now.
That's crude but effective as long as it's possible.
You may consider patching that part of the html generator, if it's not too
long.
IIRC, Marek has addapted the Pod::Parser and some other modules, so maybe
this should also be reported to these ones.
Or we may stop generating html. What a pitty.
> And here's the pod2man one:
>
> po4a.7.pod:14: Unknown command paragraph "=encoding utf-8"
>
> Is this an unsupported feature or am I doing something wrong? :S
This is a very new feature. Which version of perl do you use?
I'm using v5.8.4. It's documented, but the current parsers don't
have it implemented it yet :(
Regards,
Jordi Vilalta
11:04 a.m.
On Fri, Aug 13, 2004 at 11:00:14AM +0200, Jordi Vilalta wrote:
And here's the pod2man one:
po4a.7.pod:14: Unknown command paragraph "=encoding utf-8"
Is this an unsupported feature or am I doing something wrong? :S
Works for me. At least, I don't get any error message when adding this at
the begining of po4a.7.pod, but didn't try with the translated ones.
.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
Perl 5.8.4
Bye, Mt.
--
No, I'm not going to explain it.
If you can't figure it out, you didn't want to know anyway...
--- Larry Wall
7405
days inactive
7406
days old
6 comments
3 participants
participants (3)
-
Danilo Piazzalunga -
Jordi Vilalta -
Martin Quinson