[MPlayer-dev-eng] userfriendly release? don't flame...

[Alex Beregszaszi]

Hi,

> > > - update help_*.h files to contain new warning/error messages over the
> > >   source - or maybe switch to the gnu localization stuff?
> > 
> > This would really help the translaters (like me :)). Maybe even the
> > developers, since they don't have to bother so much about the translation 
> > ...
> > If a language doesn't have a definition it just falls back to english for 
> > only that!
> > Also this would allow usage of several languges after install so no 
> > recompile :) Put this in the binary packages perspective.
> 
> Yes, I've heard lots of goods about this stuff. And experienecd just the bad
> sides... so, could you or someone else show me an code example, how does it
> looks like? I mean which libs are required, how are translations handled
> (separate binary data files? compiled-in?) and how does the printf() looks
> like in the source when using it. How portable (including solaris, os/2,
> etc)

I've never coded i18n, but as i saw in many projects i think the only
one thing is the gettext() call.

Yes, this requests to get all the printf's to replaced by mp_msg if you
want to make the way open to translate them too.

And for the messages that arent translated, the original message will be
displayed - in the binary the original messages will be compiled and
they will be runtime parsed.

I think inserting gettext() into mp_msg_c should do the work.
(Yes, by gnu i18n you write messages as you want (e.g. in english) and
order the messages to id's in seperate files and for the translates
you need to order to the id's to the foreign languages - hmm, this id
stuff could be cropped out, but i think it makes things easier - or not :)

Also Arpi, if you want ( ;)) I could have a look at i18n and make a patch.

Ahh, sorry for this mail, i'm bit drunken :)

-
alex