Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ICU4J dependency #57

Open
gsmet opened this issue Jul 1, 2015 · 3 comments
Open

ICU4J dependency #57

gsmet opened this issue Jul 1, 2015 · 3 comments

Comments

@gsmet
Copy link

gsmet commented Jul 1, 2015

Hi Santiago,

We are using galimatias for quite some time now without any issue.

You recently introduced a dependency to ICU4J in this commit 5ce2cb9 and I was wondering if there was a way to fix the issue without adding this dependency.

You might have missed it but ICU4J is a 10 MB jar which is quite huge.

Thanks for your work.

@dadmin-admin
Copy link

+1

@smola
Copy link
Owner

smola commented Dec 19, 2018

As far as I know, ICU4J contains the only full IDNA:2008 implementation in Java, which is required to fully support the URL standard. I will consider any other implementation if it is available. It might also be possible to extract a subset of ICU4J and vendor it here, but I didn't check how much code would be required.

PRs or suggestions are welcome.

@sideshowbarker
Copy link
Contributor

sideshowbarker commented Dec 20, 2018

As far as I know, ICU4J contains the only full IDNA:2008 implementation in Java

Right. Specifically, java.net.IDN still doesn’t have IDNA:2008 support. Neither does the GNU Libidn Java port. (The GNU Libidn2 C library implements IDNA:2008, but there’s no Java port of it.)

which is required to fully support the URL standard. I will consider any other implementation if it is available. It might also be possible to extract a subset of ICU4J and vendor it here, but I didn't check how much code would be required.

It seems to me that the level of effort required to extract what’s needed for galimatias’s purpose would be quite high. So while I’m not super happy either with the ICU4J dependency, it really does seem like we’re pretty much stuck with it — at least if the goal continues to be to provide an implementation that conforms to the URL standard (which I strongly agree it should be).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants