Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
translation [2019_04_26 15:30] – smeadmin | translation [2024_02_20 23:55] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Translation | + | ====== |
+ | == last updated on Feb 21, 2023 == | ||
- | The Enterprise File Fabric | + | The Access Anywhere |
- | Out of the box, the Enterprise File Fabric (appliance) ships with the following | + | Out of the box the following |
- | * English | + | * English |
- | * English (US) | + | * French |
+ | * German | ||
* Italian | * Italian | ||
- | * Polish | + | * Spanish |
- | At its core, the File Fabric | + | At its core, the platform |
===== Which language is selected? ===== | ===== Which language is selected? ===== | ||
- | When a user visits the File Fabric' | + | When a user visits the Access Anywhere Server |
Some browsers may also provide override settings, or extensions, that also allow users to select their desired language that may differ from their operating system' | Some browsers may also provide override settings, or extensions, that also allow users to select their desired language that may differ from their operating system' | ||
- | ===== Translation management ===== | + | ==== Translation management ==== |
- | The File Fabric | + | |
+ | Access Anywhere | ||
To visit this interface, login as the **ApplAdmin** user, and click on **Settings** \> **Languages** | To visit this interface, login as the **ApplAdmin** user, and click on **Settings** \> **Languages** | ||
Line 28: | Line 31: | ||
From this screen you will notice the following controls: | From this screen you will notice the following controls: | ||
- | * **Download current version of .pot files** — To translate the File Fabric you will need the base " | ||
- | * **Force to use selected language** — When this is set to anything other than " | ||
- | * **Default language** — This sets the default language that is served if no mutual language can be negotiated with the users browser. | ||
- | * **Active languages** — This controls which languages are available. Download links to the translation files for these files are provided. | ||
- | ==== Translating the File Fabric ==== | + | * **Download current version |
- | Before you begin any translation | + | |
- | If you are translating | + | * **Force to use selected language** — When this is set to anything other than " |
+ | |||
+ | * **Default language** — This sets the default language that is served if no mutual language can be negotiated with the user's browser. | ||
+ | |||
+ | * **Active languages** — This controls the active languages and download links to the translation files for available languages. | ||
+ | |||
+ | ==== New Translations ==== | ||
+ | |||
+ | Before you begin any translation you should first ensure that you have suitable translation tools available. Access Anywhere uses the gettext standard, many free and paid tools exist, such as [POEdit](https:// | ||
+ | |||
+ | If you are translating into language that does not exist, then you should start by clicking the **Download current version of .pot files** link. | ||
In the download, you will receive a ZIP file that contains 3 POT files, each of which contain different translation strings used in different parts of the application. | In the download, you will receive a ZIP file that contains 3 POT files, each of which contain different translation strings used in different parts of the application. | ||
Line 50: | Line 58: | ||
When prompted, select the language you wish to translate to. | When prompted, select the language you wish to translate to. | ||
- | {{::translation_language_and_sme_code_pot_and_/ | + | {{::select_language.png?400|}} |
The tool will then allow you to input translations. | The tool will then allow you to input translations. | ||
Line 64: | Line 72: | ||
Once you have completed the translations, | Once you have completed the translations, | ||
- | Whilst you are saving changes to the PO files, some applications like POEdit automatically generate .MO files. These are compiled versions of the PO files and are also required by the File Fabric. | + | Whilst you are saving changes to the PO files, some applications like POEdit automatically generate .MO files. These are compiled versions of the PO files and are also required by the server. |
If your editor does not automatically compile the PO files into MO files, then most editors provide an option to convert into MO. | If your editor does not automatically compile the PO files into MO files, then most editors provide an option to convert into MO. | ||
Line 73: | Line 81: | ||
You can then revisit the **Languages** screen, and upload the ZIP file there. Once uploaded, your translations are then available and can be enabled. | You can then revisit the **Languages** screen, and upload the ZIP file there. Once uploaded, your translations are then available and can be enabled. | ||
+ | |||
+ | ==== Updating existing translations ==== | ||
+ | |||
+ | The process for updating existing translations is similar to the process for creating new translations, | ||
+ | |||
+ | You can then make you changes, compile, and upload to the server. | ||
+ | |||
+ | ==== Updating translations with new Access Anywhere Server releases ==== | ||
+ | |||
+ | When you update your installation to new versions, your existing translations will be persisted with the updates. | ||
+ | |||
+ | However, as with any new release, it is likely that new strings will have been introduced. With each release, the Access Anywhere' | ||
+ | |||
+ | To do this, download the new POT files. For each POT file, like **sme\_code.pot**, | ||
+ | |||
+ | To merge the files you can use the **msgmerge** command, part of the gettext package, like follows: | ||
+ | |||
+ | ``` | ||
+ | msgmerge sme_code_fr.po sme_code.pot > sme_code_fr_new.po | ||
+ | ``` | ||
+ | |||
+ | This will merge the old PO file with the new template (maintaining existing translations) and create a new file called **sme\_code\_fr\_new.po**. You can check the new file, and once happy rename it to the original name. Repeat this process for each PO and relevant POT file that exists. | ||
+ | |||
+ | Once done, follow the previous instructions for uploading your PO files to the Access Anywhere Server. | ||
+ | |||
+ | ## Troubleshooting | ||
+ | |||
+ | PO and POT Files can be found under | ||
+ | |||
+ | / | ||
+ | |||
+ | ==== Replacing text in the English (" | ||
+ | | ||
+ | English (" | ||
+ | |||
+ | * Download the .pot files for the current language (" | ||
+ | * Copy the .pot files to .po files(s), adding the language code to the names of the files as described on the doc. page, for example: " | ||
+ | * Edit the .po files that contain the strings strings that you want to change, replacing the empty message strings with the new values you want. | ||
+ | * Compile all three .po files, producing three .mo files. All of these files should sit together. | ||
+ | * Zip the six files (.po and .mo) and upload them to the server. | ||
+ | * Set the newly uploaded language as the default language. | ||
+ | |||
+ | The .po files that you will be starting with are the base files for the Server. | ||
+ | |||
+ | You should find the message IDs that match the strings you want to replace and put the replacement values between the quotes of the associated message strings. |