- cal10n-dev - mailman3.qos.ch

[JIRA] Created: (CAL-27) If both charset and defaultCharset are empty, CAL10N must use UTF-8, not the default encoding for your Java platform to read resource bundles
by Andrew Fink (JIRA) 09 Jan '11

09 Jan '11

If both charset and defaultCharset are empty, CAL10N must use UTF-8, not the default encoding for your Java platform to read resource bundles --------------------------------------------------------------------------------------------------------------------------------------------- Key: CAL-27 URL: http://jira.qos.ch/browse/CAL-27 Project: CAL10N Issue Type: Bug Reporter: Andrew Fink Assignee: Ceki Gulcu Please use UTF-8 as default encoding if user hasn't entered charset and defaultCharset explicitly. Latin/ASCII users won't see difference, but users with languages with national characters will feel relief. For many languages "platform default encoding" is ugly buggy _nothing_ / _random_ (for russian for example)! For russian, platform default encoding can have several possible values including UTF-8! You can add defaultCharset="" - for backward compatible random platform default encoding -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

[JIRA] Created: (CAL-15) The variant part of Locale is ignored
by Sascha Broich (JIRA) 01 Dec '10

01 Dec '10

The variant part of Locale is ignored ------------------------------------- Key: CAL-15 URL: http://jira.qos.ch/browse/CAL-15 Project: CAL10N Issue Type: Bug Reporter: Sascha Broich Assignee: Ceki Gulcu The Locale has a variant part which is currently not evaluated by the ResourceBundleFinder. This has to be changed to keep it consistent with the Java ResourceBundle behaviour. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

3 4

[JIRA] Created: (CAL-26) Implement an APT plugin to check that all enums has a key in the corresponding properties file and vice versa
by Stig Kleppe-Jørgensen (JIRA) 19 Nov '10

19 Nov '10

Implement an APT plugin to check that all enums has a key in the corresponding properties file and vice versa ------------------------------------------------------------------------------------------------------------- Key: CAL-26 URL: http://jira.qos.ch/browse/CAL-26 Project: CAL10N Issue Type: New Feature Reporter: Stig Kleppe-Jørgensen Assignee: Ceki Gulcu Priority: Minor To enable real compile time verification of the enum vs properties file, an APT plugin can be used. This can check that all enums has a property and all properties has an enum and fail the build if something is missing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

2 2

[JIRA] Created: (CAL-25) Message retrieval relies on toString instead of name()
by Michael Osipov (JIRA) 29 Sep '10

29 Sep '10

Message retrieval relies on toString instead of name() ------------------------------------------------------ Key: CAL-25 URL: http://jira.qos.ch/browse/CAL-25 Project: CAL10N Issue Type: Bug Reporter: Michael Osipov Assignee: Ceki Gulcu Priority: Critical As you can see [here http://cal10n.qos.ch/xref/ch/qos/cal10n/MessageConveyor.html#81] it realies on .toString(). My enums are richer than the basic manual depicted here thus I have overridden to string. Resouce trievals fails because the key name differs from the string represenation. Line 81 should work on #name() only and not rely #toString() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

[JIRA] Created: (CAL-24) IMessageConveyor throws MessageConveyorException which it shouldn't
by Michael Osipov (JIRA) 24 Sep '10

24 Sep '10

IMessageConveyor throws MessageConveyorException which it shouldn't ------------------------------------------------------------------- Key: CAL-24 URL: http://jira.qos.ch/browse/CAL-24 Project: CAL10N Issue Type: Bug Reporter: Michael Osipov Assignee: Ceki Gulcu As you can see here: http://cal10n.qos.ch/xref/ch/qos/cal10n/IMessageConveyor.html#58 The interface mandates all implementors to optionally throw this exception. This design has tow flaws: 1. This exception is not documented in the JavaDocs 2. It extends the RuntimeException (unchecked exception), which indicates an unrecoverable state of the client. Such exceptions should never be declared in the throws block since the client can't do anything about it. See reference here: http://www.javapractices.com/topic/TopicAction.do?Id=129 and Joshua Bloch's great book: http://www.amazon.de/Effective-Java-Programming-Language-Guide/dp/032135668… -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

[JIRA] Created: (CAL-23) Parser fails to load properties file if only key exists
by Michael Osipov (JIRA) 24 Sep '10

24 Sep '10

Parser fails to load properties file if only key exists -------------------------------------------------------- Key: CAL-23 URL: http://jira.qos.ch/browse/CAL-23 Project: CAL10N Issue Type: Bug Reporter: Michael Osipov Assignee: Ceki Gulcu Cal10n fails if a property looks like this: "KEY =" no chars after the equals sign. The exception is: Exception in thread "main" java.lang.IllegalStateException: Unexpected token Token(EOL) at ch.qos.cal10n.util.Parser.E(Parser.java:76) at ch.qos.cal10n.util.Parser.parseAndPopulate(Parser.java:60) at ch.qos.cal10n.util.CAL10NResourceBundle.read(CAL10NResourceBundle.java:57) at ch.qos.cal10n.util.CAL10NResourceBundle.<init>(CAL10NResourceBundle.java:50) at ch.qos.cal10n.util.CAL10NResourceBundleFinder.makePropertyResourceBundle(CAL10NResourceBundleFinder.java:83) at ch.qos.cal10n.util.CAL10NResourceBundleFinder.getBundle(CAL10NResourceBundleFinder.java:51) at ch.qos.cal10n.MessageConveyor.lookup(MessageConveyor.java:111) at ch.qos.cal10n.MessageConveyor.getMessage(MessageConveyor.java:77) Regular java.util.Properties does not fail. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

[JIRA] Created: (CAL-22) Parser fails to load properties file if value contains space only
by Michael Osipov (JIRA) 24 Sep '10

24 Sep '10

Parser fails to load properties file if value contains space only ----------------------------------------------------------------- Key: CAL-22 URL: http://jira.qos.ch/browse/CAL-22 Project: CAL10N Issue Type: Bug Reporter: Michael Osipov Assignee: Ceki Gulcu Cal10n fails if a property looks like this: "KEY = " or more spaces after the equals sign. The exception is: Exception in thread "main" java.lang.IllegalStateException: Unexpected token Token(EOL) at ch.qos.cal10n.util.Parser.E(Parser.java:76) at ch.qos.cal10n.util.Parser.parseAndPopulate(Parser.java:60) at ch.qos.cal10n.util.CAL10NResourceBundle.read(CAL10NResourceBundle.java:57) at ch.qos.cal10n.util.CAL10NResourceBundle.<init>(CAL10NResourceBundle.java:50) at ch.qos.cal10n.util.CAL10NResourceBundleFinder.makePropertyResourceBundle(CAL10NResourceBundleFinder.java:83) at ch.qos.cal10n.util.CAL10NResourceBundleFinder.getBundle(CAL10NResourceBundleFinder.java:51) at ch.qos.cal10n.MessageConveyor.lookup(MessageConveyor.java:111) at ch.qos.cal10n.MessageConveyor.getMessage(MessageConveyor.java:77) Regular java.util.Properties does not fail. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

[JIRA] Created: (CAL-8) MessageConveyer.lookup() uses wrong classloader
by Pete Muir (JIRA) 25 Aug '10

25 Aug '10

MessageConveyer.lookup() uses wrong classloader ----------------------------------------------- Key: CAL-8 URL: http://jira.qos.ch/browse/CAL-8 Project: CAL10N Issue Type: Bug Environment: cal10n 0.7 Reporter: Pete Muir Assignee: Ceki Gulcu MessageConveyer uses this.getClass().getClassLoader() as the classloader to use to search for resource bundles. If you wish to install cal10n as a installed library in an application server (or in any case where the cal10n jar is placed on a parent classlaoder), the classloader of the classes using cal10n may not be searched for resource bundles. I would suggest using declaredClass.getClassLoader(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

3 3

[JIRA] Created: (CAL-21) Improvements for CAL10NResourceBundleFinder class
by Nick Belaevski (JIRA) 24 Aug '10

24 Aug '10

Improvements for CAL10NResourceBundleFinder class ------------------------------------------------- Key: CAL-21 URL: http://jira.qos.ch/browse/CAL-21 Project: CAL10N Issue Type: Improvement Reporter: Nick Belaevski Assignee: Ceki Gulcu 1. In makePropertyResourceBundle(...) method reader is created twice: once by calling toReader(...) method, the second time in inline code 2. In the same method as 1 - shouldn't writer be closed in final block? 3. openConnectionForUrl(...) uses URLConnection#setDefaultUseCaches(...) affecting all URLConnection being created. There's setUseCaches(....) specific for this connection object -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

[JIRA] Created: (CAL-20) MiscUtil uses identity comparison for string
by Nick Belaevski (JIRA) 24 Aug '10

24 Aug '10

MiscUtil uses identity comparison for string -------------------------------------------- Key: CAL-20 URL: http://jira.qos.ch/browse/CAL-20 Project: CAL10N Issue Type: Bug Reporter: Nick Belaevski Assignee: Ceki Gulcu In method ch.qos.cal10n.util.MiscUtil.urlToFile(URL) there's a code: if(url.getProtocol() != "file") that uses identity comparison of strings -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0