You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2006/11/03 00:56:26 UTC
[jira] Created: (DERBY-2037) provide checking tool to flag possible
errors in message translations
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
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
[jira] Updated: (DERBY-2037) provide checking tool to flag possible
errors in message translations
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ 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
[jira] Closed: (DERBY-2037) provide checking tool to flag possible
errors in message translations
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-2037?page=all ]
Myrna van Lunteren closed DERBY-2037.
-------------------------------------
> 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
> Fix For: 10.3.0.0
>
> Attachments: DERBY-2037_20061121.diff, DERBY-2037_20061121.stat, 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
[jira] Updated: (DERBY-2037) provide checking tool to flag possible
errors in message translations
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-2037?page=all ]
Myrna van Lunteren updated DERBY-2037:
--------------------------------------
Derby Info: [Patch Available]
> 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: DERBY-2037_20061121.diff, DERBY-2037_20061121.stat, 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
[jira] Commented: (DERBY-2037) provide checking tool to flag
possible errors in message translations
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-2037?page=comments#action_12446789 ]
Myrna van Lunteren commented on DERBY-2037:
-------------------------------------------
There were the following additional comments on the first cut of the tool:
- the tool needs explanation of what it does and when it is to be used
(readme, javadoc, add to relevant wiki pages)
> 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
[jira] Updated: (DERBY-2037) provide checking tool to flag possible
errors in message translations
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-2037?page=all ]
Myrna van Lunteren updated DERBY-2037:
--------------------------------------
Attachment: DERBY-2037_20061121.stat
DERBY-2037_20061121.diff
Attaching a patch holding a reworked program, incl. README and build.xml.
I placed the LocCompare source file in trunk/tools/l10n.
Also modifies trunk/build.xml to add a new target, l10ncheck, that's not part of any other target.
I have tried to address all raised issues.
This is as far as I intend to carry this for a first cut.
reviews, anyone?
> 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: DERBY-2037_20061121.diff, DERBY-2037_20061121.stat, 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
[jira] Resolved: (DERBY-2037) provide checking tool to flag
possible errors in message translations
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-2037?page=all ]
Myrna van Lunteren resolved DERBY-2037.
---------------------------------------
Fix Version/s: 10.3.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
I committed the patch with revision: http://svn.apache.org/viewvc?view=rev&revision=482389
> 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
> Fix For: 10.3.0.0
>
> Attachments: DERBY-2037_20061121.diff, DERBY-2037_20061121.stat, 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