Re: Bug#263402: ispell: no default for, "german" or "german -tex" at high priority
On Thu, Aug 19, 2004 at 12:16:47PM +0200, Christian Perrier wrote:
>
> >
> > Sumarizing for them, debian-installer/language possible values were originally
> > single iso-639 two letters language code, but seems that
> > debian-installer/language allows things like the one you used
> > (de_DE:de_DE:de:en_GB:en). Since the code for selection of ispell/wordlist
> > default values expected a single iso-639 two letters language code all the
> > automatic selection process is broken.
>
> Yep, debian-installer/language value now contains what's appropriate
> for the LANGUAGE variable.
>
I agree with that choice. But from the first mails previous to the automation
and also previous to the implementation in debian/installer (see #228837)
I understood that the most probable choice was it to contain the two letters
code and thought that everything else was derived from
debian-installer/{language,country} values, and wrote the code for it. But as
written there, that was still a moving target in debian-installer at that time.
Unfortunately I had no time to take a look later at the debian-instaler internals
or to make a run on it. I am also very surprised that nobody else realised about
this earlier.
And of course, current debian-installer settings are more versatile and
what they must be (somebody can select DE as country and de_CH as language,
what otherwise would not be possible).
> If you need to get the user's language, you should either get the
> value from the LANG variable, or grab debian-installer/language and
> then "cut -f1 -d: | cut -f1 -d_"
>
Is perl,
($language,$country) = split("_",( split(":",$language) )[0]);
with $language originally the value of debian-installer/language. I do not
know if language values without country suffix are possible, but just in
case, the value of debian-installer/country is used if $country is void after
that.
That is in short the fix I have ready pending of more testing. All the other
attempts with close values if no exact match is found were already done in
dictionaries-common.config.
Cheers,
--
Agustin
Reply to: