public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Documentation Encoding
Date: Sat, 22 Apr 2006 23:02:06 +0900	[thread overview]
Message-ID: <444A375E.3090301@thinrope.net> (raw)
In-Reply-To: <200604221544.03548.damjanek@chopin.edu.pl>

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



  reply	other threads:[~2006-04-22 14:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-22 13:44 [gentoo-dev] Documentation Encoding Damian Szeluga
2006-04-22 14:02 ` Kalin KOZHUHAROV [this message]
2006-04-22 16:34   ` Mike Frysinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=444A375E.3090301@thinrope.net \
    --to=kalin@thinrope.net \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox