Loggytronic Forum

VOMP => VOMP General / MVP => Topic started by: Schnurps on August 01, 2005, 00:56:36

Title: Translations
Post by: Schnurps on August 01, 2005, 00:56:36
Hi Chris,

your project looks really promising.
If it is in a bit more stable stage, I will really like use it for my family's MediaMVPs. :-)

It would be great when the interface could be translated in German. Have you schelduled multi-lingual support?
Perhaps I could do the translation to German, if you agree.

Schnurps
Title: Re: Translations
Post by: Chris on August 01, 2005, 18:25:05
Hi, I like the idea but I have to say I am a bit clueless on how best to write multilingual programs. I suppose vomp won't be too bad because there aren't that many words. I hadn't really considered it too much yet since it is all so alpha at the moment. When I come up with a way of doing it then certainly you can do the translation :)

Chris
Title: Re: Translations
Post by: davep on August 01, 2005, 19:02:28
Look in i18n.c in vdr for one way to do it. Basically that file contains the English version of every string output by vdr together with the translations in the different supported languages. When a text string needs to go to the user it passes through a translate function which identifies the English string and replaces it with the non-English equivalent. The PLUGINS.html file explains how a plugin can add its own strings to the translation system, and the plugin version of mediamvp uses this.

However I believe all of the user interaction within vomp is done by the client, ie all the text is included in dongle.bin, so the client would need to have its own implementation. That raises the question of how much space is there in the MVP memory? If space gets tight it might be necessary to create different dongle files for the different languages (ie one translation per file) or to do things an entirely different way.

Dave
Title: Re: Translations
Post by: Schnurps on September 07, 2005, 22:24:21
I addet this as a feature request on the sourceforge site.
It's at the moment surely not the most important feature request, but so it is kept in view for further releases...

Schnurps
Title: Re: Translations
Post by: Chris on September 07, 2005, 22:32:57
Yes, actually I've just had an email from Dave about this. I am currently planning a bit of a GUI rewrite, so I don't want anyone to waste time in the code at the moment, but after that I think we should all plan a translation system for it.
Title: Re: Translations
Post by: davep on September 13, 2005, 16:51:13
Yes I'm looking at the i18n stuff, and the code is coming along nicely.

Dave
Title: Re: Translations
Post by: Chris on September 13, 2005, 17:28:40
dave, I committed a large chunk of the gui rewrite last night, I don't think it will drastically affect any translation stuff but there might be some cvs conflicts. Just to let you know..

BTW, the gui rewrite isn't finished, it's just in an intermediate working stage :)
Title: Re: Translations
Post by: davep on September 14, 2005, 18:44:56
No problem. Incidentally have you spotted that on the current CVS the 'welcome' screen is never redrawn, so the clock remains frozen at the time the MVP was booted?

Dave
Title: Re: Translations
Post by: Chris on September 14, 2005, 18:58:38
Yeah. I left that because I need some timed event system to run the clock, and then it needs to work out whether that area of the welcome screen is the top most box, etc etc, blah blah. I shelved it until at least after this gui rewrite - as there is now at least real memory allocated for each window. I still need some z-order code and an event system though. Rather complicated for just a clock!