mirror of
https://github.com/LaCasemate/fab-manager.git
synced 2024-12-03 14:24:23 +01:00
100 lines
6.1 KiB
Markdown
100 lines
6.1 KiB
Markdown
# Fab-Manager translation documentation
|
|
|
|
This document will explain you what you need to know to contribute to the translation process of Fab-Manager.
|
|
|
|
##### Table of contents
|
|
|
|
1. [Translation](#translation)<br/>
|
|
1.1. [Using a TMS](#using-a-tms)<br/>
|
|
1.2. [Using In-Context translation](#using-in-context-translation)<br/>
|
|
1.3. [From the files](#from-the-files)<br/>
|
|
1.3.1 [Front-end translations](#i18n-translation-front)<br/>
|
|
1.3.2 [Back-end translations](#i18n-translation-back)
|
|
2. [Configuration](#configuration)<br/>
|
|
2.1. [Settings](#settings)<br/>
|
|
2.2. [Applying changes](#applying-changes)
|
|
|
|
<a name="translation"></a>
|
|
## Translation
|
|
|
|
<a name="using-a-tms"></a>
|
|
### Using a TMS
|
|
We use [Crowdin](https://www.crowdin.com), a translation management system (TMS) to simplify translator's job in fab-manager.
|
|
You can access it at [translate.fab-manager.com](https://translate.fab-manager.com) and start translating to one of the already configured languages.
|
|
If you want to translate Fab-Manager to a new language, just send us an email to [contact@fab-manager.com](mailto:contact@fab-manager.com) and we'll add this new language to the TMS.
|
|
|
|
<a name="using-in-context-translation"></a>
|
|
### Using In-Context translation
|
|
To translate the front-end application (angularJS client), and the notifications, you can use [Crowdin In-Context](https://crowdin.com/page/in-context-localization).
|
|
This allows you to use Fab-Manager as normally, but with the addition of small "edit" icons on the top-left corner of each text blocs.
|
|
Clicking on this "edit" icon will open the Crowdin translation interface and you'll be able to translate or modify existing translations directly.
|
|
You can access it at [in-context.translate.fab-manager.com](https://in-context.translate.fab-manager.com/).
|
|
|
|
<a name="from-the-files"></a>
|
|
### From the files
|
|
If you don't wan't want to use the TMS, you can write translations with in the source files.
|
|
This is more complicated and you must know what you're doing.
|
|
Please prefer the [TMS method](#using-a-tms) if your're not familiar with software development.
|
|
|
|
First, consider that it can be a good idea to setup a development environment to contribute to the software translation.
|
|
This is not mandatory, but this will allow you to test your changes in context and see if anything went wrong, especially with the special syntaxes.
|
|
Please refer to the [development readme](development_readme.md) or to the [virtual machine instructions](virtual-machine.md) to setup such an environment.
|
|
|
|
Once done, check the files located in `config/locales`:
|
|
|
|
- Front app translations (angular.js) are located in `config/locales/app.scope.XX.yml`.
|
|
Where scope has one the following meaning :
|
|
- admin: translations of the administrator views (manage and configure the FabLab).
|
|
- logged: translations of the end-user's views accessible only to connected users.
|
|
- public: translation of end-user's views publicly accessible to anyone.
|
|
- shared: translations shared by many views (like forms or buttons).
|
|
- Back app translations (Ruby on Rails) are located in `config/locales/XX.yml`.
|
|
- Emails translations are located in `config/locales/mails.XX.yml`.
|
|
- Messages related to the authentication system are located in `config/locales/devise.XX.yml`.
|
|
|
|
If you plan to translate the application to a new locale, please consider that the reference translation is French.
|
|
Indeed, in some cases, the English texts/sentences can seems confuse or lack of context as they were originally translated from French.
|
|
|
|
To prevent syntax mistakes while translating locale files, we **STRONGLY advise** you to use a text editor which support syntax coloration for YML and Ruby.
|
|
As an example, [Visual Studio Code](https://code.visualstudio.com/), with the [Ruby extension](https://marketplace.visualstudio.com/items?itemName=rebornix.Ruby) and the [YAML extension](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml) will do the job.
|
|
|
|
<a name="i18n-translation-front"></a>
|
|
#### Front-end translations
|
|
|
|
Front-end translations uses [angular-translate](http://angular-translate.github.io) with interpolations interpreted by [MessageFormat](https://github.com/SlexAxton/messageformat.js/).
|
|
**Please read the documentation about the [ICU MessageFormat syntax](http://userguide.icu-project.org/formatparse/messages#TOC-MessageFormat) before translating.**
|
|
|
|
Anyway, it is strongly recommended to use our [translation management system](https://translate.fab-manager.com/).
|
|
|
|
<a name="i18n-translation-back"></a>
|
|
#### Back-end translations
|
|
|
|
Back-end translations uses the [Ruby on Rails syntax](http://guides.rubyonrails.org/i18n.html) but some complex interpolations are interpreted by [MessageFormat](https://github.com/format-message/message-format-rb) and are marked as it in comments.
|
|
**DO NOT confuse the syntaxes.**
|
|
|
|
In each cases, some inline comments are included in the localisation files.
|
|
They can be recognized as they start with the sharp character (#).
|
|
These comments are not required to be translated, they are intended to help the translator to have some context information about the sentence to translate.
|
|
|
|
You will also need to translate the invoice watermark, located in `app/pdfs/data/`.
|
|
You'll find there the [GIMP source of the image](app/pdfs/data/watermark.xcf), which is using [Rubik Mono One](https://fonts.google.com/specimen/Rubik+Mono+One) as font.
|
|
Use it to generate a similar localised PNG image which keep the default image size, as PDF are not responsive.
|
|
|
|
|
|
<a name="configuration"></a>
|
|
## Configuration
|
|
|
|
In development, locales configurations are made in [config/application.yml](../config/application.yml.default).
|
|
In production, locales configuration are made in the [config/env](../docker/env.example) file.
|
|
If you are in a development environment, your can keep the default values, otherwise, in production, values must be configured carefully.
|
|
|
|
<a name="settings"></a>
|
|
### Settings
|
|
|
|
Please refer to the [environment configuration documentation](environment.md#internationalization-settings)
|
|
|
|
<a name="applying-changes"></a>
|
|
### Applying changes
|
|
|
|
After modifying any values concerning the localisation, restart the application (ie. web server) to apply these changes in the i18n configuration.
|