Re: [Mplayerplug-in-devel] Status and are we about ready to release?

[Anders L. <li...@io...>]

Hi again

Typically I just find some nonsense when I pressed send, sorry.

ons, 03 08 2005 kl. 03:06 +0200, skrev Anders Lind:
> Hi
> 
> Sorry I really did not have a lot of time today ;)
> 
> First let us agree on what we want.
> Solution 1:
> Do we want that mplayerplug-in automatically adjusts the language based
> on the language and country parameters the user logged into the system
> with and falls back to the default languange the program has been
> programmed in like English if the native language of the user is not
> (yet) supported by mplayerplug-in?
> 
> Solution 2:
> Or do we wish the user to have the opertunity to:
> 1. set a wished languange
> 2. set a fall back language
> 3. and a system fall back language that mplayerplug-in falls back to
> 
> E.g.
> 1. Dutch
> 2. German (The Dutch guy may prefer German over English)
> 3. system fall back languange is English because of the author (Kevin)
> 
> Solution 1 is Solution 2 without part 2 and without user interaction
> regarding configuration.
> 
> Solution 2 could be set to the language based on the current user
> profile when the user first runs mplayerplug-in and the user may
> afterwards be allowed change each of the first two options of Solution 2
> in e.g. the configuration file.
> 
> As of now each of the language files of mplayerpluig-in is stored in
> e.g. Debian like this:
> for each supported language we
> have /usr/share/locale/<language>/LC_MESSAGES/mplayerplug-in.mo
> 
> We either have to store the language files where they are now and we can
> skip bindtextdomain. textdomain is in my understanding only needed if we
> change domain within the program (meaning how we choose a translation
> from the original language and to say German. E.g. Cat becomes in one
> domain to "Katze" and in another to "Der kleine Garfield" - well silly
> example :) )
> 
> If we want mplayerplug-in to automatically choose (solution 1) we go for
> only bind_textdomain_codeset I think.
> 
> If we want the user to choose and/or perhaps have user chosen fall back
> language we need bindtextdomain like bindtextdomain("mplayerplug-in",
> "/usr/share/locale"); (the rest of the directory and the language file
> in particular is determined automatically by gettext I
> think, /<language>/LC_MESSAGES/mplayerplug-in).
> An arbitrary directory for the language files is allowed(!) according to
> the gnu site so it does not need to be /usr/share/locale in particular.
> 
I only see the importance of using bindtextdomain if we place the
language files in another place than the default system place like on
Debian:
/usr/share/locale

The chosen language is not chosen by bindtextdomain, but on whether we
manage to set the LANGUAGE environment variable in the right way like
stated just below this line.
> The question is can we avoid using the LANGUAGE environment variable to
> specify a colonseparated list of wished languages or can we specify
> LANGUAGE inside mplayerplug-in when we read the configuration file?
> And related to this: Is there a setenv (or export) specific feature in C
> to set the LANGUAGE environment variable with ?
> For reference see:
> http://www.gnu.org/software/libc/manual/html_node/Using-gettextized-software.html#Using-gettextized-software
> 
> I can't see why textdomain should be used at all if we do not change
> domain.
> 
> And I guess we skip the plural support as of now. Can't see the use of
> it as of now we the relative simple texts we have.
> 
> It is easier if we know which solution we go for - which do you choose
> Kevin, how advanced do we need to be? :)
> 
> 
> Cheers
> 
> Anders

Bye for tonight :)

Anders