translation enablement #1
Comments
|
What does that mean? Automatic translation of payloads? (just trying to clarify.. I can think of a few different interpretations of "translation enablement") |
|
@srl295 is investigating how to use a Bluemix Globalization service to translate English text in the Web application to appear in other languages. It demonstrates how a team could automate a release task as part of a continuous delivery pipeline to more rapidly deliver applications that must support globalization requirements. |
|
@ebullient right — just a placeholder issue for now. I'll add some more details when I figure out what I'm asking. But the general idea is to translate the app itself, not the payloads. |
|
work in progress @ https://github.com/srl295/blue-messenger/tree/intl |
* uses (requires) the Globalization Pipeline bound service * use `npm run gen-i18n` to pickup any changes to index.html * use localized number formatting on the client side * Some strings aren't translated yet, such as "You have sent 83 messages!" and "Generate a alto message load for 5 minutes!" Fixes: cfsworkload#1
* uses (requires) the Globalization Pipeline bound service
* use `npm run gen-i18n` to pickup any changes to index.html
* use localized number formatting on the client side
* escape HTML from `Hey <b>you!</b>` to `Hey {b}you!{/b}` for translation
Fixes: cfsworkload#1
* uses (requires) the Globalization Pipeline bound service
* use `npm run gen-i18n` to pickup any changes to index.html
* use localized number formatting on the client side
* escape HTML from `Hey <b>you!</b>` to `Hey {b}you!{/b}` for translation
Fixes: cfsworkload#1
|
any update? |
investigate translation enablement
The text was updated successfully, but these errors were encountered: