(→Which language code should I use for a new team?: Minor language code correction) |
(Q&A sequence modified) |
||
Line 1: | Line 1: | ||
+ | __TOC__ | ||
{{#CUSTOMTITLE:CKEditor Localization Troubleshooting}} | {{#CUSTOMTITLE:CKEditor Localization Troubleshooting}} | ||
The following article describes some issues that may arise during the localization process. If your problem is not described here, [https://www.transifex.net/projects/p/ckeditor/ contact CKEditor project maintainers] to get support. | The following article describes some issues that may arise during the localization process. If your problem is not described here, [https://www.transifex.net/projects/p/ckeditor/ contact CKEditor project maintainers] to get support. | ||
Line 12: | Line 13: | ||
Do not forget to unlock the translation when you are done with your work. | Do not forget to unlock the translation when you are done with your work. | ||
+ | |||
+ | === Which language code should I use for a new team? === | ||
+ | When you are [[CKEditor_3.x/Developers_Guide/Localization_Teams#Requesting_a_New_Team|setting up a new localization team]], you will be able to choose one from the drop-down list on Transifex page. | ||
+ | |||
+ | [[Image:Transifex_language_codes.png|frame|center|Language codes available in Transifex]] | ||
+ | |||
+ | |||
+ | Please note that while Transifex offers both two letter and four letter language codes, you should stick to the following CKSource rules based on ISO 639-1: | ||
+ | * For a ''standard variation of a language'', use a two letter language code, for example <code>pt</code> for Portuguese as used in Portugal. | ||
+ | * For a ''regional variant of a language only'', use a four letter language code, for example <code>pt_BR</code> for Portuguese as used in Brazil. | ||
=== Do I still need to escape apostrophes in localized strings? === | === Do I still need to escape apostrophes in localized strings? === | ||
Line 36: | Line 47: | ||
* BOM is present at the beginning of the file. | * BOM is present at the beginning of the file. | ||
* The <code>.po</code> file structure was altered and is no longer compliant with the project resources. | * The <code>.po</code> file structure was altered and is no longer compliant with the project resources. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 08:31, 2 December 2011
Contents
- 1 How to report disruptive team members, abuse, and vandalism
- 2 Resource was not locked after downloading it for translation
- 3 Which language code should I use for a new team?
- 4 Do I still need to escape apostrophes in localized strings?
- 5 Transifex hangs on uploading a localized file
- 6 Transifex reports a failed file correctness check
The following article describes some issues that may arise during the localization process. If your problem is not described here, contact CKEditor project maintainers to get support.
How to report disruptive team members, abuse, and vandalism
If you feel that there is a member of your team who is abusing the CKEditor localization project in any way, please report him or her to the project maintainers.
Resource was not locked after downloading it for translation
You can lock the resource manually by selecting the Lock this translation to notify others you're working with it. option in the Translation Details dialog window.
Do not forget to unlock the translation when you are done with your work.
Which language code should I use for a new team?
When you are setting up a new localization team, you will be able to choose one from the drop-down list on Transifex page.
Please note that while Transifex offers both two letter and four letter language codes, you should stick to the following CKSource rules based on ISO 639-1:
- For a standard variation of a language, use a two letter language code, for example
pt
for Portuguese as used in Portugal. - For a regional variant of a language only, use a four letter language code, for example
pt_BR
for Portuguese as used in Brazil.
Do I still need to escape apostrophes in localized strings?
No. Although previously we have been working directly on JavaScript files and all apostrophes had to be escaped by using a backslash character, you no longer need to do this. Our tools will now perform all the necessary replacements in the background so just enter a correct literal string.
- Old version:
-
Barre d\'emplacement des éléments de l\'éditeur
-
- Current version:
-
Barre d'emplacement des éléments de l'éditeur
-
Transifex hangs on uploading a localized file
Sometimes when a file is malformed or uses an incorrect encoding, the upload may not succeed — it will hang without a descriptive error message. If this happens please check the following:
- Whether the file is correctly encoded.
All CKEditor files are UTF-8 encoded. ANSI files will be rejected. - Whether the file does not contain BOM.
- Whether the file structure was not altered in any way.
- You can run
msgfmt -c
on the file to check its correctness before you attempt to upload it.
- You can run
Transifex reports a failed file correctness check
On uploading the file Transifex may report that the file is malformed.
As suggested by Transifex, check the file by running msgfmt -c
. Possible causes of the error might be:
- BOM is present at the beginning of the file.
- The
.po
file structure was altered and is no longer compliant with the project resources.