| 2014-10-10 08:11:06 |
David Planella |
bug |
|
|
added bug |
| 2014-10-10 08:12:51 |
David Planella |
description |
In order to make it easy for developers to internationalize their apps, we should add full i18n support
- Ensure all strings are wrapped in i18n.tr() calls
- Add the required CMake rules to extract translatable messages and build translations
- (Optional) add a README.translations file explaining some concepts about managing translations
Adding the CMake rules is relatively trivial. The following MP should help with an example of what's needed. An alternative would be to create a .cmake module that all applications can reuse
https://code.launchpad.net/~dpm/libqtelegram/i18n/+merge/236284 |
In order to make it easy for developers to internationalize their apps, we should add full i18n support in the templates. This should include:
- Ensure all strings are wrapped in i18n.tr() calls
- Add the required CMake rules to extract translatable messages and build translations
- (Optional) add a README.translations file explaining some concepts about managing translations
Adding the CMake rules is relatively trivial. The following MP should help with an example of what's needed. An alternative would be to create a .cmake module that all applications can reuse
https://code.launchpad.net/~dpm/libqtelegram/i18n/+merge/236284 |
|
| 2014-10-10 08:15:43 |
Zoltan Balogh |
qtcreator-plugin-ubuntu: status |
New |
Confirmed |
|
| 2014-10-10 08:15:46 |
Zoltan Balogh |
qtcreator-plugin-ubuntu: importance |
Undecided |
Critical |
|
| 2014-10-10 08:15:56 |
Zoltan Balogh |
qtcreator-plugin-ubuntu: assignee |
|
zbenjamin (zeller-benjamin) |
|
| 2014-10-10 08:16:03 |
XiaoGuo, Liu |
bug |
|
|
added subscriber The Yue team |
| 2014-10-10 08:19:22 |
David Planella |
description |
In order to make it easy for developers to internationalize their apps, we should add full i18n support in the templates. This should include:
- Ensure all strings are wrapped in i18n.tr() calls
- Add the required CMake rules to extract translatable messages and build translations
- (Optional) add a README.translations file explaining some concepts about managing translations
Adding the CMake rules is relatively trivial. The following MP should help with an example of what's needed. An alternative would be to create a .cmake module that all applications can reuse
https://code.launchpad.net/~dpm/libqtelegram/i18n/+merge/236284 |
In order to make it easy for developers to internationalize their apps, we should add full i18n support in the templates. This should include:
- Ensure all strings are wrapped in i18n.tr() calls
- Add the required CMake rules to extract translatable messages and build translations (see [1])
- (Optional) add a README.translations file explaining some concepts about managing translations (see [1])
Adding the CMake rules is relatively trivial. The following MP should help with an example of what's needed. An alternative would be to create a .cmake module that all applications can reuse
[1] https://code.launchpad.net/~dpm/libqtelegram/i18n/+merge/236284 |
|
| 2014-10-10 08:41:12 |
David Planella |
description |
In order to make it easy for developers to internationalize their apps, we should add full i18n support in the templates. This should include:
- Ensure all strings are wrapped in i18n.tr() calls
- Add the required CMake rules to extract translatable messages and build translations (see [1])
- (Optional) add a README.translations file explaining some concepts about managing translations (see [1])
Adding the CMake rules is relatively trivial. The following MP should help with an example of what's needed. An alternative would be to create a .cmake module that all applications can reuse
[1] https://code.launchpad.net/~dpm/libqtelegram/i18n/+merge/236284 |
In order to make it easy for developers to internationalize their apps, we should add full i18n support in the templates. This should include:
- Ensure all strings are wrapped in i18n.tr() calls
- Add the required CMake rules to extract translatable messages and build translations (see [1])
- (Optional) add a README.translations file explaining some concepts about managing translations (see [1])
Adding the CMake rules is relatively trivial. The following MP should help with an example of what's needed. An alternative would be to create a .cmake module that all applications can reuse.
This document [2] illustrates the translation workflow.
[1] https://code.launchpad.net/~dpm/libqtelegram/i18n/+merge/236284
[2] https://docs.google.com/a/canonical.com/document/d/12fEDKGVlNAkeXQyNXUM8JcekYwfvN7brRG5m5a0a4Dk/edit#heading=h.vbkzlk3ri2wg |
|
| 2014-10-13 15:13:22 |
Benjamin Zeller |
qtcreator-plugin-ubuntu: status |
Confirmed |
In Progress |
|
| 2014-10-14 08:38:14 |
Launchpad Janitor |
branch linked |
|
lp:~zeller-benjamin/qtcreator-plugin-ubuntu/i18n_and_reviewtools |
|
| 2014-10-20 19:02:30 |
Launchpad Janitor |
qtcreator-plugin-ubuntu (Ubuntu): status |
New |
Fix Released |
|
| 2014-10-23 12:46:33 |
Benjamin Zeller |
qtcreator-plugin-ubuntu: status |
In Progress |
Fix Released |
|
