Currently BlogBridge comes in two languages that we personally maintain: English and Russian. However, we encourage and support everyone who wishes to contribute the translation in any other language. By doing so, you help your fellow citizens not knowing any of the two standard languages to enjoy our product.
You can become a maintainer of the translation and provide the updates as we add new features, or you can provide only up-to-date version and let someone else update it later. Both ways hold immense value to us and our users, so don’t worry if you don’t have time for continued support. Help us by doing that you really can and enjoy what you do!
What is translatable?
- every message (except new functions in weekly builds)
- command names
- help screens
- tool tips
- everything else
How to translate?
We are constantly looking for ways to make the translation of the application easier and accessible. This document describes an improved and simplified way of translation compared to what it was before, requiring to download and install BlogBridge from the source code.
With the powerful plug-in architecture you now can package a translation as an external plug-in package and attach it to the application to get the language you want. Yes, it’s that easy.
How to create a translation?
- Find blogbridge.jar that belongs to the BlogBridge application on your disk
- Copy blogbridge.jar to blogbridge.zip and extract these two files:
- Action.properties — commands, help strings, tool-tips
- Strings.properties — dialog boxes, alerts, other text messages
- Now download and start Attesoro (http://attesoro.org/download.html) translation tool.
- Open the Action.properties file you extracted in the step 2 with Attesoro and create a new locale with Edit / Locale / New… (choose your language and the country)
- Select it in the tree in the top-left corner of the screen. You can see that all keys in the list below became blue, which means that none of them have translation for the selected language / locale. Your goal now is to walk through as many “.label”, “.helptext” and “.tooltip” keys as you can / wish and provide the translation to the messages they show in English.
- After you finished with Actions, save the results and continue with Strings.properties. The keys in that bundle have no suffixes and you can translate as many of them as you like.
- In command labels, you can use ampersand (&) to indicate a character to underline
- If you need a “…” character, use “\u2026″ instead of three periods
- Note that sometimes it isn’t clear how a message should be translated and what the correct tense is. In this case you’d better find where it’s shown in the application and see how it would sound naturally.
- Keep in mind that some terms “feed”, “reading list”, “guide” may need no translation. If your language has no equivalents, it’s better to leave the original spelling for them.
When you save your work in Attesoro, it creates new files with the same name, but with language suffixes (like Actions_ru.properties for Russian). These are the files you will need to distribute.
How to see the results?
So you have your translations in two files “Action_xx_yy.properties” and “Strings_xx_yy.properties”. Now you can check the results in BlogBridge. For this:
- Find the working folder of BlogBridge (
/.bb/final or /.bb/weekly depending on the version you use)
- Create “mytranslation” under the “plugins” folder there.
- Copy your translation files inside the new folder.
- Create the “package.xml” with the following contents:
<package name="<language> Translation" description="Translates BlogBridge into <language>" version="1.0" author="<your name>" email="<your address>"> <actions bundle="Action_xx_yy" type="Commands in <language>"/> <strings bundle="Strings_xx_yy" type="Text messages in <language>"/> </package>
Note: You need to replace <language>, <your name>, <your address> and bundle names with your specific values.
- Now you can start BlogBridge, open the Plug-ins manager, tick your plug-in package and restart to make it active.
- Upon restart, you should see the changes in text messages.
Note: Once you enabled the plug-in, you need to restart BlogBridge only once every time you change something in the translation files to let the application grab the changes.
What and where to send?
At this stage you have two translation files, the package.xml file and complete satisfaction with the results. Now how to prepare the package for distribution:
- Check that package.xml has all info about you and the package.
- Check the spelling of your translation. I know, I know, but I still find many errors in my spelling there in the files.
- Create a ZIP archive with your translation. There should be just three files, no folders, no other stuff. It’s the easiest way to make it, believe me.
- Try your new package by placing it in the “plugins” folder. Don’t forget to move the “mytranslation” folder out of the “plugins” to let BB find the right package.
Are you satisfied with the results? Send this ZIP package to us for review and publication!