[Bashburn-info] Fw: Something funky in the config menu

[Nick W. <ni...@li...>]

Begin forwarded message:

Date: Thu, 25 Sep 2008 22:01:06 +0100
From: Nick Warne <ni...@li...>
To: "Steven W. Orr" <st...@sy...>
Cc: bashburn <Bas...@li...>
Subject: Re: [Bashburn-info] Something funky in the config menu


On Thu, 25 Sep 2008 10:56:12 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:

> Nick, Maybe I'm not getting it. I sense that CTH.lang is used as a
> stopgap to provide in case a language is not supported. But if we're
> in Swahili and the language is not supported then we should default
> to English instead of creating a copy of an English language file. At
> the most, we should be looking to see in BBLANG is in the set of
> supported languages and if it's not then set it to English. Yes? No?

Yes and no.  Look at the lang/Italian/configure.lang file (e.g.)

It does not HAVE the $VARs associated with the help file, whether it is
in Swahili, Klingon, or any other language.  If the $VARs do not exist,
then nothing gets sourced and no help text when it that language.

The rest of the file[s] for menu etc. work OK...  so it cannot just be
reverted to English as default - just the 'not updated' variables in
these files. 

Nick
-- 
Free Software Foundation Associate Member 5508

-- 
Free Software Foundation Associate Member 5508