Hi, All I have found that russian html page, generated by groff from mplayer.1 and published on MPlayer website have broken encoding. It doesn't have any cyrilly characted. Here is a line from page source <a href="#éóðïìøúï÷áîéå">éóðïìøúï÷áîéå</a><br> I'm think, that it was generated using ISO-8859-1 (or similar) encoding enstead of koi8-r. -- Regards, Vladimir Voroshilov mailto:voroshil@gmail.com JID: voroshil@jabber.ru ICQ: 95587719
On Wed, Nov 08, 2006 at 12:01:25PM +0600, Vladimir Voroshilov wrote:
I have found that russian html page, generated by groff from mplayer.1 and published on MPlayer website have broken encoding. It doesn't have any cyrilly characted. Here is a line from page source <a href="#éóðïìøúï÷áîéå">éóðïìøúï÷áîéå</a><br>
I'm think, that it was generated using ISO-8859-1 (or similar) encoding enstead of koi8-r.
The problem is that (current versions of) groff do not support KOI8-R input. We already had a similar problem with the Chinese and Czech man pages - they are in UTF-8 encoding - that we solved by using groff-utf8, which accepts UTF-8 input. One solution would be to convert the Russian manual page to UTF-8. Generating HTML from that is not a problem, it works for Chinese and Czech and I just confirmed it's no problem with Russian. Whether this is a problem for system man pages - I don't know, you'll have to tell me how it works for you. A course of action here would be to run the UTF-8 man page through iconv during the installation procedure. This could pave the way for using only UTF-8 for the man pages as well. I could also hack up the documentation generation script to convert the Russian man page from KOI8-R to UTF-8 before generating the HTML. Opinions? Diego
On Wed, Nov 08, 2006 at 12:01:25PM +0600, Vladimir Voroshilov wrote: The problem is that (current versions of) groff do not support KOI8-R input. We already had a similar problem with the Chinese and Czech man pages - they are in UTF-8 encoding - that we solved by using groff-utf8, which accepts UTF-8 input.
One solution would be to convert the Russian manual page to UTF-8. Generating HTML from that is not a problem, it works for Chinese and Czech and I just confirmed it's no problem with Russian.
Whether this is a problem for system man pages - I don't know, you'll have to tell me how it works for you. A course of action here would be to run the UTF-8 man page through iconv during the installation procedure. This could pave the way for using only UTF-8 for the man pages as well. This will be a problem at least on my Gentoo box. It does not show UTF-8 man pages correctly under koi8-r locale. So converting man
2006/11/8, Diego Biurrun <diego@biurrun.de>: pages to unicode will be good solution only after creating apropriate install script. I prefer to keep koi8-r encoding till translation end.
I could also hack up the documentation generation script to convert the Russian man page from KOI8-R to UTF-8 before generating the HTML.
During translation process, i prefer this case, but i also want to hear another developers' opinions. P.S. I also will try to found solution to show unicode man pages on non-unicode locale correctly. -- Regards, Vladimir Voroshilov mailto:voroshil@gmail.com JID: voroshil@jabber.ru ICQ: 95587719
On Wed, Nov 08, 2006 at 07:08:55PM +0600, Vladimir Voroshilov wrote:
On Wed, Nov 08, 2006 at 12:01:25PM +0600, Vladimir Voroshilov wrote: The problem is that (current versions of) groff do not support KOI8-R input. We already had a similar problem with the Chinese and Czech man pages - they are in UTF-8 encoding - that we solved by using groff-utf8, which accepts UTF-8 input.
One solution would be to convert the Russian manual page to UTF-8. Generating HTML from that is not a problem, it works for Chinese and Czech and I just confirmed it's no problem with Russian.
Whether this is a problem for system man pages - I don't know, you'll have to tell me how it works for you. A course of action here would be to run the UTF-8 man page through iconv during the installation procedure. This could pave the way for using only UTF-8 for the man pages as well. This will be a problem at least on my Gentoo box. It does not show UTF-8 man pages correctly under koi8-r locale. So converting man
2006/11/8, Diego Biurrun <diego@biurrun.de>: pages to unicode will be good solution only after creating apropriate install script.
Should be easy enough: iconv -t UTF-8 -f KOI8-R < DOCS/man/ru/mplayer.1 > $DESTDIR/mplayer.1 or similar integrated into 'make install'.
I prefer to keep koi8-r encoding till translation end.
What difference does it make? XML docs are already UTF-8...
P.S. I also will try to found solution to show unicode man pages on non-unicode locale correctly.
You may wish to look at groff-utf8. Diego
Diego Biurrun wrote:
This will be a problem at least on my Gentoo box. It does not show UTF-8 man pages correctly under koi8-r locale. So converting man pages to unicode will be good solution only after creating apropriate install script.
Should be easy enough:
iconv -t UTF-8 -f KOI8-R < DOCS/man/ru/mplayer.1 > $DESTDIR/mplayer.1
or similar integrated into 'make install'. I think (if you wish to keep all docs in unicode), better way will be keeping man page as UTF-8 in source tree and convert it to KOI8-R during install. I'm afraid that many russian distros have troubles with unicode man pages (but i'm not sure about this).
I prefer to keep koi8-r encoding till translation end.
What difference does it make? XML docs are already UTF-8...
P.S. I also will try to found solution to show unicode man pages on non-unicode locale correctly.
You may wish to look at groff-utf8. I meant some world-wide solution, that will work on any (or most) distro out of box :) I my case (translating man page) iconv+groff will be enough.
Ok. If you say 'yes' i'll convert man page to UTF-8. This would not be much harder than working with unicode xml files. -- Regards, Vladimir Voroshilov mailto:voroshil@gmail.com Omsk State University JID: voroshil@jabber.ru ICQ: 95587719
On 8 Nov 2006 20:33, voroshil@gmail.com wrote:
Should be easy enough:
iconv -t UTF-8 -f KOI8-R < DOCS/man/ru/mplayer.1 > $DESTDIR/mplayer.1
or similar integrated into 'make install'.
I think (if you wish to keep all docs in unicode), better way will be keeping man page as UTF-8 in source tree and convert it to KOI8-R during install. I'm afraid that many russian distros have troubles with unicode man pages (but i'm not sure about this).
Patriculary on my system it is not a problem to read utf-8 manuals (I use ASP 11, which is FC5-based). But I agree that cyryllic workstations are not utf-8 ready and confirm a lot of troubles with reding utf-8 manuals on other/older systems. IMHO we can't force unicode man pages, because users will be forced to use utf-8 systems to read them. So the best solution will be one proposed by Vladimir: convert man page to system's locale during install.
On Thu, Nov 09, 2006 at 01:23:20AM +0300, Andrew Savchenko wrote:
Patriculary on my system it is not a problem to read utf-8 manuals (I use ASP 11, which is FC5-based).
How does Fedora achieve this? Diego
On 10 Nov 2006 18:04, Diego Biurrun wrote:
On Thu, Nov 09, 2006 at 01:23:20AM +0300, Andrew Savchenko wrote:
Patriculary on my system it is not a problem to read utf-8 manuals (I use ASP 11, which is FC5-based).
How does Fedora achieve this?
It seems that nroff automatically recognize utf-8 and convert it to locale's encoding. For testing purposes I convert ru/mplayer.1 to utf-8 and checked out that running $ nroff -mandoc 2>/dev/null mplayer.1 is enough to display properly utf-8 man page on non-utf8 locale (cp1251). I'm using groff-1.18.1.1-6.FC4, maybe this will help. According to info groff it supports unicode, I don't know how exactly.
On Saturday, 11 November 2006 at 03:59, Andrew Savchenko wrote:
On 10 Nov 2006 18:04, Diego Biurrun wrote:
On Thu, Nov 09, 2006 at 01:23:20AM +0300, Andrew Savchenko wrote:
Patriculary on my system it is not a problem to read utf-8 manuals (I use ASP 11, which is FC5-based).
How does Fedora achieve this?
It seems that nroff automatically recognize utf-8 and convert it to locale's encoding. For testing purposes I convert ru/mplayer.1 to utf-8 and checked out that running $ nroff -mandoc 2>/dev/null mplayer.1 is enough to display properly utf-8 man page on non-utf8 locale (cp1251).
I'm using groff-1.18.1.1-6.FC4, maybe this will help. According to info groff it supports unicode, I don't know how exactly.
Fedora's groff is heavily patched: http://cvs.fedora.redhat.com/viewcvs/devel/groff/ I bet some of these patches add utf support. Regards, R. -- MPlayer developer and RPMs maintainer: http://rpm.greysector.net/mplayer/ There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan
On Wed, Nov 08, 2006 at 01:51:34PM +0100, Diego Biurrun wrote:
I could also hack up the documentation generation script to convert the Russian man page from KOI8-R to UTF-8 before generating the HTML.
I have done this and gone one step further by converting all man pages to UTF-8 before converting them to HTML and text with groff-utf8. This seems to work well, even the text version of the Polish man page has no more obvious artifacts. Please verify this is working correctly for you, but make sure you use the www1 mirror, otherwise you might be looking at an outdated copy. Diego
Diego Biurrun wrote:
On Wed, Nov 08, 2006 at 01:51:34PM +0100, Diego Biurrun wrote:
Please verify this is working correctly for you, but make sure you use the www1 mirror, otherwise you might be looking at an outdated copy. Russian HTML man page on www1 displays correctly.
Diego _______________________________________________ MPlayer-DOCS mailing list MPlayer-DOCS@mplayerhq.hu http://lists.mplayerhq.hu/mailman/listinfo/mplayer-docs
-- Regards, Vladimir Voroshilov mailto:voroshil@gmail.com Omsk State University JID: voroshil@jabber.ru ICQ: 95587719
participants (5)
-
Andrew Savchenko -
Diego Biurrun -
Dominik 'Rathann' Mierzejewski -
Vladimir Voroshilov -
voroshil＠gmail.com