Projects:Translation Management
Contents |
Introduction
This project is to cover areas relating to the creation and implementation of languages within the application:
- Initial creation of a translation.
- Publication of statistics of availability, completeness and quality.
- Installation of a translation.
- Refinement of a translation.
- Testing to Production.
- Translation of business data - e.g. Product Names.
- Translation of External Documents - e.g. Purchase Orders.
Project Headline Information
- Leader: Openbravo
- Release: 2.50
- Status: Phase 1 - Iteration 1
- Functional Specification: Completed
- Technical Documentation: Completed 15 Sep 2008 - To be updated during iterations 1 and 2.
- Development Phases:
Documentation
Formal Documentation
Supporting Documentation
Quality Assurance
Test Plans
Testing Status
Development
Backlog
| ref | title | func spec ref | Business Proc ref | description | estimation | priority | dependencies | issue | status |
|---|---|---|---|---|---|---|---|---|---|
| Replace Label field with ref | |||||||||
| Locate users current language | |||||||||
| Locate all text strings for the artifact/language | |||||||||
| replace default string with translation | |||||||||
| populate untranslated text from default text | |||||||||
| populate html page with strings | |||||||||
| remove path to static translated html pages | |||||||||
| retrieve supporting collateral for each field |
Iterations
Phase 1
Iteration 1 - 15 Sep to 26 Sep
Target - 50 hours
| ref | title | func spec ref | Business Proc ref | description | estimation | priority | dependencies | issue | status |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Language Creation & Definition | TRL1 | BPTRL1 | The system should allow the user to define a new language within the application easily and quickly | 12 hours | HIGH | - | - | Done |
| 8 | Translation Repository | OTRL1 | BPTRL4 | The system will provide a central repository that allows Openbravo ERP implementers access to submit and retrieve translation packs and updates | 24 hours | HIGH | - | - | Done |
| 2 | Source existing translations | TRL2 | BPTRL1 | The system should allow the user to locate an existing translation quickly and easily from within the application itself. This ability will be dependent on the users rights | 14 hours | HIGH | 8 | 3993 | - |
| Total | 50 hours |
Iteration 2 - 29 Sep to 10 Oct
Target - 50 hours
| ref | title | func spec ref | Business Proc ref | description | estimation | priority | dependencies | issue | status |
|---|---|---|---|---|---|---|---|---|---|
| 14 | Translating Files | NTRL3 | BPTRL1 | The system will provide a default mechanism for translation of application strings and generation in a format that allows the translation to be installed into an Openbravo ERP implementation | 24 hours | HIGH | - | 3394 | - |
| 4 | Importing a New System Language | TRL4 | BPTRL1 | The system should provide the user with a mechanism to import a language pack into the application. This should be achieved without the user needing to go outside the application | 24 hours | HIGH | 2 | 3394, 3993 | - |
| 5 | Enable a New System Language | TRL5 | BPTRL1 | The system should allow a qualified user to enable a new translation for users without having to recompile and deploy the application | 2 hours | HIGH | 1 | - | - |
| Total | 50 hours |
Iteration 1 - Backlog
| ref | title | description | estimation | priority | dependencies | status |
|---|---|---|---|---|---|---|
| BL1 | refactor client Translation screens | Remove ISOCountry and ISOLanguage objects and windows. This is to be a function of the repository to maintain this information. This needs to be reviewed in the contect of BL2 and offline availability for installing translations. | 1 hour | Pending | ||
| BL2 | Allow for 'no external internet connection' | The system should still function correctly if there is no internet connection, this will limit some functionality but the System Admin should still be able to install languages from within the internal environment. | 2 hours | high | Pending | |
| BL3 | Enable structure to cater for Modularity file locations. | When the output of a translation export is created, the xml files related to a module should be exported to a module folder with the translation folder. | 2 hours | high | Pending | |
| BL4 | Validate development with the Modularity branch | Integrate new code and development with the branch for the Modularity project. Note any conflicts that require correction. | 4 hours | high | Pending | |
| Total | 9 hours |
Phase 2
Iteration 3 - 13 Oct to 24 Oct
Target - 50 hours
| ref | title | func spec ref | Business Proc ref | description | estimation | priority | dependencies | issue | status |
|---|---|---|---|---|---|---|---|---|---|
| 12 | Copy the Base Language | NTRL1 | BPTRL2 | The system will provide translators with the ability to copy the system base language for translation | 8 hours | MEDIUM | - | - | - |
| 13 | Export a Language Pack | NTRL2 | BPTRL2/ BPTRL3 | The system will allow translators to export all relevant fields and strings to a file type that allows them to parse the values for translation | 8 hours | MEDIUM | 1 | 3230, 3993 | - |
| 3 | Create a New Translation | TRL3 | BPTRL2 | The system should provide the user with a simple and efficient means to create a new language pack | 8 hours | MEDIUM | 12,13,14 | - | - |
| 6 | Refine an Implemented System Language | TRL6.1 | BPTRL3 | The system will enable a qualified user to amend translations within the application interface | 20 hours | MEDIUM | - | - | - |
| 17 | Define elements for Multiple Language Support | MLS1 | BPTRL6 | The application will provide System Admin users with the ability to define elements of the business data for MLS | 4 hours | MEDIUM | - | 3262, 3452 | - |
| Total | 48 hours |
Iteration 4 - 27 Oct to 7 Nov
Target - 36 hours
| ref | title | func spec ref | Business Proc ref | description | estimation | priority | dependencies | issue | status |
|---|---|---|---|---|---|---|---|---|---|
| 19 | External Document Translation | EXTRL1 | BPTRL6 | The system will allow translation of external documents into languages other than those defined as available in the user interface. A user should be able to create a document in the language of a customer other than those defined as system languages | 24 hours | MEDIUM | 17 | 3333, 2377, 2202 | - |
| 24 | Enable MLS data input in native language | MLS1 | BPTRL6 | The application will enable a user to enter data into a window in their native language and the application will ensure that the data is persisted in the application in both the default table and the translated language table. | 12 hours | MEDIUM | - | 2202 | - |
| Total | 36 hours |
Phase 3
To be scheduled.
Time Tracking
Phase 1
| ref | title | time | running total | notes |
|---|---|---|---|---|
| 1 | Language Creation/Definition | 0.5 hrs | 0.5 hrs | Wire framing translation entities |
| Language Creation/Definition | 1.5 hrs | 2 hrs | Preparing WAD language table | |
| Language Creation/Definition | 2 hrs | 4 hrs | Creating new Language window in WAD. | |
| Language Creation/Definition | 1 hr | 5 hrs | Language window created and layout completed. Need to link in lookups to Country and Language codes, auto generate the name based on ll_CC_version from fields on the form. | |
| Language Creation/Definition | 1.5 hrs | 6.5 hrs | Created necessary lookup tables and windows, recreated language test window. Need to resolve sequencer issue to create test data, then auto populate fields from selections made in the windows, also populate ISO Country, ISO Language, and ISO Language Country tables with relevant data. | |
| Language Creation/Definition | 1 hrs | 7.5 hrs | Updated table definitions to allow for UUID id creation. Update form with correct names and layout, input test data for ISO Country, ISO Language, ISO Language/Country windows. | |
| Language Creation/Definition | 3 hrs | 10.5 hrs | Create SL_Language_Name callout to update the Language name field with combination of ISOCode_version, to provide a unique name complete with versions of the same translation. Add call to SL_Language_Name to the inpADIsoLangaugeCountry, inpISOCode, and inpTranslatedVersion fields in the LanguageDev table.
Add retrieval for ISOCode from AD_ISO_LANGAUGE_COUNTRY table based on selection in the Language field on the window. | |
| Language Creation/Definition | 1.5 hrs | 10.5 hrs | Tidy up the generation of a language in the Language/Country window - ensure the language is in lower case and the country is upper case. Review all windows, tables, and code and clean them. Create a callout to populate and format the AD_ISO_Language_Country name and iso code fields based on the selections in the ISO Country and ISO Language fields. | |
| 8 | Translation Repository | 1 hour | 3 hours | Rethinking Client Translation View |
| 8 | Translation Repository | 1 hour | 4 hours | Script database objects for repsitory objects |
| 8 | Translation Repository | 1 hour | 5 hours | Create repository web service classes - TranslationService (Interface) and TranslationServiceImpl. Create TranslationHandler class to manage retrieval of information and to act as a layer between the application and the web service layer. |
| 8 | Translation Repository | 2 hours | 7 hours | Tidy up functionality around the TranslationHandler, TranslationSearchHandlerData |
| 8 | Translation Repository | 2 hours | 9 hours | Compile src-trl with new classes and install in the Butler source code. Implement unit tests in the src-trl library, configure, and create first test cases. Test cases passing. |
| 8 | Translation Repository | 3 hours | 12 hours | Refactoring code flow between search and handlers |
| 8 | Translation Repository | 1 hours | 13 hours | Flesh out tests for complete Translationheader info including LanguagePack, add test for null values in the TranslationSearchData object. |
| 8 | Translation Repository | 1.5 hours | 14.5 hours | Create windows for ISO Country, ISO Language, ISO Language/Country, Translation. Recompile and input test data. |
User Stories
| ref | title | func spec ref | Business Proc ref | description | estimation | priority | dependencies | issue |
|---|---|---|---|---|---|---|---|---|
| 1 | Language Creation/Definition | TRL1 | BPTRL1 | The system should allow the user to define a new language within the application easily and quickly | - | HIGH | - | - |
| 2 | Source existing translations | TRL2 | BPTRL1 | The system should allow the user to locate an existing translation quickly and easily from within the application itself. This ability will be dependent on the users rights | - | HIGH | 8 | 3993 |
| 3 | Create a New Translation | TRL3 | BPTRL2 | The system should provide the user with a simple and efficient means to create a new language pack | - | MEDIUM | 12,13,14 | - |
| 4 | Importing a New System Language | TRL4 | BPTRL1 | The system should provide the user with a mechanism to import a language pack into the application. This should be achieved without the user needing to go outside the application | - | HIGH | 2 | 3394, 3993 |
| 5 | Enable a New System Language | TRL5 | BPTRL1 | The system should allow a qualified user to enable a new translation for users without having to recompile and deploy the application | - | HIGH | 1 | - |
| 6 | Refine an Implemented System Language | TRL6.1 | BPTRL3 | The system will enable a qualified user to amend translations within the application interface | - | MEDIUM | - | - |
| 7 | Retrieve Updates to Language Packs | TRL6.2 | BPTRL3 | The system should provide a mechanism that allows a qualified user to retrieve updated translations provided by other implementers/translators | - | LOW | 8 | - |
| 8 | Translation Repository | OTRL1 | BPTRL4 | The system will provide a central repository that allows Openbravo ERP implementers access to submit and retrieve translation packs and updates | - | HIGH | - | - |
| 9 | Accept Translation Updates | RTRL1 | BPTRL3/ BPTRL4 | The system will allow implementers of Openbravo ERP to submit updated translations to the central repository from within the application | - | LOW | 8 | - |
| 10 | Score/Quality Rate Translations | RTRL2 | BPTRL4 | The system will provide a mechanism that allows the community and Openbravo ERP to rate a translation (new or update) for quality and suitability for implementation | - | LOW | - | - |
| 11 | Publish New/Updated Translations | RTRL3 | BPTRL4 | The system will provide a mechanism to enable translations (new and updates) to implementers of Openbravo ERP. This mechanism will include the quality/score for the translation to allow the implementer to decide if they wish to implement the translation into a live installation | - | LOW | 8 | - |
| 12 | Copy the Base Language | NTRL1 | BPTRL2 | The system will provide translators with the ability to copy the system base language for translation | - | MEDIUM | - | - |
| 13 | Export a Language Pack | NTRL2 | BPTRL2/ BPTRL3 | The system will allow translators to export all relevant fields and strings to a file type that allows them to parse the values for translation | - | MEDIUM | 1 | 3230, 3993 |
| 14 | Translating Files | NTRL3 | BPTRL1 | The system will provide a default mechanism for translation of application strings and generation in a format that allows the translation to be installed into an Openbravo ERP implementation | - | HIGH | - | 3394 |
| 15 | Submit New Translations to Repository | NTRL4 | BPTRL2/ BPTRL3/ BPTRL4 | The system will provide a convenient method for a new Translation to be submitted to a central repository for distribution to the community and implementers | - | LOW | 8 | - |
| 16 | Translator User Role | TRL7 | BPTRL1 | The system will allow rights to be assigned to a user with specific translation functionality. This role will have rights to update language packs within the application interface | - | LOW | - | - |
| 17 | Define elements for Multiple Language Support | MLS1 | BPTRL6 | The application will provide System Admin users with the ability to define elements of the business data for MLS | - | MEDIUM | - | 3262, 3452 |
| 18 | Export MLS Business Data | MLS2 | BPTRL6 | The system will allow a Translator to export all 'Business Data' elements within the application marked for MLS to external files in a format that allows the translator to create translations for these files | - | LOW | 13,17 | 3262, 3452 |
| 19 | External Document Translation | EXTRL1 | BPTRL6 | The system will allow translation of external documents into languages other than those defined as available in the user interface. A user should be able to create a document in the language of a customer other than those defined as system languages | - | MEDIUM | 17 | 3333, 2377, 2202 |
| 20 | Install languages during installation | INSTRL1 | BPTRL7 | The system will allow the installation of other languages during the installation process | - | LOW | 2,4 | 3322 |
| 21 | Install multiple languages during installation process | INSTRL2 | BPTRL7 | The system will allow the installation of multiple languages during the initial installation process of Openbravo ERP | - | LOW | 20 | 3322 |
| 22 | Default user language selection | TRL8 | BPTRL1 | The system will make it possible to configure a default user language per user. If this default language does not exist, the users operating systems language should be selected. Users may want to have their operating system on a language but access to Openbravo ERP using another language | - | LOW | 1 | 3235 |
| 23 | Delete translation texts with their parent original text | TRL9 | BPTRL3 | The system will allow an authorised user to delete an element from the application and by doing so will also delete the translations for that text also. The translation text should not stop a valid deletion process | - | LOW | - | 3331 |
| 24 | Enable MLS data input in native language | MLS1 | BPTRL6 | The application will enable a user to enter data into a window in their native language and the application will ensure that the data is persisted in the application in both the default table and the translated language table. | - | MEDIUM | - | 2202 |