[
https://issues.apache.org/jira/browse/LANG-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904146#action_12904146
]
James Carman edited comment on LANG-285 at 8/30/10 9:12 AM:
------------------------------------------------------------
This seems like an awful lot of code for something that's 1 or 2 lines of code
if java.text.Normalizer is available from JDK6.
was (Author: jwcarman):
Is this code going to change when Oracle decides to change the name of the
class to come.oracle.*? They've already messed up quite a few folks by
changing the JVM name on their latest release from what I understand. Also, is
it smart to depend on non-core classes here? What about other JVMs? Will this
code not work on other JVMs?
> Wish : method unaccent
> ----------------------
>
> Key: LANG-285
> URL: https://issues.apache.org/jira/browse/LANG-285
> Project: Commons Lang
> Issue Type: New Feature
> Components: lang.*
> Reporter: Guillaume Coté
> Priority: Minor
> Fix For: 3.0
>
> Attachments: LANG-285-unaccent-using-Collator.patch, LANG-285.patch,
> MapBuilder.java, StringUtilsAccents.patch, unaccent.patch, UnnacentMap.java
>
>
> I would like to add a method that replace accented caracter by unaccented
> one. For example, with the input String "L'été où j'ai dû aller à l'île
> d'Anticosti commenca tôt", the method would return "L'ete ou j'ai du aller à
> l'ile d'Anticosti commenca tot".
> I suggest to call that method unaccent and to add it in StringUtils.
> If we cannot covert all case, the first version could only covert iso-8859-1.
> If you are willing to go forward with that idea, I am willing to contribute a
> patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
