The VideoLAN Forums

- Swithch interface to Skins 2
- assuming the application does not crashes or becomes locked , right click on a blank portion of the buttons pannel
- Select skin -> it shows two positions, "default" and "Open skin..."

The "default" string has either no msgid/msgstr correspondence, or the program is not able to point correctly to the translation. There is a string
#: modules/audio_output/alsa.c:84 msgid "default"
which apparently belongs to other menu item.

Cristi

"default" is actually the name of the default skin, and should probably not be translated.
This name is retrieved from the skin file itself (actually, if you have several skins installed, you will have several other names in the list).

Hm, interesting. Strange for a name, though.

As for "and should probably not be translated", I think I disagree. This decision should be left to the skin author, assuming it is technically possible for him to define translated names for his skin.

Just an example, which is only half a good example here: Opera browser comes by default with two skins, one Opera Standard and another Windows Native / Macintosh Native (this depends on the OS). These two skins have their own translation ID in the Opera language file, so these can be (and actually are) translated in Opera menus. As for other external installable skins, the actual skin name is given by the filename which contain the skin (a .zip file), so these can only be translated by renaming the filename itself. The installable skins are stored in per-user basis locations, so the skin name can be also established on a per-user basis.

Cristi

A skin being a zip or tar.gz file, it is always possible to extract the XML file, modify the skin name, rezip and change the extension to be .vlt. Even if it is less convenient than renaming the skin file, it allows the same things as what you described for Opera.

BTW, if you want to translate the name of the skin, why not translating several other parts of the skin as well? For example, the Text control allows to display some text, which should most of the time be translated. The skin author is free to use the strings (s)he wants and I don't see any way, technically speaking, to provide a translation for these strings, other than letting the user change them manually (which is already possible as explained above).

And I'm not talking about the strings that might be embedded in the images of the skin

there are words for default in other languages you know...