[jira] Updated: (LOOM-38) Update I18N Keys

The following issue has been updated:

    Updater: peter royal (mailto:[email protected])
       Date: Wed, 14 Apr 2004 8:51 PM
    Changes:
             Version changed from 1.0
             Fix Version changed to future
             Fix Version changed from 1.0
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=LOOM-38&page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=LOOM-38

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: LOOM-38
    Summary: Update I18N Keys
       Type: Improvement

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: loom
 Components: 
             Engine
             Tools
   Fix Fors:
             future

   Assignee: 
   Reporter: Peter Donald

    Created: Sun, 24 Aug 2003 11:37 PM
    Updated: Wed, 14 Apr 2004 8:51 PM

Description:
Currently the keys for the I18N strings are of varrying formats and "standards". Most follow the pseudo-standard of <area>.<content>.<level> where <level> is one of "info", "err", "notice", <area> is a short hand for user of message (ie DefaultInfoBuider may use "builder") and <content> is the id of specific message such as "missing-header".

However this is not always followed and can be hard to maintain. It would be better to go to a more formalized/structured key space such as;

MSG-0001 : message used when displaying interface to users
ERR-0001 : error message representing failure
WRN-0001 : warning message that represented a failure that is guarded against and does not halkt the process

This would make it much easier to verify that all the messages in source code have coresponding entrys in resource bundles using simple perl pattern matching script. 


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira