Changes between Version 3 and Version 4 of Ticket #5763


Ignore:
Timestamp:
10/01/2017 05:10:43 PM (2 years ago)
Author:
sebastian
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5763

    • Property Owner changed from tlucas to sebastian
    • Property Summary changed from Firefox and Microsoft Edge don't pickup Latin American Spanish translations to Target languages supported by Firefox
  • Ticket #5763 – Description

    v3 v4  
    11=== Background === 
    2 Firefox and Microsoft Edge differentiate between `es-MX` (Mexico), `es-AR` (Argentinia) and `es-CL` (Chile), while Chrome combines these dialects of Spanish under `es-419`. Currently, the `gecko-webext` and `edge` builds include the same locales as the `chrome` builds, however, since Firefox and Microsoft Edge don't recognize `es-419`, they instead falls back to the `es` (i.e. Spanish as spoken in Spain) translation for all Latin American dialects. 
     2The build targets `chrome`, `gecko-webext` and `edge` only include translations for languages supported by Chrome. There are plenty of languages supported by Firefox that aren't included in that subset. 
     3 
     4Moreover, Firefox and Microsoft Edge differentiate between `es-MX` (Mexico), `es-AR` (Argentinia) and `es-CL` (Chile), while Chrome combines these dialects of Spanish under `es-419`. But since Firefox and Microsoft Edge don't recognize `es-419`, they instead fall back to `es` (i.e. Spanish as spoken in Spain). 
    35 
    46=== What to change === 
    57 
    6 Instead of mapping `es-419` to `es-MX` (for CrowdIn), we should translate `es-MX`, `es-AR` and `es-CL` separately, and map `es-MX` to `es-419` only for the Chrome builds. 
     8* Add missing target languages, supported by Firefox, to the translation project on Crowdin. 
     9* Update [https://hg.adblockplus.org/buildtools/file/b203bf192cc6/localeTools.py#l33 langMappingChrome] accordingly to account for the new languages, removing unnecessary region suffixes for languages we only translate one dialect of. 
     10* Remove the mapping for `es-419` from `langMappingChrome`, so that `es-MX` is imported/exported unchanged. But instead convert it to `es-419` only when building for the `chrome` target.