WINAMP.COM | Forums - Winamp Translation

WINAMP.COM | Forums : Powered by vBulletin version 2.3.9

WINAMP.COM | Forums > Developer Center > Winamp Development > Winamp Translation

Last Thread Next Thread

Author

Thread

TheSaw
Senior Member

Registered: Apr 2009
From:

Winamp Translation

Hy,
I've been reading some articles about Winamp's translation system, but I need to clarify a few things. Is there some step by step tutorial or something like that to look at, or where should I start?

If I want people to translate my plug-in, can I distribute these .wlz files separately, or do I need to include them in the same package with the whole Winamp translation? Do I include only the stringtable in the resource file, or all the dialogs? Will Winamp load these, or should I load each string separately from the string table?

Quick Link | Report this post to a moderator | IP: Logged

09-19-2009 01:13 PM

Click here to Send TheSaw a Private Message

DrO
Moderator

Registered: Sep 2003
From: UK

http://www.meggamusic.co.uk/winamp/docs/xlat/xlat.html has some information about the wlz format (basically a renamed zip with .lng and other files stored inside it like skins).

the lng file is a resource only dll file with relevant resources in it which are then used (if present vis the look-up process) otherwise the resources are the same as from your plugin dll.

stringtable item 65535 is essentially a basic requirement as an identifier of the plugin for the localisation process. it holds a guid string generated via guidgen. it's best to have a look at an existing .lng file like those from the winamp essentials pack which are generally small scale so easier to look through.

as for distribution, that basically falls on the shoulders of the language pack authors to include the .lng files unless you store them in their own folder (like i used to do with my projects before the Winamp 5.5). if the plugin is good enough or gets the interest from key localisers then you'll tend to find it becomes part of the language pack distribution.

from memory there is enough information in the code examples for using api_language (all of the files should be in place) and it all has relatively easy to use macros for access the different modes as needed.

-daz

__________________
My Plugin Site | Current Plugin Releases | Winamp-en-gb Lang Pack [14/03/2009 (Rev #2)]

Quick Link | Report this post to a moderator | IP: Logged

09-21-2009 07:00 PM

Click here to Send DrO a Private Message

Koopa
Forum King

Registered: Apr 2004
From: DrO's Beta Dungeon

Well, I agree with the above post. If a plug-in is really useful/popular, then there is a good chance, that I'd include it to my wlz file.

I did this in the past too. Good stuff gets attention, this is why most translators already ship Essentials Pack translations in their wlz files.

The WavPack author added a lng based translation too, nearly all language pack authors already ship a translation for the plugin in their wlz file.

quote:
I or do I need to include them in the same package with the whole Winamp translation?

One of the main reasons, why I like the wlz system is, that it's not possible for others to include additional files to the wlz. The language pack author is the driver and has full control over it.

If other translators would add additional files to my wlz file, I would loose any control. Then we cannot talk about a languge pack anymore.

The language packs are one package from one author. The advantage is that all strings harmonies together.

If someone else would add another language file, and may uses different grammar/translations, it wouldn't fit with the rest of the package.

Another issue is, that people would blame the wlz author, if something in the additional file wouldn't fit with the rest of the translation.

You have no clue how many mails I get related to the translation.

Translation is a hard process, different people have different translation styles.

I just can guarantee for a high quality language pack, if I have full control.

You could compare it with skins, I doubt that any skin author would be happy, if other people would patch his skin and add additional stuff.

As for your taskbar plugin, it's very popular (already got a few requests to add it to Essentials Pack) and if you ever decide to use the lng based translation, I'd probably add it to my wlz file too.

-Chris

Quick Link | Report this post to a moderator | IP: Logged

10-23-2009 11:30 AM

Click here to Send Koopa a Private Message

TheSaw
Senior Member

Registered: Apr 2009
From:

Hm, I've managed to look into them at that point, and it didn't seem to hard to do, but wasn't sure if the change (pretty big one, coding-wise) would be worth it. I mean I'm not sure how much would I have to change around... loading the file, shipping the files with the installer etc. It's prolly not that hard, but since I don't know that much about the whole system, I'm a bit skeptical

I'll look into it more and see what's it all about.

__________________
Winamp integration plug-in with Windows 7

Quick Link | Report this post to a moderator | IP: Logged

10-29-2009 02:23 PM

Koopa
Forum King

Registered: Apr 2004
From: DrO's Beta Dungeon

The localized files would be shipped in the wlz files from the translators and not in your installer.

All you have to provide is an English example lng file, which is the fundamental component for other translators. Just to make this clear.

Quick Link | Report this post to a moderator | IP: Logged

10-29-2009 04:55 PM

TheSaw
Senior Member

Registered: Apr 2009
From:

Okay, so what about the existing translations? Can I just convert them to this format, and "someone" will include them in the pack, or the "new" translators will re-translate them?

__________________
Winamp integration plug-in with Windows 7

Quick Link | Report this post to a moderator | IP: Logged

10-29-2009 05:44 PM

Koopa
Forum King

Registered: Apr 2004
From: DrO's Beta Dungeon

Should be possible to convert the strings from your ini based translations to the lng format, since you know, what string is related to which translation string.

Some of your existing translations were already made by official translators. E.g. the Polish Winamp translator made the translation for your plugin.

The big advantage is, that the taskbar plugin translations would perfectly fit with the rest of the Winamp translation.

Quick Link | Report this post to a moderator | IP: Logged

10-29-2009 06:49 PM

TheSaw
Senior Member

Registered: Apr 2009
From:

Okay, I don't have time in the weekend, but I'll look into this next week, and try to convert it to the "official" translation system

Thanks. (I'll ask here if something went wrong :P)

__________________
Winamp integration plug-in with Windows 7

Quick Link | Report this post to a moderator | IP: Logged

10-29-2009 10:00 PM

DrO
Moderator

Registered: Sep 2003
From: UK

there's nothing stopping things being left in an ini file setup (is how my jtfe plugin and few others still are since they pre-dated the 5.5+ WLZ support and i don't have the time/resources to migrate things now). since you could have your code look in the exported language folder (see IPC_GETLANGUAGEPACKINSTANCE) for an 'auto' or some other specifically named file and use that if found otherwise use a custom file as per the user's decision (like the droplist i have in the jtfe plugin).

yes it's nicer to have a proper .lng file (especially when dialogs are concerned) but that can be worked around if using a .ini file setup (as well as having it work correctly with unicode strings).

-daz

__________________
My Plugin Site | Current Plugin Releases | Winamp-en-gb Lang Pack [14/03/2009 (Rev #2)]

Quick Link | Report this post to a moderator | IP: Logged

11-01-2009 10:48 PM

TheSaw
Senior Member

Registered: Apr 2009
From:

Hm, really? Can you elaborate on this? I mean on the "being left in an ini file setup".
For my plug-in the dialog isn't an issue, it's big enough to fit any language I think. Also, the .ini file supports right-to-left languages, the dialog modifies according to that, and full Unicode support.

__________________
Winamp integration plug-in with Windows 7

Quick Link | Report this post to a moderator | IP: Logged

11-02-2009 09:11 PM

Koopa
Forum King

Registered: Apr 2004
From: DrO's Beta Dungeon

I guess he means, that you could add both things.

Leave the current translation files as is and ship all the localization files in installer, like you did in the past.

Additionally you can add wlz based language pack support.

Make that the plugin first checks for a language file in the extracted wlz folder.

So to explain it more simple:

Dro's plugins have a dropdown list. The list shows all available language files.

The language file, which is part of the wlz language packs (extracted in a temp folder) is shown as 'Auto' entry in the dropdown list. The other entries, like e.g. 'Deutsch' are language files, which are part of the Jump to File Extra installer (installed in Winamp program folder).

Jump to File Extra checks, if a jtfe_auto.ini was found in the extracted temp wlz folder. Then it automatically enables the auto mode.

If a wlz doesn't provide a language file, it simply would be English and the user can set the language via the dropdow. list.

I hope I have't confused you.

So 'Auto' and 'Deutsch' could be both German language file. 'Auto' is the file, which comes from my wlz language pack, while 'Deutsch' could come from the German file, you're already shipping in your installer.

Quick Link | Report this post to a moderator | IP: Logged

11-04-2009 10:51 PM

TheSaw
Senior Member

Registered: Apr 2009
From:

Okay, this made it almost clear
So, few more questions left: I load and initialize the service api, and I've found the macros to use to get the strings...
How can I check if a localization was found?
The macros are a bit confusing, which one should I use in which situation? I'm mainly referring to the "need it to fallback to a different module" thingy, and the memory freeing of these strings. Am I responsible for deallocating the memory?

Thanks.

__________________
Winamp integration plug-in with Windows 7

Quick Link | Report this post to a moderator | IP: Logged

11-05-2009 12:25 PM

Koopa
Forum King

Registered: Apr 2004
From: DrO's Beta Dungeon

I hope DrO replies and gives you a better explanation.

In the meantime, you may want to take a look at this:

http://www.hydrogenaudio.org/forums...=64560&st=0

Quick Link | Report this post to a moderator | IP: Logged

11-05-2009 04:44 PM

TheSaw
Senior Member

Registered: Apr 2009
From:

Well you've said in that thread that an .ini file can be a valid language file for the pack. I don't want the translators to modify my dialog, I think it fits the needs of all languages (If not, I'll make changes so it will). If this is the case, will the .ini file strings be accessible through the same language service api? Also, how will it find the correct file, I understood that's done via the 65535 string entry if it were a string resource?

__________________
Winamp integration plug-in with Windows 7

Quick Link | Report this post to a moderator | IP: Logged

11-06-2009 09:31 AM

Koopa
Forum King

Registered: Apr 2004
From: DrO's Beta Dungeon

Yes, the wlz system can use ini files as well. No need to use a lng file. Jump to File, Time Restore and other of DrO's plugins use ini files as well.

The advantage is that you can use both, your current localization files and the 'auto' file, provided from the wlz archive, which will be automatically loaded if it was found.

Sadly, there is no real documentation for developers, which explains the wlz system in general.

For technical infos wait for a reply from DrO, since he did the whole wlz system and he uses the auto mode in some of his plugins too.