[
https://issues.apache.org/jira/browse/JENA-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damian Steer updated JENA-177:
------------------------------
Attachment: jena-icu4j.patch
IRI-icu4j.patch
So nearly there:
IRI-icu4j.patch and jena-icu4j.patch almost remove our dependency on icu4j. In
two cases I have written a couple of crazy functions to work around the jdk
missing unicode property information.
However we have a problem with java.net.IDN (puny code). Like many jdk
replacements it clearly originates in icu4j, but it doesn't act in the same
way. Is this a jdk bug?
icu4j:
IDNA.convertIDNToASCII("André",
IDNA.USE_STD3_RULES | IDNA.ALLOW_UNASSIGNED);
works.
jdk:
IDN.toASCII("André",
IDN.USE_STD3_ASCII_RULES|IDN.ALLOW_UNASSIGNED);
"java.lang.IllegalArgumentException: Contains non-LDH characters"
I've included the non-working replacement commented out in the IRI patch.
Anyone have a clue??
> If possible remove dependency to ICU4J by using Java built-in functionality
> ---------------------------------------------------------------------------
>
> Key: JENA-177
> URL: https://issues.apache.org/jira/browse/JENA-177
> Project: Jena
> Issue Type: Wish
> Components: IRI, Jena
> Reporter: Thorsten Möller
> Priority: Minor
> Attachments: IRI-icu4j.patch, IRI.patch, jena-icu4j.patch, jena2.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Jena-core and IRI currently depend on ICU4J for implementing Unicode support.
> Since ICU4J is rather heavyweight of which a rather small fraction is used,
> we should check if there is a way of implementing the functionality in an
> alternative way, either by (i) using built-in (standard) Java classes, (ii)
> other libraries that are already dependencies, or (iii) in a completely
> alternative way. This is also supported by the fact that since relevant parts
> have been initially implemented, Unicode support has been considerably
> extended in Java, see
> http://java.sun.com/developer/technicalArticles/javase/i18n_enhance/.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
