You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2014/08/26 23:33:59 UTC

[jira] [Commented] (OAK-260) Avoid the "Turkish Locale Problem"

    [ https://issues.apache.org/jira/browse/OAK-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111375#comment-14111375 ] 

Hoss Man commented on OAK-260:
------------------------------

FWIW: Locale.ROOT and the non-platform default methods can help you avoid this type of problem.

And the forbidden-apis checker can help ensure that you only use the non-platform default methods...

http://blog.thetaphi.de/2012/07/default-locales-default-charsets-and.html
https://code.google.com/p/forbidden-apis/


> Avoid the "Turkish Locale Problem"
> ----------------------------------
>
>                 Key: OAK-260
>                 URL: https://issues.apache.org/jira/browse/OAK-260
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core, jcr
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>             Fix For: 1.1
>
>
> We currently use String.toUpperCase() and String.toLowerCase() and in some cases where it is not appropriate. When running using the Turkish profile, this will not work as expected. See also 
> http://mattryall.net/blog/2009/02/the-infamous-turkish-locale-bug
> Problematic are String.toUpperCase(), String.toLowerCase(). String.equalsIgnoreCase(..) isn't a problem.



--
This message was sent by Atlassian JIRA
(v6.2#6252)