Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(ivy): i18n - support setting locales for each translation file #33381

Commits on Oct 25, 2019

  1. fix(ivy): i18n - support setting locales for each translation file

    Previously the target locale of a translation file had to be extracted
    from the contents of the translation file. Therefore it was an error if
    the translation file did not provide a target locale.
    
    Now an array of locales can be provided via the `translationFileLocales`
    option that overrides any target locale extracted from the file.
    This allows us to support translation files that do not have a target
    locale specified in their contents.
    
    // FW-1644
    Fixes angular#33323
    petebacondarwin committed Oct 25, 2019
    Copy the full SHA
    185f747 View commit details
    Browse the repository at this point in the history
  2. fix(ivy): i18n - update localize-translate to accept target-locales

    The `localize-translate` command line tool can now accept an array of
    target locales to support the case where translation files do not
    contain them. Specify this array via the `--target-locales` option.
    
    NOTE to early adopters: in order to support this, the original `-t`
    option for the binary has changed from being a glob pattern to an array
    of paths, which will have matching indices to any provided target-locales.
    petebacondarwin committed Oct 25, 2019
    Copy the full SHA
    c7a3767 View commit details
    Browse the repository at this point in the history