I am trying to translate a French Module to English using an extension since I don’t maintain the main module. I have no trouble adding features to the module using an extension ( new boards, pieces, etc ). however, when I try to do an extension that only does a translation it seems to be ignored. I see it getting loaded, but it has no effect.
If I put the translation in the main module, I can see it working.
Are there any tricks to getting translation working as an extension?
I ran it again in player mode after making sure that I had the French-to-English translations in the extension.
I can see the extension loading, but the names of the player sides and the tool bar button text is still coming up in French.
It’s like the translation isn’t taking. I’m not getting any errors in the chat window:
Race for the Galaxy version v3.0 designed by Soft-bug from VassalForge.org
Extension Race_Galaxy_v3_english v3.0e loaded
Extension Race_Galaxy_v3_solo v3.0e loaded
I am using the “Race for the Galaxy” module posted in the modules area and added a new extension for an English translation.
If I make the translation in the module itself, I can see the English.
Are there any special settings in Vassal or the main module you have to set to enable translations? ( I’m using the 3.1.0 )
This makes a translation thar works ONLY if your Regional and Language Settings is set to exactly English (United States), it won’t work for English (Australia), English (Belize), etc.
This will nearly always be what you want, it creates a translation that is invokes as long as the Language is set to English, regardless of the Country option.
I’m wondering if country specific translations is actually warranted for Vassal?
I don’t see any reason to prevent it, though. If somebody really wants
“colour” instead of “color”, then that should be something they can
make a country-specific translation for.
It’s a question of whether the convenience of having “colour” instead of “color” outweighs the potential for confusion that we’re seeing in this thread.
This isn’t Country specific though but dialect specific. Maybe the options should just reflect those instead of the countries. It would cut the selection list down dramatically
It’s a question of whether the convenience of having “colour” instead of “color” outweighs the potential for confusion that we’re seeing in this thread.
What I see here is that the way we do fall-back for country-specific
translations is broken, not that there’s anything wrong with having
country-specific translations.
We already have it so that if language LL isn’t avilable, then you get
the default English translation. Why can’t we make LL_cc default to LL
if LL_cc isn’t available?
I think you misunderstand something here. Nothing is broken.
It does.
The problem here is that the user created LL_cc, but no LL, and his Locale was actually LL_xx. Java went to fall back to LL, but it did not exist, so it fell through to the source language of the the module, which is French.
The user never wanted to create LL_cc, he actually wanted to create LL. I would argue that all users only want to create LL.
I see. I didn’t understand the problem. Could we instead prevent the creation
of LL_cc if there is no LL? (Or suggest to the user on selection of LL_cc
that he create LL instead, if it doesn’t exist? Or automatically create LL
from LL_cc if there is not already an LL when LL_cc is created?)
The options reflect the options available in Java Locale settings, I’m not about to start making up a scheme to replace this.
Java Locale’s are made up of 2 parts - Major part is language, Minor part is country.
The country setting is primarily used for things like date format, currency symbol and number display formats, that can vary wildly between different countries using the same language.
Realistically, will anybody care if there is only one English translation available for American-based and English-based spelling using countries? Given that to actually get this to work, you would have to include not just 2 translations, but many, 1 for each country that does not follow the spelling scheme of the main translation.
Is there a reasonable example in other languages where country-based translations is needed (French comes to mind being so widely spoken)?
Otherwise, I think it is one of these ‘nice’ extra features that just serves to cause confusion and will never actually be used, except in error.