- This topic has 15 replies, 3 voices, and was last updated 1 year, 5 months ago by
.
-
Posts
-
@Mikhail I can speak Japanese 😀
A modified XML Content Translator for SCADA 6:
https://drive.google.com/file/d/1gDzsxNPvpC2uhSiWt9Rwitm_eEcCA8JU/previewDownload XML Content Translator for SCADA 6:
https://github.com/kumajaya/XmlContentTranslator/releases/download/1.11.1/XmlContentTranslator.zip…and be happy translate SCADA 6 to your own language!
Support both SCADA 5 and 6 language files:
https://github.com/kumajaya/XmlContentTranslator/releases/download/1.11.2/XmlContentTranslator.zipHi,
Xml Content Translator may be quite useful to create automatic translations to many languages.What are the differences between source and modified Xml Content Translator?
Do you know if this app uses external or internal engine for translation?
Is it possible to translate, for example, ScadaWeb.en-GB.xml by a few clicks?Hi, Xml Content Translator use Google translate API to automate translate base language to target language. Even the translation results not always perfect but quite useful to speed up translation task, we can manually review and edit the results directly on the application after. This app can track online base language and sync to our translation target locally, remove the missing content and add the new one. You can continue to update the base language as you need and I can start translate it right now.
Original app show all Xml node attributes as translation base, not as we expected and can’t translate multi line words. That’s why a modification needed.
To support language auto detection, we need to add language information to xml base like this:
<?xml version=”1.0″ encoding=”utf-8″ ?>
<ScadaDictionaries name=”English”>
<General>
<Culture>en-GB</Culture>
</General>
<!– ScadaCommon.dll –>
<Dictionary key=”Scada.Application”>
<Phrase key=”ProductName”>Rapid SCADA</Phrase>
<Phrase key=”ServerAppName”>Server</Phrase>
<Phrase key=”CommAppName”>Communicator</Phrase>
.
.
</ScadaDictionaries>And you can make a statement, SCADA 6 will ready with almost perfect bahasa Indonesia user interface 😀
Unmodified vs modified Xml Content Translator:
https://drive.google.com/file/d/11wvlILgn69QzILmo7sKf57SBgPt7KHc9/preview
Sorry, the correct one:
<?xml version=”1.0″ encoding=”utf-8″ ?>
<ScadaDictionaries name=”English”>
<General>
<CultureName>en-GB</CultureName>
</General>
<!– ScadaCommon.dll –>
<Dictionary key=”Scada.Application”>
<Phrase key=”ProductName”>Rapid SCADA</Phrase>
<Phrase key=”ServerAppName”>Server</Phrase>
<Phrase key=”CommAppName”>Communicator</Phrase>
.
.
</ScadaDictionaries>> ScadaDictionaries name=”English”
I’m not ready to add a new attribute in language files right now. May be it’s possible to use English source by default.> SCADA 6 will ready with almost perfect bahasa Indonesia user interface
Cool! Have you used the latest files from GitHub?
Would you pull the v6 translation to GutHub?Thanks a lot for the idea about XML Content Translator! We can create machine translations for the most popular languages. They can be used as a base for human translations.
My modified Xml Content Translator always sync to github for base language 😀 A complete SCADA 6 xml language raw url included. Yes, I’ll make a pull request for Indonesian language support.
Yes, I’ll make a pull request for Indonesian language support.
The pull request has been merged. Thank you! I also asked you for some changes in the pull request comments.
Is it possible to use Xml Content Translator for update language files if phrases were added/changed/deleted?
Xct will remove no existence key, add a new key with a pink background cell (a mark for empty translation), but can’t detect content changes.
I’m doing a content translation for Chinese Simplified, thank you
https://github.com/geffzhang/scada-v6/tree/ChineseSimplifiedLangPack/LangPack/ChineseSimplified
- You must be logged in to reply to this topic.