[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Language fall-back
From:       Eduard Werner <edi.werner () gmx ! de>
Date:       2004-05-15 18:23:44
Message-ID: 200405152023.44754.edi.werner () gmx ! de
[Download RAW message or body]

Sobotu 15 meje 200420:26, Nicolas Goutte pisaše:
> On Saturday 15 May 2004 16:49, Eduard Werner wrote:
> > Sobotu 15 meje 200415:12, Heiko Evermann pisaše:
> > > Think about the alternative: load the catalogs for all the languages
> > > that the user chose in kcontrol, and the user can choose what he gets
> > > to see. If he likes English, he can just choose one (his) language and
> > > English. But if he doesn't, he can pick any other language to fill in
> > > the gaps of his favourite translation. I guess, it might not even be
> > > too difficult to implement that?
> >
> > I don't know. It will definitely make KDE a bit slower. Maybe when the
> > language settings get changed a new .mo-file could be generated
> > containing all the strings in all the languages you want for every
> > program (I guess msgmerge could already do that). The language settings
> > of a user would then result in a virtual "user language". That way KDE
> > wouldn't have to load several language catalogs.
>
> But users get only .po files shipped, not the .mo ones.
>
> Then you would also to have to "compile" the .mo files in .po (or without
> .mo files, uncompile, merge, re-compile.)

If you only get *.po-files shipped you have to compile them anyway, since KDE 
reads the *.mo-files.

My idea was that this would be done when selecting the GUI languages by 
merging all the languages you select into one.

Cheers

Edi

[prev in list] [next in list] [prev in thread] [next in thread]