db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2037) provide checking tool to flag possible errors in message translations
Date Fri, 03 Nov 2006 01:06:18 GMT
     [ http://issues.apache.org/jira/browse/DERBY-2037?page=all ]

Myrna van Lunteren updated DERBY-2037:
--------------------------------------

    Attachment: LocCompare.java

Attaching the source file LocCompare.java

I will think about where this should go a bit more, then make a proper patch.

This current file differs from the one suggested in the thread to the list (in the description)
in the following:
- by default, it assumes the locale files to be compared are in the same location as the english
ones. One can still specify a temporary location. I thought this maybe might be useful after
all.
- it continues on to a next message if the original message string is not found.

This does not yet implement the following:
- print comparison strings by default to allow easy diffs (comment by Rajesh).
     The program has code that prints out the Strings compared when the program is run with
-Dtvtdebug=true. But I've found there's too much information in that case, the output becomes
quickly unreadable. I'll play with it a bit more, see if I find a place to print this where
it looks ok (to me).
- check on non-valid characters (comment Andrew).




> provide checking tool to flag possible errors in message translations
> ---------------------------------------------------------------------
>
>                 Key: DERBY-2037
>                 URL: http://issues.apache.org/jira/browse/DERBY-2037
>             Project: Derby
>          Issue Type: Test
>          Components: Localization
>    Affects Versions: 10.3.0.0
>            Reporter: Myrna van Lunteren
>         Assigned To: Myrna van Lunteren
>            Priority: Minor
>         Attachments: LocCompare.java
>
>
> It would be useful to have a tool available that flags possible translation file issues,
such as:
> - missing translations for (new) English messages
> - mismatched parameters between English and non-English messages
> - translation of keywords 
> - quoting problems (i.e. use of double quotes when single quotes should be used, use
of single quotes when double quotes should be used. This is based on what's described in the
MessageFormat api doc)
> - mismatched characters such as < (when meaning smaller than), > (when meaning
larger than), % etc.
> - identification of invalid characters, specifically characters in the range of 0x00-0x1f
(which are ASCII) and 0x7f-0xff
> Note that such a tool cannot be definite (except about the missing messages) because
the English messages are not following very strict formatting, and because what's acceptable
syntax/grammar in one language may not work in another. 
> A discussion about a first cut at such a tool can be found at:
> http://comments.gmane.org/gmane.comp.apache.db.derby.devel/32187

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message