Re: [MPlayer-DOCS] [RFC] converting documentation to UTF-8
Diego Biurrun wrote:
This makes me think that the moment to convert everything to UTF-8 may have come. Others have been lobbying for it before, I'm willing to go along now. I'm in favor of it. On my console, umlauts and some other characters are always garbled when I svn diff the German (iso-8859-1) xml files. So it would definitely ease the workflow for me. Is there anything that speaks against the conversion? Will it cause problems for translators? Any volunteers to do it? Following the thread it seems that the issue is solved for most if not all contributors. Since there are some vim users out there besides me, it might be considerable to add vim flags to the files so thatfileencoding settings are automatically set (although it works fine for me without them).I have no idea though if it might cause trouble when viewing the docs for all the platforms/browsers out there. Maybe we should check that too for some of them. I'm willing to make conversions although I think that some contributors with write access should do it themselves for their language in order to verify that it really works for them. On huge patch/commit per language should do the job then I think. Also, I assume that not all languages have to be converted at the same time.. Is there anything to do besides changing the xml flag (first line of the file) and the conversion with ie iconv?
Sebastian
Is there anything to do besides changing the xml flag (first line of the file) and the conversion with ie iconv?
I just did that. Seems to work perfectly here. Unfortunately I cannot check with a pure iso-8859-something system..
mail@kraymer.de píše v Po 30. 10. 2006 v 13:36 +0100:
Is there anything to do besides changing the xml flag (first line of the file) and the conversion with ie iconv?
I just did that. Seems to work perfectly here. Unfortunately I cannot check with a pure iso-8859-something system..
On my Sarge/latin2: html documentation in UTF-8: works (links2, firefox) manpage in UTF-8: crappy but no big deal, freezes mc when preview. manpage in UTF-8 on rxvt-unicode: works fine
_______________________________________________ MPlayer-DOCS mailing list MPlayer-DOCS@mplayerhq.hu http://lists.mplayerhq.hu/mailman/listinfo/mplayer-docs
On Wed, Nov 01, 2006 at 09:26:40AM +0100, Jiří Heryán wrote:
mail@kraymer.de píše v Po 30. 10. 2006 v 13:36 +0100:
Is there anything to do besides changing the xml flag (first line of the file) and the conversion with ie iconv?
I just did that. Seems to work perfectly here. Unfortunately I cannot check with a pure iso-8859-something system..
On my Sarge/latin2: html documentation in UTF-8: works (links2, firefox) manpage in UTF-8: crappy but no big deal, freezes mc when preview. manpage in UTF-8 on rxvt-unicode: works fine
Converting the man page to HTML is problematic. This may be due to the fact that I have an outdated groff version that does not yet properly support UTF-8. It seems that Debian (even unstable) still carries groff 1.18.1 while the current version is 1.19.2 ... Diego
On Wed, Nov 01, 2006 at 02:47:31PM +0100, Diego Biurrun wrote:
On Wed, Nov 01, 2006 at 09:26:40AM +0100, Jiří Heryán wrote:
mail@kraymer.de píše v Po 30. 10. 2006 v 13:36 +0100:
Is there anything to do besides changing the xml flag (first line of the file) and the conversion with ie iconv?
I just did that. Seems to work perfectly here. Unfortunately I cannot check with a pure iso-8859-something system..
On my Sarge/latin2: html documentation in UTF-8: works (links2, firefox) manpage in UTF-8: crappy but no big deal, freezes mc when preview. manpage in UTF-8 on rxvt-unicode: works fine
Converting the man page to HTML is problematic. This may be due to the fact that I have an outdated groff version that does not yet properly support UTF-8. It seems that Debian (even unstable) still carries groff 1.18.1 while the current version is 1.19.2 ...
I've done a bit more digging and it seems that groff is behind the times even in current versions :-( There is a wrapper called groff-utf8 that works around the most glaring deficiencies and is able to handle UTF-8 input files: http://www.haible.de/bruno/packages-groff-utf8.html Right now we have a problem with the Czech and Chinese man page, which are already in UTF-8 and the converted HTML and text versions on the homepage are garbage. I have updated the documentation generation script to use groff-utf8 for the Czech and Chinese man pages, seems to work fine so far.. Diego
On Wed, Nov 01, 2006 at 06:20:46PM +0100, Diego Biurrun wrote:
I have updated the documentation generation script to use groff-utf8 for the Czech and Chinese man pages, seems to work fine so far..
Note that the text version of the Polish man page is somewhat garbled at the moment. If some of you Polish people care about it, you'll have to find a fix yourselves, I really don't know how. Diego
On Wed, Nov 01, 2006 at 06:44:04PM +0100, Diego Biurrun wrote:
Note that the text version of the Polish man page is somewhat garbled at the moment. If some of you Polish people care about it, you'll have to find a fix yourselves, I really don't know how.
It's something broken/too new on MPlayer box, as on my box conversion (both with col -bxp and col -bx) works fine. Anyway, unless someone tells me how to make man understand one utf-8 manpage amongst many iso-8859-2 ones, I'm against conversion of manpage to utf-8, as it simply breaks everything on my system. Torinthiel -- Waclaw "Torinthiel" Schiller GG#: 3073512 torinthiel(at)megapolis(dot)pl gpg: 0906A2CE fpr: EE3E DFB4 C4D6 E22E 8999 D714 7CEB CDDC 0906 A2CE "No classmates may be used during this examination"
On Wed, Nov 01, 2006 at 07:00:42PM +0100, Torinthiel wrote:
On Wed, Nov 01, 2006 at 06:44:04PM +0100, Diego Biurrun wrote:
Note that the text version of the Polish man page is somewhat garbled at the moment. If some of you Polish people care about it, you'll have to find a fix yourselves, I really don't know how.
It's something broken/too new on MPlayer box, as on my box conversion (both with col -bxp and col -bx) works fine.
distro? groff version? Diego
On Wed, Nov 01, 2006 at 07:04:53PM +0100, Diego Biurrun wrote:
It's something broken/too new on MPlayer box, as on my box conversion (both with col -bxp and col -bx) works fine.
distro? groff version?
PLD linux. Doubt you've heard of it (unless I've mentioned it earlier). www.pld-linux.org IIRC kraken:~$ groff --version GNU groff version 1.18.1 Copyright (C) 2002 Free Software Foundation, Inc. GNU groff comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of groff and its subprograms under the terms of the GNU General Public License. For more information about these matters, see the file named COPYING. called subprograms: GNU grops (groff) version 1.18.1 GNU troff (groff) version 1.18.1 (yes, it's quite ancient, but it's possible PLD added some Polish support patches, I'll check later today) Torinthiel -- Waclaw "Torinthiel" Schiller GG#: 3073512 torinthiel(at)megapolis(dot)pl gpg: 0906A2CE fpr: EE3E DFB4 C4D6 E22E 8999 D714 7CEB CDDC 0906 A2CE "No classmates may be used during this examination"
On Wed, Nov 01, 2006 at 07:00:42PM +0100, Torinthiel wrote:
On Wed, Nov 01, 2006 at 06:44:04PM +0100, Diego Biurrun wrote:
Note that the text version of the Polish man page is somewhat garbled at the moment. If some of you Polish people care about it, you'll have to find a fix yourselves, I really don't know how.
It's something broken/too new on MPlayer box, as on my box conversion (both with col -bxp and col -bx) works fine. Anyway, unless someone tells me how to make man understand one utf-8 manpage amongst many iso-8859-2 ones, I'm against conversion of manpage to utf-8, as it simply breaks everything on my system.
Two possible solutions... 1. convert to local encoding at build-time or install-time. 2. make the system tools assume utf-8 but fallback to a configured legacy codepage if any text which does not parse as valid utf-8 appears. Rich
Diego Biurrun píše v St 01. 11. 2006 v 18:44 +0100:
On Wed, Nov 01, 2006 at 06:20:46PM +0100, Diego Biurrun wrote:
I have updated the documentation generation script to use groff-utf8 for the Czech and Chinese man pages, seems to work fine so far..
TXT export is still broken, I'm afraid. Unfortunately I can't offer a solution. Regards Jiri
On Mon, Nov 27, 2006 at 11:25:16AM +0100, Jiří Heryán wrote:
Diego Biurrun píše v St 01. 11. 2006 v 18:44 +0100:
On Wed, Nov 01, 2006 at 06:20:46PM +0100, Diego Biurrun wrote:
I have updated the documentation generation script to use groff-utf8 for the Czech and Chinese man pages, seems to work fine so far..
TXT export is still broken, I'm afraid. Unfortunately I can't offer a solution.
Yes, the section titles get mangled. I have no idea why. Diego
On Mon, Oct 30, 2006 at 12:41:39PM +0100, mail@kraymer.de wrote:
I'm willing to make conversions although I think that some contributors with write access should do it themselves for their language in order to verify that it really works for them. On huge patch/commit per language should do the job then I think. Also, I assume that not all languages have to be converted at the same time..
Converting one at a time is of course no problem. Also, the maintainers should agree, although it seems that all maintainers do now.
Is there anything to do besides changing the xml flag (first line of the file) and the conversion with ie iconv?
I'm not aware of anything. Diego
Hello, [...] On Mon, Oct 30, 2006 at 12:41:39PM +0100, mail@kraymer.de wrote:
contributors. Since there are some vim users out there besides me, it might be considerable to add vim flags to the files so thatfileencoding settings are automatically set (although it works fine for me without them).I have no idea though if it might cause trouble when viewing the docs for
I'm not against adding vim flags, but it might be more helpful to document a bit how to configure vim right for utf8-editing, I think support for vim-flags is quite often deactivated by default because of vulnerabilities in the past (and it is the kind of feature that always gives me an uncomfortable feeling)... Greetings, Reimar Döffinger
Hello, [...] On Mon, Oct 30, 2006 at 12:41:39PM +0100, mail@kraymer.de wrote:
contributors. Since there are some vim users out there besides me, it might be considerable to add vim flags to the files so thatfileencoding settings are automatically set (although it works fine for me without them).I have no idea though if it might cause trouble when viewing the docs for
I'm not against adding vim flags, but it might be more helpful to document a bit how to configure vim right for utf8-editing, I think support for vim-flags is quite often deactivated by default because of vulnerabilities in the past (and it is the kind of feature that always gives me an uncomfortable feeling)...
Hm, good point. I wasn't aware of these things and I'm not really sure now if vim would use these flags on my system (as mentioned before, I don't need them anyway). Also, there's no need to jump the gun with it. Anyone else in favor/against vim (or also emacs) flags?Let's get done with the conversions first. After that, I could add a few lines in translations.txt about :set fileencoding and termencoding(?); at least these were the only enc. commands I ever needed. Sebastian
participants (6)
-
Diego Biurrun -
Jiří Heryán -
mail＠kraymer.de -
Reimar Döffinger -
Rich Felker -
Torinthiel