Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "DSDP/MTJ/Requirements/MIDlet Localization Support"
m |
(detailing requirements) |
||
Line 14: | Line 14: | ||
<b>ID</b>: L10n:FR002 - Locale Editor | <b>ID</b>: L10n:FR002 - Locale Editor | ||
− | <b>Description:</b> | + | <b>Description:</b> Add an editor to edit the locales source file. This editor will have several tabs: one for each existing locale in the source files and on overview tab. Each locale tab will show the set of keys and the set of messages associated with that locale. There must be options in the editor to add/remove locale and add/remove keys. |
+ | |||
<b>Priority:</b> 1 | <b>Priority:</b> 1 | ||
Line 26: | Line 27: | ||
<b>ID</b>: L10n:FR003 - Generate Bundles During Build | <b>ID</b>: L10n:FR003 - Generate Bundles During Build | ||
− | <b>Description:</b> | + | <b>Description:</b> Localization support uses an XML source file to group different locales. During |
+ | build the properly bundles (ex: messages_en_US.properties, | ||
+ | messages_pt_BR.properties) must be generated from the locales source and placed | ||
+ | in the correct locations | ||
<b>Priority:</b> 1 | <b>Priority:</b> 1 | ||
Line 39: | Line 43: | ||
<b>ID</b>: L10n:FR004 - Export Bundles | <b>ID</b>: L10n:FR004 - Export Bundles | ||
− | <b>Description:</b> | + | <b>Description:</b> Localization support uses an XML source file to group different locales. An |
+ | option must be added to the User interface to export proper bundles (ex: | ||
+ | messages_en_US.properties, | ||
+ | messages_pt_BR.properties) from the locales source file. | ||
+ | |||
<b>Priority:</b> 2 | <b>Priority:</b> 2 | ||
Line 51: | Line 59: | ||
<b>ID</b>: L10n:FR005 - Externalize Strings | <b>ID</b>: L10n:FR005 - Externalize Strings | ||
− | <b>Description:</b> | + | <b>Description:</b> Add a wizard or replace the "Source > Externalize Strings" wizard in order to |
+ | Externalize MIDlet source strings to the appropriate MIDlet project locale | ||
+ | source, according to the MIDLet project localization support added in MTJ. | ||
<b>Priority:</b> 4 | <b>Priority:</b> 4 | ||
Line 64: | Line 74: | ||
<b>ID</b>: L10n:FR006 - Import Previously Existing Bundles in Project Locale Source | <b>ID</b>: L10n:FR006 - Import Previously Existing Bundles in Project Locale Source | ||
− | <b>Description:</b> | + | <b>Description:</b> If a project which already has property files for different locales is imported |
+ | in an MTJ workspace, support to import this properties into an MTJ Locale | ||
+ | Source file is required. | ||
<b>Priority:</b> 5 | <b>Priority:</b> 5 | ||
Line 77: | Line 89: | ||
<b>ID</b>: L10n:FR007 - Ant Task to Generate Bundles | <b>ID</b>: L10n:FR007 - Ant Task to Generate Bundles | ||
− | <b>Description:</b> | + | <b>Description:</b> Localization support in MTJ uses an XML source file to group different locales. |
+ | If the user decides to build his project using Ant (plus Antenna), it is | ||
+ | interesting to have an ant task to generate proper bundles (property files) | ||
+ | from the locales source file. | ||
<b>Priority:</b> 5 | <b>Priority:</b> 5 |
Latest revision as of 18:56, 16 October 2008
ID: L10n:FR001 - Add Localization Support To a MIDlet Project
Description: Add an option to add L10n Support to a MIDlet Project, this will create a locales source files, and a java source code that makes the messages available to be used in the MIDlet code.
Priority: 1
Owner: Hugo Raniere
Status: Proposed on 15-Oct-2008
Community Review: TBD
ID: L10n:FR002 - Locale Editor
Description: Add an editor to edit the locales source file. This editor will have several tabs: one for each existing locale in the source files and on overview tab. Each locale tab will show the set of keys and the set of messages associated with that locale. There must be options in the editor to add/remove locale and add/remove keys.
Priority: 1
Owner: Hugo Raniere
Status: Proposed on 15-Oct-2008
Community Review: TBD
ID: L10n:FR003 - Generate Bundles During Build
Description: Localization support uses an XML source file to group different locales. During build the properly bundles (ex: messages_en_US.properties, messages_pt_BR.properties) must be generated from the locales source and placed in the correct locations
Priority: 1
Owner: Hugo Raniere
Status: Proposed on 15-Oct-2008
Community Review: TBD
ID: L10n:FR004 - Export Bundles
Description: Localization support uses an XML source file to group different locales. An option must be added to the User interface to export proper bundles (ex: messages_en_US.properties, messages_pt_BR.properties) from the locales source file.
Priority: 2
Owner: Hugo Raniere
Status: Proposed on 15-Oct-2008
Community Review: TBD
ID: L10n:FR005 - Externalize Strings
Description: Add a wizard or replace the "Source > Externalize Strings" wizard in order to Externalize MIDlet source strings to the appropriate MIDlet project locale source, according to the MIDLet project localization support added in MTJ.
Priority: 4
Owner: Hugo Raniere
Status: Proposed on 15-Oct-2008
Community Review: TBD
ID: L10n:FR006 - Import Previously Existing Bundles in Project Locale Source
Description: If a project which already has property files for different locales is imported in an MTJ workspace, support to import this properties into an MTJ Locale Source file is required.
Priority: 5
Owner: Hugo Raniere
Status: Proposed on 15-Oct-2008
Community Review: TBD
ID: L10n:FR007 - Ant Task to Generate Bundles
Description: Localization support in MTJ uses an XML source file to group different locales. If the user decides to build his project using Ant (plus Antenna), it is interesting to have an ant task to generate proper bundles (property files) from the locales source file.
Priority: 5
Owner: Hugo Raniere
Status: Proposed on 15-Oct-2008
Community Review: TBD