Translation files are hosted and managed on the Transifex website. Get an account and help to translate to your language! If your language is missing, just head over to Transifex and request a new language.
Text length: The translations for many languages frequently exceed the length of the corresponding English source. It could be a problem for the layout of graphical components (e.g. buttons). Some elements have a character limit on the translation tool.
Special characters: Some characters representing values (%d, %s), newline (\n) and HTML tags must not be translated. For other translating recommendations, see Transifex help
For special words or particular contexts look at the “Instructions” text box (gives explanations or definitions).
weasis-i18n is the internationalization project (i18n) of Weasis. As a separate project, it can have its own release cycle. The OSGi fragments of plug-ins contain only the translation files which are merged during runtime to the matching module of the application.
To obtain daily built packages, see this page .
That means the translation packages can be deployed at any time, it does not need to follow the Weasis life cycle. With remote packages, the plug-in translation will be updated by Weasis only if the timestamp number has changed. This timestamp is set during the build phase described below.
Additional projects to obtain a full translation of Weasis:
The java-swing-dialogs translations must be updated manually in the weasis-launcher module and docking-frames translations must be packaged witin the library.
- JDK 11 or higher
- Maven 3 or higher
If your computer is behind a proxy server, configure maven .
- Git or directly download the source code from GitHub
Getting the Source
To clone the repository, first install GIT and either clone using a graphical GIT client (such as Tortoise Git) or directly from the command line using the command:
$ git clone https://github.com/nroduit/weasis-i18n.git
Build the distribution
Go in the weasis-i18n directory, Compile and install all the plug-ins in the local Maven repository
$ mvn clean install -Dtransifex.token="<your-token>"
All the APIs require to be authenticated. So the value “your-token” must be replaced by your generate token, see how to get this token on Transifex.
Command if you are behind a proxy server:
$ mvn clean install -DproxySet=true -DproxyHost="host" -DproxyPort="port" -Dtransifex.token="<your-token>"
The distribution files are located in the weasis-i18n-dist/target/dist folder.
Apply the translations
The translation package can be built manually as described below or it is automatically built every 24 hours and can be downloaded from here . When Building Weasis , the last package is downloaded automatically.
- In order to update Weasis with new translations, unzip weasis-i18n.zip and either:
- Pass the weasis.i18n location into the launch command
$weasis:config pro="weasis.i18n <your-uri>" $weasis:config pro="weasis.i18n file:/home/weasis-i18n-dist-4.0.0-SNAPSHOT" $weasis:config pro="weasis.i18n https://<your-domain>/weasis-i18n-dist-4.0.0"
- Replace the files in the “bundle-i18n” folder where Weasis is installed (not possible when Weasis is distributed from an application store or the Mac signed package).
- Pass the weasis.i18n location into the launch command :
weasis-launcher-i18n cannot be updated dynamically as the launcher is not an OSGi module. It must be imported manually into the Weasis source (weasis-launcher).