-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #5 from rmraya/Localization
Localization
- Loading branch information
Showing
115 changed files
with
4,465 additions
and
629 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
# XLIFF Manager Localization | ||
|
||
Localizing XLIFF Manager requires processing 3 types of files: | ||
|
||
1. Java .properties files | ||
2. TypeScript strings in JSON format | ||
3. Documentation from DITA files | ||
|
||
## Localization of Java .properties | ||
|
||
[javaPM](https://www.maxprograms.com/products/javapm.html) is used to generate XLIFF from `/src` folder. | ||
|
||
Use a command like this to generate XLIFF: | ||
|
||
```bash | ||
/path-to-Javapm/createxliff.sh -src XLIFFManager/src -xliff yourXliffFile.xlf -srcLang en -tgtLang fr -enc UTF-8 | ||
``` | ||
|
||
XLIFF Manager .properties are encoded in UTF-8; translated versions must be generated using UTF-8 character set. | ||
|
||
## Localization of TypeScript strings | ||
|
||
XLIFF Manager can be used to generate to generate XLIFF from the JSON files stored in `/i18n` folder. | ||
|
||
- Use `/i189/filterConfig.json` when generating XLIFF to handle `'&'` signs used in menu names as regular characters instead of HTML entities. | ||
- Select *Paragraph Segmentation* to avoid splitting strings at inconvenient places. | ||
- Select *Export Approved Segments as TMX* when merging the translated XLIFF and then reuse those translations when processing the User Guide. | ||
|
||
## Localization of DITA manuals | ||
|
||
Although you can use XLIFF Manager to generate XLIFF from the DITA maps stored in `/docs` folder, it is stronly suggested to use [Fluenta](https://www.maxprograms.com/products/fluenta.html) for processing the manuals. Fluenta offers enhanced methods for reusing translations when the manual is updated. | ||
|
||
Use [Conversa DITA Publisher](https://www.maxprograms.com/products/conversa.html) to publish the translated DITA maps as PDF. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
Oops, something went wrong.