jQmobile Localization and Internationalization - ?
Am looking at what is available for automatic translation of jQuery Mobile objects from a default language to the local language.
Have found the following:
jQuery UI - Distributes a number of jQuery objects pre-built into various languages. Not only is this limited to the specific supported jQuery (not necessarily jQuery Mobile) objects, it also seems to me rather cumbersome having to custom build objects for download.
jQuery Mobile (and other javascript) plugins - About a year ago there was a spate of interest and development, I've found at least 4 javascript implementations that either carry the jQuery name or are javascript so should easily integrate with jQuery Mobile. Problem I've found is that although the app code was written I have not found any which include or dovetail easily into projects which can provide resource files... So a Dev guy would have to also build his language translations from scratch.
Jakarta taglibs - The largest and possibly most comprehensive public library of resource files is possibly the Jakarta Apache Project (https://attic.apache.org/projects/jakarta-taglibs.html), but with two problems... The library is specific to <only> Java, requires compiling in Java to even possibly view and explore the possibility of extracting the contents and... The SVN and project documentation links are dead so who knows what its current status is. It's possible to download libraries from before it became an Apache project, but still... what a headache exploring something which might not even work.
In general, I was expecting a library of resource files specific to jQuery Mobile, especially since many of its objects are just stylized links.
If a fully recommended and complete localization option does not exist, I guess I'd be willing to select one of the plugins and create a public repo for crowd-sourcing the necessary resource files (read - people willing to provide translations for a standard set of words jQuery Mobile objects use). I also have ideas for implementing the distribution and use of these resource files in a far more efficient manner than how jQuery UI now does it.
Looking for thoughts, comments and recommendations,
TSU