All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Krelin <hacker@klever.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] locales
Date: Wed, 20 Jun 2007 12:45:15 +0200	[thread overview]
Message-ID: <4679053B.4060606@klever.net> (raw)
In-Reply-To: <48239d390706200314y300766en9956ec5e56789ce5@mail.gmail.com>

I do not see why do we want to get rid of non-utf locales. Wouldn't an 
attempt to make utf-locales work more productive? And I believe making 
things work should be of higher priority than making packaging friendlier.

At the moment, we have troubles entering non-latin utf8 in x11. That 
should be fixed before going any further. And before you can fix it you 
need to find out what exactly the problem is. This is where I'd suggest 
that we start at.

Love,
H

Sergey Lapin wrote:
> Hi, all!
> 
> Note: I could be fundamentally wrong here, so, please feel free to
> point me to right direction in this case.
> 
> As it was discussed on #oe, locale infrastructure lacks implementation
> on oe.dev, and, in particular, in Angstrom.
> 
> With a bit of research I done on this subject made me to come up with
> a few ideas, which I'd like to know your opinion about.
> 
> Present status:
> *-locale* packages are generated, but not put on image. These packages
> contain message translations.
> * Only glibc locale which is put on image (if any) is en_GB.
> 
> Infrastructure problem:
> * We need a way to set up automatic locale package installation during
> image build
> according to some subset of languages/locales.
> * We need a way to install "language" in simple user-friendly way. I
> mean here not only locale packages, but also various
> language-dependent files (docs, keymap settings, various configuration
> files, etc.).
> 
> Various random problems encountered:
> * GPE locale.alias for gpe-dm needs cleanup (get rid of non-UTF8 locales?)
> * libx11 locale.alias needs cleanup (setup for UTF8-only system).
> 
> So, if we go utf8-only, we need to do a great cleanup/testing job here
> to settle things up.
> 
> As for infrastructure, I see several questionable methods of solving this:
> 
> 1. each package RRECOMMENDS its locale packages for locales mentioned
> in local.conf variable, and additional ones, which are related.
> 
> 2. image RRECOMMENDS locale packages blindly for all normal packages
> for languages which are in a var mentioned in 1.
> 
> 3. all -locale packages generated during builds are written to some
> special lists, for each language. Then meta-packages are generated
> from these lists.
> 
> ...
> 
> So, any ideas?
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 



  parent reply	other threads:[~2007-06-20 11:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20 10:14 [RFC] locales Sergey Lapin
2007-06-20 10:40 ` Holger Freyther
2007-06-20 14:25   ` Sergey Lapin
2007-06-20 14:34     ` Holger Freyther
2007-06-20 15:01       ` Sergey Lapin
2007-06-20 14:55     ` Paul Sokolovsky
2007-06-20 10:45 ` Michael Krelin [this message]
2007-06-20 11:36   ` Koen Kooi
2007-06-20 15:34 ` Paul Sokolovsky
2007-06-20 22:05   ` Sergey Lapin
2007-06-21  7:38     ` Paul Sokolovsky
2007-06-21  7:53       ` Koen Kooi

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=4679053B.4060606@klever.net \
    --to=hacker@klever.net \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.