On Wed, 2002-02-27 at 20:02, Petter Reinholdtsen wrote:
> Do anyone but me thing this is a good idea? Should I submit a patch
> into BTS, or what?
Please do.
p.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[Petter Reinholdtsen]
> I'm working on fixes for base-config, and in the process I thought it
> is smart to change dbootstrap to be able to us the lang->msgcat
> content the same way as the LANGUAGE environment is handled by libc,
> ie as a colon separated list of langauges to try. It is very re
Junichi Uekawa wrote:
> > You mean something like the termwrap program in base-config?
>
> Yes, I have now been informed that this work has already been done
> a while ago.
Of course it doesn't work if the necessary terminal programs are not
installed by dbootstrap for the chosen languages. I'm
Joey Hess <[EMAIL PROTECTED]> cum veritate scripsit:
> > I have an impression that you don't seem to understand the problem.
> > The right way would be to have a way of starting jfbterm
> > before base-config.
>
> You mean something like the termwrap program in base-config?
Yes, I have now bee
Petter Reinholdtsen wrote:
> [Joey Hess]
> > You mean something like the termwrap program in base-config?
>
> It looks relevant, but I'm unable to find out from where it is
> executed. Is it currently used by base-config?
The inittab written by dbootstrap calls it.
--
see shy jo
--
To UNSU
[Joey Hess]
> You mean something like the termwrap program in base-config?
It looks relevant, but I'm unable to find out from where it is
executed. Is it currently used by base-config?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTE
Junichi Uekawa wrote:
> I have an impression that you don't seem to understand the problem.
> The right way would be to have a way of starting jfbterm
> before base-config.
You mean something like the termwrap program in base-config?
--
see shy jo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTE
[Junichi Uekawa]
> Looks more sane, to me, at least.
Good. I submitted it to BTS, #135565.
Fixing it in base-config first, and then start to propagate more up to
date LANG and LANGUAGE variables from boot-floppies sounds like a good
idea. Hope Joey share my view. :-)
--
To UNSUBSCRIBE, ema
Petter Reinholdtsen <[EMAIL PROTECTED]> cum veritate scripsit:
> OK. Second try. Tests if the locale is valid, generate it if it is
> missing, try to set the console charset (assuming it is already
> ISO-8859-1), and unset LANG and LANGUAGE if any of this fails.
>
> Would this still break Japa
[Junichi Uekawa]
> Add something like this:
OK. Second try. Tests if the locale is valid, generate it if it is
missing, try to set the console charset (assuming it is already
ISO-8859-1), and unset LANG and LANGUAGE if any of this fails.
Would this still break Japanese installs, or should it
I'm working on fixes for base-config, and in the process I thought it
is smart to change dbootstrap to be able to us the lang->msgcat
content the same way as the LANGUAGE environment is handled by libc,
ie as a colon separated list of langauges to try. It is very relevant
for Norwegian, where Bo
At Sun, 24 Feb 2002 23:52:29 +0900,
Junichi Uekawa wrote:
> > base-config could check the locale, run the apropriate program and
> > restart itself afterwards. This means: load fonts for latin* and koi8*
> > locales, or start the special terminal programs for Japaneese and
> > similar.
>
> I've g
Eduard Bloch <[EMAIL PROTECTED]> cum veritate scripsit:
> Okay, what not just make a static list of non-latin1 languages which
> have special requirements, and install those requirements from
> dbootstrap? As said, the new debootstrap has the --include=... option(*).
>
> base-config could check
On Sun, 2002-02-24 at 14:03, Eduard Bloch wrote:
> Okay, what not just make a static list of non-latin1 languages which
> have special requirements, and install those requirements from
> dbootstrap? As said, the new debootstrap has the --include=... option(*).
Yup, that's exactly what needs to be
#include
Philip Blundell wrote on Sun Feb 24, 2002 um 01:50:52PM:
> Take ja_JP as an example. At the moment, if you select Japanese at the
> dbootstrap language chooser screen, the first stage install will use
> Japanese and everything after reboot (ie base-config etc) will use
> English. With
On Sun, 2002-02-24 at 00:21, Petter Reinholdtsen wrote:
> Is there anyone who know if the font/charset information in the
> langs/*.src files is used at all?
Dbootstrap does make some effort to do so, see setFont in boxes.c. I
don't think we actually ship the support files to make this work, no
On Sun, 2002-02-24 at 00:26, Petter Reinholdtsen wrote:
> Is there anything in the patch that should make it worse for non-latin
> languages?
Yes.
Take ja_JP as an example. At the moment, if you select Japanese at the
dbootstrap language chooser screen, the first stage install will use
Japanese
On Sun, Feb 24, 2002 at 09:43:45PM +0900, Junichi Uekawa wrote:
> But how much is supported by the console anyway?
>
> C ?
> I've got an impression that
> ISO-8859-1 seems to be supported (somewhat).
Latin 2 (i.e. ISO-8859-2) is supported just fine provided an appropriate
console font is set.
Petter Reinholdtsen <[EMAIL PROTECTED]> cum veritate scripsit:
Add something like this:
use_locales_supported () {
case $1 in
en_*) return 0 ;;
whatever_*) return 0 ;;
else_*) return 0 ;;
*)
# the fallback is not to use it.
return 1;
;;
}
and surround the
Petter Reinholdtsen <[EMAIL PROTECTED]> cum veritate scripsit:
> I understand this to mean the right way for Japanese install. I
> believe that is not my problem but your problem. I do not know how to
> solve your problem. I do not know which charset or encoding are used
> in Japan. I do not
[Junichi Uekawa]
> I have an impression that you don't seem to understand the problem.
Perhaps not. I hope discussing it here will improve the general
understanding.
> The right way would be to have a way of starting jfbterm before
> base-config.
I understand this to mean the right way for Jap
Petter Reinholdtsen <[EMAIL PROTECTED]> cum veritate scripsit:
> The locale part is by the way broken. it should be 'ja_JA' or something
> other valid variation.
No, JA does not exist.
ja_JP is a valid locale.
Japanese language of Japan.
I have an impression that you don't seem to understan
[Junichi Uekawa]
> Er... no, it will cause problems, if it was used for anything that
> is not supported by the console by default.
>
> I don't think that many languages are supported by the default console.
> That kind of attitude is found pretty often in latin-charset people.
Eh, I think you m
Petter Reinholdtsen <[EMAIL PROTECTED]> cum veritate scripsit:
> Well, it will only cause some problems if it is used for Japanese.
> Adding the patch should not in itself create some new problems, should
> it? It should just make a better base to find problems with the fonts
> when using locale
[Philip Blundell]
> You should liaise with Joey Hess. But yes, filing it as a wishlist bug
> seems like a reasonable first step.
OK. I'll give it some more work first.
> You may not want to do all the work needed for these languages, but
> as a minimum you need to make sure that your patch do
[Junichi Uekawa]
> Hmm.. this might cause some problem. Doing it unconditionally might
> cause problem with ja_JP, because on the linux console, you only get
> to see some Greek strings displayed...
Well, it will only cause some problems if it is used for Japanese.
Adding the patch should not in
On Sat, 2002-02-23 at 11:54, Petter Reinholdtsen wrote:
> Here is the patch. Should I register it as a bug against base-config?
You should liaise with Joey Hess. But yes, filing it as a wishlist bug
seems like a reasonable first step.
Also, remember that other changes may be needed to make the
Petter Reinholdtsen <[EMAIL PROTECTED]> cum veritate scripsit:
> Agreed. I ended up making a patch for base-config trying to
> generating the needed locale, and unsetting LANG and LANGUAGE if is
> isn't available. Both LANG and LANGUAGE is needed, to make it
> possible to use a prioritized list
[Phil Blundell]
> It's fairly easy to go in either direction. There's certainly no need
> to pass both of them separately. Either dbootstrap can just write out
> /etc/locale.gen itself, in which case base-config just needs to call
> locale-gen to do the actual generation, or base-config could g
On Fri, 2002-02-15 at 10:35, Petter Reinholdtsen wrote:
> Should the string to put in /etc/locale.gen be passed in as well? It
> is required to generate the valid locale. I'm not sure if it easy to
> guess is string based on the locale, or if it is easy to guess locale
> based on this string.
I
[Michael Bramer]
> btw:
> I have a new DDTS running for the translation of the tasksel
> description file.
>
> Maybe next week we go public and we can start translation this...
Cool. :-)
Is there some document describing the information passed from
boot-floopies to base-config using /ro
[Phil Blundell]
> What about "LANG=de_DE@euro date", does that work?
Yes, it works:
% date
Fri Feb 15 11:13:38 CET 2002
% LANG=de_DE.ISO-8859-15@euro date
Fre Feb 15 11:13:30 CET 2002
% LANG=de_DE@euro date
Fre Feb 15 11:13:35 CET 2002
%
> fr_FR.ISO-8559-1.../usr/share/i18n/loca
On Tue, Feb 12, 2002 at 11:15:37AM +0100, Petter Reinholdtsen wrote:
> [Eduard Bloch]
> > Good question. I though base-config was the only one, but now I have
> > seen that the file is sourced into the base-config's environment.
>
> OK. I want the settings passed on to tasksel and debconf to get
On Wed, 2002-02-13 at 13:01, Petter Reinholdtsen wrote:
>> I have to use the name listed in the LANG variable to get the German
> translation. I can't use any other variation:
>
> % LANG=de_DE.ISO-8859-15@euro date
> Mit Feb 13 13:59:08 CET 2002
> % LANG=de_DE.ISO-8859-15 date
> Wed Feb
On Wed, 2002-02-13 at 12:54, Petter Reinholdtsen wrote:
> [Philip Blundell]
> > I checked these in. But, in fact, I suspect this should probably be
> > "de_DE.ISO-8859-15@euro", and similarly for the other EMU countries.
>
> I guess you mean "[EMAIL PROTECTED]"?
Oh, I thought the character set
[Phil Blundell]
> It doesn't seem to work for me. My /etc/locale.gen includes:
>
> fr_FR ISO-8559-1
> de_DE.ISO-8859-1 ISO-8859-1
>
> If I do "LANG=fr_FR ls --help", I get the French help text; if I do
> "LANG=fr_FR.ISO-8859-1 ls --help", the messages come out in English.
> Conversely, "de_DE"
[Philip Blundell]
> I checked these in. But, in fact, I suspect this should probably be
> "de_DE.ISO-8859-15@euro", and similarly for the other EMU countries.
I guess you mean "[EMAIL PROTECTED]"?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
On Tue, 2002-02-12 at 11:08, Petter Reinholdtsen wrote:
> I found these bugs:
>
> Index: german.src
> ===
> RCS file:
>/cvs/debian-boot/boot-floppies/utilities/dbootstrap/langs/german.src,vretrieving
>revision 1.7
> diff -u -3 -p -
On Tue, 2002-02-12 at 11:08, Petter Reinholdtsen wrote:
> [Phil Blundell]
> > If you are putting "en_US.ISO-8859-1" in $LANG, you need to put
> > "en_US.ISO-8859-1 ISO-8859-1" in /etc/locale.gen. But yes, "." is
> > always the separator for the character set part.
>
> Are you sure? I believe th
[Phil Blundell]
> Some of the language definition files (e.g. german, which I guess Eduard
> was using) just set ->locale to the language code. It does seem like
> these are in error.
> Also, if we can make LANG come out right, I don't think there is any
> need to set LANGUAGE at all. So, to su
On Tue, 2002-02-12 at 10:52, Petter Reinholdtsen wrote:
> I combined and corrected your patch. Here is a better suggestion.
> I'm not sure if the question should be presented at all. If it is
> needed to get the translations working, it should be installed.
Agreed. We should try to avoid askin
[Eduard Bloch]
> I tried this a while ago to install locales. It is broken since I do
> not allocate the string memory correctly, but the basic idea is
> clear.
I combined and corrected your patch. Here is a better suggestion.
I'm not sure if the question should be presented at all. If it is
n
On Tue, 2002-02-12 at 10:32, Petter Reinholdtsen wrote:
> I should suggest using the locale member in 'struct language_item' in
> LANG, and making sure this is a proper locale, and then use the msgcat
> member in LANGUAGE. I do not really understand why perl was
> complaining earlier. If the LAN
On Tue, 2002-02-12 at 10:32, Petter Reinholdtsen wrote:
> I should suggest using the locale member in 'struct language_item' in
> LANG, and making sure this is a proper locale, and then use the msgcat
> member in LANGUAGE.
Yes, that looks like it could work. We could also consider re-enabling
On Tue, 2002-02-12 at 10:32, Petter Reinholdtsen wrote:
> [Philip Blundell]
> > Mistakenly. Feel free to change it back.
>
> I don't have write access to the CVS. I'm not a Debian developer.
Oh, right, sorry. Okay, I'll do this. If you make a patch to add some
appropriate "--include" options
[Philip Blundell]
> Mistakenly. Feel free to change it back.
I don't have write access to the CVS. I'm not a Debian developer.
> Remember that for non-latin languages you will probably have to pull
> in some kind of terminal program as well, e.g. kon2 for Kanji, or
> the resulting translations
[Eduard Bloch]
> Good question. I though base-config was the only one, but now I have
> seen that the file is sourced into the base-config's environment.
OK. I want the settings passed on to tasksel and debconf to get
translated messages there. If the only other program/package is
base-config,
On Mon, 2002-02-11 at 23:46, Petter Reinholdtsen wrote:
> Apparently, someone knew this. I checked the CVS log for
> dbootstrap/util.c, and discovered that user aph inserted
> LANGUAGE= 2001-11-20. Then the user pb changed this to
> LANG= 2002-01-07. This obviously triggered the warning from
>
#include
Petter Reinholdtsen wrote on Tue Feb 12, 2002 um 12:46:38AM:
> There seem to be some confusion. Why was LANGUAGE= changed to LANG=?
>
> Which program is the intended receiver of this value?
Good question. I though base-config was the only one, but now I have
seen that the file is sou
On Tue, Feb 12, 2002 at 12:46:38AM +0100, Petter Reinholdtsen wrote:
> [Petter Reinholdtsen]
> > More testing shows that the LANGUAGE variable can be used when the
> > country is unknown. It only works when the LANG variable is set to an
> > existing locale. The nice ting about the LANGUAGE vari
50 matches
Mail list logo
