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] enable UTF8 per default?
Date: Wed, 01 Mar 2006 01:24:26 +0900	[thread overview]
Message-ID: <4404793A.6060701@thinrope.net> (raw)
In-Reply-To: <20060228125046.GX10994@elladan.wh-og.hs-niederrhein.de>

Lars Weiler wrote:
> * Patrick Lauer <patrick@gentoo.org> [06/02/28 11:58 +0100]:
>> Enabling the unicode useflag in the profiles should help our
>> international users and should not cause any problems. Are there any
>> known bugs / problems this would trigger? Any reasons against that?
> 
> It is enabled by default.  At least on ppc.  And that since,
> uhm, summer 2004?
> 
> I can't say if there are any problems, as I didn't received
> a bug for a long time.
Well there are a few problems, but yes I cannot name them now.
Using Japanese, Cyrillic and English in a few encodings each is a big nightmare.

Nowadays I try to move everything to UTF-8, but there are those windoze users
and webdevs that make all Japanese in Shift_JIS ... So support of wide range of
encodings is a must, but UTF-8 is the truth.

> The only thing that's nasty: we don't have any good utf8-fonts for the console.
And not only the console.
Even for xterm there are not many good fonts (known to me) that display both Japanese
and Cyrillic in regular and bold. Currently there is only on combination that works for me.

So fonts, font config and related stuff is what has to be fixed first.

Kalin.

P.S. And before fixed, it has to be filed... Promise to take notes (again) when I see something.
-- 
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|

-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-02-28 16:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28 10:58 [gentoo-dev] enable UTF8 per default? Patrick Lauer
2006-02-28 11:32 ` Diego 'Flameeyes' Pettenò
2006-02-28 11:47   ` Patrick Lauer
2006-02-28 12:11     ` Diego 'Flameeyes' Pettenò
2006-02-28 14:27     ` Mike Frysinger
2006-02-28 12:50 ` Lars Weiler
2006-02-28 13:50   ` Patrick Lauer
2006-02-28 14:46     ` Joseph Jezak
2006-02-28 16:24   ` Kalin KOZHUHAROV [this message]
2006-03-04 12:46     ` Alexander Simonov
2006-03-04 20:13       ` Kalin KOZHUHAROV
2006-02-28 16:51 ` Josh
2006-02-28 17:47 ` solar
2006-02-28 17:53   ` Ciaran McCreesh
2006-02-28 18:25   ` Bryan Østergaard
2006-02-28 19:18   ` Kevin F. Quinn (Gentoo)
2006-02-28 20:23     ` solar
2006-02-28 23:51 ` Bjarke Istrup Pedersen
2006-03-08  7:43 ` [gentoo-dev] " Mathieu Bonnet
2006-03-09 20:25 ` [gentoo-dev] " Kevin F. Quinn (Gentoo)
2006-03-11 20:29 ` Eldad Zack

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=4404793A.6060701@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