[gentoo-dev] Documentation Encoding

[gentoo-dev] Documentation Encoding

[Damian Szeluga]

[-- Attachment #1: Type: text/plain, Size: 799 bytes --]

Hi!

I'm using UTF-8 encoding in my system. The main problem is, that lots
of /usr/share/man/* and /usr/share/doc/* files are iso8859-2 encoded (as my
LINGUAS is set to pl). I think, that Portage itself should recode all the
files, which go to /usr/share/man/ and /usr/share/doc/ directories to UTF-8
by default. There's also a problem with Groff, which is unable to show
unicode chars correctly. I made a package to solve it
(http://hoth.amu.edu.pl/~d_szeluga/groff-utf8.tar.bz2), but I think it's a
bit dirty hack.
So:
Are there any plans, to make Portage install all the docs in desired
encoding? 
Are there any plans, to do something with Groff?

-- 
PGP: 0xAB6AF545
Fingerpring: FE1C FC81 61E9 3979 4A1E  B0E2 27DB 5EA1 AB6A F545
JID: damjanek <at> chopin <dot> edu <dot> pl

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

Re: [gentoo-dev] Documentation Encoding

[Kalin KOZHUHAROV]

Damian Szeluga wrote:
> I'm using UTF-8 encoding in my system. The main problem is, that lots
> of /usr/share/man/* and /usr/share/doc/* files are iso8859-2 encoded (as my
> LINGUAS is set to pl). I think, that Portage itself should recode all the
> files, which go to /usr/share/man/ and /usr/share/doc/ directories to UTF-8
> by default.
Not sure if that will be an easy task since the source encoding is probably not
known. Probably this should go upstream?

> There's also a problem with Groff, which is unable to show
> unicode chars correctly. I made a package to solve it
> (http://hoth.amu.edu.pl/~d_szeluga/groff-utf8.tar.bz2), but I think it's a
> bit dirty hack.
I am absolutely out of time now, hope to be able to look at it in a week.
.. actually I had a look :-) So this is a different package from groff as it seems.
http://www.haible.de/bruno/packages-groff-utf8.html

Dunnow, but probably trying to integrate UTF-8 support in groff and working with
upstream should be doable if that package is working?
We in JP land often have problems with Japanese man pages and others and there was
a patch floating around (USE=cjk emerge groff) that kind of solves the problem a bit.

So, fixing groff is definately a good idea!
Any takers? ;-)

The last time I looked in the code I couldn't make much out of it :-(

Kalin.

-- 
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|

-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Documentation Encoding

[Mike Frysinger]

On Saturday 22 April 2006 10:02, Kalin KOZHUHAROV wrote:
> Damian Szeluga wrote:
> > There's also a problem with Groff, which is unable to show
> > unicode chars correctly. I made a package to solve it
> > (http://hoth.amu.edu.pl/~d_szeluga/groff-utf8.tar.bz2), but I think it's
> > a bit dirty hack.
>
> I am absolutely out of time now, hope to be able to look at it in a week.
> .. actually I had a look :-) So this is a different package from groff as
> it seems. http://www.haible.de/bruno/packages-groff-utf8.html
>
> Dunnow, but probably trying to integrate UTF-8 support in groff and working
> with upstream should be doable if that package is working?

yes ... working with upstream is best as i'm pretty clueless when it comes to 
UTF8 issues in groff and wont really be of any use in getting it fixed in 
portage ... see this bug:
http://bugs.gentoo.org/126361

> We in JP land often have problems with Japanese man pages and others and
> there was a patch floating around (USE=cjk emerge groff) that kind of
> solves the problem a bit.

if you want/need cjk support, you'll have to use groff-1.18.x as groff-1.19.x 
wont work
-mike
-- 
gentoo-dev@gentoo.org mailing list