iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/integration/cli-hello-world-ivy-i18n/e2e
History
Pete Bacon Darwin f433d6604b feat(ivy): i18n - support source locale inlining (#33101) 
Add a new flag to `localize-translate` that allows the
source locale to be specified. When this locale is
provided an extra copy of the files is made for this
locale where the is no translation but all the calls to
`$localize` are stripped out.

Resolves FW-1623

PR Close #33101
 		2019-10-14 20:32:57 +00:00
..
de test(ivy): i18n - add compile time translation to integration test (#32881) 2019-10-09 13:19:38 -07:00
en feat(ivy): i18n - support source locale inlining (#33101) 2019-10-14 20:32:57 +00:00
fr test(ivy): i18n - add compile time translation to integration test (#32881) 2019-10-09 13:19:38 -07:00
legacy test(ivy): i18n - add compile time translation to integration test (#32881) 2019-10-09 13:19:38 -07:00
runtime test(ivy): i18n - add compile time translation to integration test (#32881) 2019-10-09 13:19:38 -07:00
README.md test(ivy): i18n - add compile time translation to integration test (#32881) 2019-10-09 13:19:38 -07:00
app.po.ts test(ivy): i18n - add compile time translation to integration test (#32881) 2019-10-09 13:19:38 -07:00
protractor.conf.js test(ivy): add cli-hello-world-ivy-i18n integration test (#31609) 2019-08-30 12:53:26 -07:00
tsconfig.e2e.json test(ivy): add cli-hello-world-ivy-i18n integration test (#31609) 2019-08-30 12:53:26 -07:00

README.md

E2E tests

There are four different sets of e2e tests in this folder. They are all testing different translation scenarios, but they are all built with IVY enabled.

runtime

Translations are provided at runtime by calling loadTranslations() in the polyfill.ts

de and fr

The application is built (into the dist folder) and then two sets of translations (src/locales/messages.(de|fr).json) are used to generate two copies of the app, which have been translated (compile-time inlined).

These translated apps are stored in tmp/translations/(de|fr).

legacy

The legacy ng xi18n tool extracts the messages from the Angular templates, into the XLIFF 1.2 format with legacy message ids (tmp/legacy-locales/messages.legacy.xlf).

The translation file is modified to apply a simple translation.

The app must be compiled using the i18nLegacyMessageIdFormat option set to ensure that the correct message ids are used to match those in the translation files.

The app is translated using the compile-time inlining tool to generate a copy that has the translated message in it.

Hosting

Since the CLI hosts from and in-memory file-system the compile-time inliner is not able to translate the output files. So the de, fr and legacy apps must be statically built to disk and translated there.

Since the translated app is now on disk, we cannot use the CLI to serve it. Instead we use a simple static HTTP server instead.