Yes, that's the point. I think this would "only" require that each module writer use an external xml file storing all the strings used at screen. As a proof of concept, I can try (I'm just starting to learn Python ;-) to modify one plugin to use this system. For a more general use, a global option (for example LANGUAGE) could be defined in freevo_config.py to automaticaly setup the language used in the whole program.
Comments are welcomed ;-) David Le lun 18/08/2003 à 17:36, Sylvain FABRE a écrit : > I see the point. In fact, maybe we should propose to the devel list a real > multi-language system for Freevo. > > > ok, > > I start to modify the skin but a full localization would require to > > modify python files since only some strings (mainly the ones used for > > the menu) are in XML files. For example, I try to change the "TV Guide" > > string but I have to modify tv.py for that... > > > > Regards, > > ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Freevo-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-users
