[jira] Updated: (OFBIZ-385) Externalize strings for translation. . Normalize existing keys.

["Marco Risaliti (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OFBIZ-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marco Risaliti updated OFBIZ-385:
---------------------------------

    Component/s: framework

> Externalize strings for translation. . Normalize existing keys.
> ---------------------------------------------------------------
>
>                 Key: OFBIZ-385
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-385
>             Project: OFBiz
>          Issue Type: Task
>          Components: framework
>    Affects Versions: SVN trunk
>         Environment: All platforms
>            Reporter: Gerrie Myburgh
>            Priority: Trivial
>
> 1. Externalize strings for translation. 
> Stings taken out are all strings that comply with the following criteria
> Has more than one word in it
> 60 % of all the words are recognized as known standard English words
> 60 % of the string length consists of known standard English words
> Strings are places one of 3 files
> 1.	Exception.properties
> 2.	Message.properties
> 3.	UndefContext.properties
> Each property file is placed into the correct directories in the module that contains the *.java file
> Keys are defined in the *.java file as
> Private static final String Name1Name2Name3 = "Name1Name2Name3";
> Then referred to in the code as Name1Name2Name3.
> UtilMisc must be changed to return the current Locale for the thread using the resource. This is required in the case of  Exceptions using resources to construct error messages.
> 2. Normalize existing keys.
> All keys of the form name1.name2.name3 is to be changed to Name1Name2Name3. The references to the keys must be changed in the *.java file as well as the definition in the *.properties file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.