When trying to export XLIFF for my development language there is no way to include translations.
I have a development language set to Czech like this
When I want to export existing translations for Czech - there is no checkbox for that
I can select 'Development Language Only' but it does not give me current translations I already have in Localizable.strings (Czech).
Everything is working fine for Slovak though. I also want to have Czech language to be a default one for English, France etc. That's why I set it up as a development language.
Related
I have localized my Xcode project with 2 languages:
English - (developer language)
German
I have translated every Text in the User interface formatted like:
BUTTON_UPLOAD
ALERT_MESSAGE_WRONG_PASSWORD
I call these TOKENS.
My aim:
I want to export these TOKENS in XLIFF for English translation like
"BUTTON_Upload" = "Upload" (I know that this is not the XLIFF Format, It's just for demonstrating)
But the problem what I have is now, is that I only can translate
English -> German
But actually it is
TOKEN Language -> German
My aim is
TOKEN LANGUAGE -> English
TOKEN LANGUAGE -> GERMAN
Is there another instead of using any foreign language what I will never use as a PSEUDO_LANGUAGE?
With the command:
xcodebuild -exportLocalizations -localizationPath . -project "YourProject.xcodeproj" -exportLanguage en
you can set the target language and then its working.
I thank myself :-)
So I understand how Multilingual App Toolkit 4.0 works and it works great for my Xamarin.Android project. The default language is English, and with MAT we've translated it to Dutch and German.
Then comes the translator along and asks about how to make changes to the English texts, which is my source texts and the basis of all translations. The source texts (English) are in a file Resources\values\Strings.xml. Alter a string there, would invalidate all translations (Dutch and German).
Besides invalidation, I can't send my translator the normal .xlf file, because all source texts are in the Strings.xml file.
So my question is, how can my translator alter the source language texts in the most easy way (preferably with an .xlf file)?
The short answer is that you can't. The design of the Multilingual App Toolkit focused on providing easy support for translation into other languages. The concept of providing source content editing was not considered.
That said, as a workaround you could add another variant of English. For Android apps, the default is English Neutral (en), so adding en-US or en-UK would create the XLIFF file that your translator / proofer could edit using the same tooling (e.g.: Multilingual Editor) to provide source content proofing. If using the same translator for proofing and translating, they could apply the translation based on the update English string to the Dutch and German files.
When you receive the XLF files back ensure all the resource in the proofing English XLF (e.g.: en-US) are marked as need review, translated or final (basically anything except 'New'). The reason is that the Multilingual App Toolkit does not include untranslated resource in the generated target resource file. (The reason is for language fallback purposes in Windows apps).
Now you can import the proofed English file with the other XLF file and build. Copy the entire contents from the proofed English resource file(s) overtop the original source files (recommend Comparing first). When you next build, you will receive warnings that the source resources have changed after the translation, but you can just review and clear those warning in the editor, or clear them globally within the Visual Studio IDE.
I've added english language to my app written originally in polish, set the default language to en-us but for some reason people from non-english speaking countries still get the polish translation, any ideas?
You have to modify the project file manually:
<PropertyGroup>
<SupportedCultures>en;pl</SupportedCultures>
You don't have to add your default language to SupportedCultures
Our Cake 1.3 php site is coded with English as the default language. On the front page we have a Spanish and Brazillian flag which is used to translate the site into the desired language via the use of .po files. When the flags are sued there is no problem with translations.
However we have found that when we use a Spanish version of Firefox to look directly at the site we see the brazilian text! I would have expected to see the English text or maybe even the browsers attempt to translate into Spanish.
Our Locale folder is structured as follows:
Locale
Por
LC_MESSAGES
default.po
Spa
LC_MESSAGES
default.po
Aprt from the obvious error of Spanish visitors to the site seeing Portugese this also leads to any sign ups that are done to be registered as an English sign up which is causing us a real head ache in the admin.
Is the Spanish firefox just picking the first translation file it sees? If so how do we stop this and either get it to use the correct version or, as I suspect it should be doing, show the english text thus making it obvious to press the Spanish flag.
Any help or advise would be appreciated.
Although I have created a resource file for simplified chinese AppResources.zh-CH.resx, and i have added it in the supported culture in the csproj, the chinese text is not displayed. Instead the default english text is shown when i change the language to simplified chinese.
Though those text such as the month name which is obtained from the WP OS is shown in chinese.
The other languages such as spanish and german works like a charm. I have created the generic german and spanish( AppResources.de.resx, and AppResources.es.resx)
Am i missing? Do i have to make changes for any other changes for chinese?
Your entering the wrong (unsupported) culture for in the supported culture.
Please check the following link for the supported language and culture.