Please add puri-unicode

[HiTECNOLOGYs]

Hello,

It's fork of cl-puri with UFT-8 characters support.

Source code can be found here: https://github.com/archimag/puri-unicode.git
Author: Andrey Moskvitin, based on Franz inc. code
License: LLGPL

[quicklisp]

The puri.asd file clashes with the existing puri.asd. Either this puri must become the new official puri, or its changes must be merged into the real puri.

[HiTECNOLOGYs]

Ok, I'll try to contact the developer and tell him about this. Are there any other ways to solve this problem except changing system name? This library was considered as an optional choice for those who want to use unicode characters in URIs.

[quicklisp]

It could be available in another dist.

[orthecreedence]

Hi, one of the users of one of my libraries (wookie) is requesting I use puri-unicode instead of puri so they can use unicode routes. Changing puri-unicode seems this is a dead issue, but I'd like to make progress on it. Is the only issue with this library the name of the puri.asd file? In other words if I submit a PR that renames puri.asd to puri-unicode.asd, can the two projects exist side-by-side with no further changes? Or do the package names themselves have to change in the puri-unicode package to not conflict?

Thanks!

[HiTECNOLOGYs]

@orthecreedence, it's not just that. I tried contacting Andrey and he said that the point of library, in his opinion, is to supersede puri because many libraries suffer "Unicode problem" because of puri. I agree with this statement, ranaming isn't a way out of this situation. The issue is still alive out there (archimag/puri-unicode#3) and the suggested solution was to add "virtual" pakages to QL. Zach is still in the process of thinking about this, as far as I know. I guess all you can do is write it yourself and make a pull request hoping that it's good enough for upstream or wait until Zach figures what would be the best to do. I tried implementing this myself but I didn't get too far with my programming and design skills.

[quicklisp]

puri-unicode could work.

It would also be nice to have the changes merged upstream in PURI, I think.

[HiTECNOLOGYs]

Indeed. Merging puri-unicode into upstream is definitely good idea. @orthecreedence, can you handle this or I should? Asking Andrey if he wants his fork to be merged can also be good idea, I suppose.

[orthecreedence]

My availability for my github projects has been sporadic at best lately, let's both plan to talk to the puri maintainers/Andrey and bug them about merging in puri-unicode (since I might drop the ball on it anyway). If it can sneak into the main puri project, that would probably be the best solution.

[HiTECNOLOGYs]

Andrey doesn't have any objections against merging. He also said that Kevin didn't want new not-really-necessary dependencies (puri-unicode uses babel. It can be dropped as most implementations provide Unicode support, but I agree with Andrey: using babel is somewhat better). If somebody can convince the developer of puri that puri-unicode is worth merging, it'll be excellent.

[orthecreedence]

I emailed Kevin Rosenberg (maintainer of puri) and asked about merging, waiting to hear back now.

[lu4nx]

Kevin Rosenberg reply message yet?

[orthecreedence]

Nope, doesn't seem to be responding. Keep on eye on quri. Might be the eventual replacement of puri.

[quicklisp]

I think it would be better to use quri at this point.