Changes between Version 4 and Version 5 of Ticket #104, comment 8


Ignore:
Timestamp:
08/16/2017 03:31:50 PM (3 years ago)
Author:
sebastian
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #104, comment 8

    v4 v5  
    11I'd like to revive this issue, since Erick is interested in picking it up. However, the issue description seems out-of-date. Specifically the Gecko-specific features/syntax (including access keys) aren't relevant anymore, as legacy Gecko extensions are phased out. 
    22 
    3 Also, since we only need to target the [https://developer.chrome.com/extensions/i18n Chrome-style translation format], I'd rather parse any metadata for the validation from the `comment` field in the source translation's `locales/en_US/*.json` file. That way we avoid redundancies (for example max length is usually already documented there) and have all translation data in one place. 
     3Also, since we only need to target the [https://developer.chrome.com/extensions/i18n Chrome-style translation format], I'd rather parse any metadata for the validation from the `description` field in the source translation's `locales/en_US/*.json` file. That way we avoid redundancies (for example max length is usually already documented there) and have all translation data in one place. 
    44 
    55Then again, max length is already enforced by CrowdIn, and flagging strings which may be equal to the source translation might be tricky since some (in particular short) translations might match the English string in some but not all translations. But what we'd still need at least, is validation of placeholders.