Move iso639 strings in its own translation file

1 files changed, 3 insertions, 2 deletions

diff --git a/support/doc/development/localization.md b/support/doc/development/localization.md
index 3cf797516..97e9e2c51 100644
--- a/support/doc/development/localization.md
+++ b/support/doc/development/localization.md
@@ -8,7 +8,7 @@ Will generate XLIFF files for Angular and escape inner elements in `source` tag
 
 This script will create `player_en_US.xml` XLIFF file using custom strings (VideoJS plugins) and strings from `videojs_en_US.json` file.
 
-It will also create `server_en_US.xml` XLIFF file using custom strings (defined inside the script, we did not find a way to extract them from TypeScript server files).
+It will also create `server_en_US.xml` and `iso639_en_US.xml` XLIFF file using server strings and custom strings (defined inside the script, we did not find a way to extract them from TypeScript server files).
 
 ```
 $ npm run i18n:generate
@@ -25,7 +25,8 @@ $ zanata-cli push
 ## Pull translation
 
 Pull XLIFF files from Zanata, and unescape them (so we retrieve inner elements in `source` tag, used by Angular).
-A hook converts `player` and `server` translation files to JSON (needed by Video.JS, and our application to have efficient runtime translation).
+A hook converts `player` and `server`, `iso639` translation files to JSON (needed by Video.JS, and our application to have efficient runtime translation).
+Then, `iso639` files will be merged in `server` files (so we have only one JSON file to serve server translations).
 
 ```
 $ zanata-cli pull