Give us feedback: what features do you want to see next?
The most comprehensive library of Javascript i18n classes available
Brought to you by:
ehoogerbeets1
Menu
▾
▴
Hi all,
JEDLSoft is looking for feedback on the sort of features that you want to see next in the next feature release of ilib. We have put a feature backlog together on the wiki at [roadmap], but don't feel limited to just that list. If you want something not on the list, let us know that too!
Thanks,
Edwin
Related
Wiki: roadmap
Hi,
I'm interested in a complete tutorial. It ends with chapter 5.6 but I want to see the localization tool chapter that is referenced in the TOC. The doc for iLib can't be opened in Sourceforge, even with an account.
Regards Achim
Sorry, that was a slip up. The docs do end with Chapter 5.6 but I hadn't updated the TOC before publishing it. The localization tool and the zone info compiler are not open-sourced. (Or at least not yet.)
When you say the doc for ilib cannot be opened... which url do you mean? The URL to the reference docs is not protected by any security:
http://docs.jedlsoft.com/ilib/jsdoc/
and the wiki pages on this sourceforge site should be publically available too. Let me know which one you had problems with and I'll try to figure out what is going on. Thanks!
Hi Edwin,
Thanks for this. I am looking for locale specific sorting routines. I'd recommend incorporating the Unicode Consortium's CLDR standards for implementing this. But, basically I don't see any way to sort properly lists appearing on a page other than specifically and manually having a linguist do the sort for each language. What a pain.
Last edit: William Kirtz 2012-10-30
Hi William, we are working on implementing the Unicode Collation Algorithm which depends on tailoring data from CLDR. It is on the backlog, but I can prioritize it higher if needed. (See http://www.unicode.org/reports/tr10/ )
I was thinking perhaps implementing a relatively quick-and-dirty but non-UCA-compliant collation algorithm for languages that use the Latin script. As long as I get the API right, then I can fill in the correct and full UCA "under the covers" in a later release so that client code would not need to be modified. It would just start working better. Would that be of interest? What locales do you need to support?
Hi, Latin scripts isn't what we are concerned about, although that would be nice to have. Really what we are looking for are the Asian scripts: CJK first then Viet, Thai, etc. It's the really tough ones that are our principal concerns.
I see... all the difficult ones! Well, there is a bunch of infrastructure we have to build first before going tackling the Asian collation problem, so it will be a while before we get there.