Great, thanks for the translation.
I will add it to the next version. Maybe this will be our first RC.
Regarding the translations, "oeh" sent me an example by PN I'd like to answer here.
Take for example the Scroll to top droplet . It has an output text "Scroll to top" this text needs to be translatable and to work on multilingual sites.
Hm. In this case, the markup has to be added to the page "by hand". I think I know what you mean - you'd like to insert something like
<a id="toTop" href="#">^ <?php echo translate('Scroll to Top'); ?></a>
into the page and have translations for different page languages automatically. I'm not sure if this should be a feature for jQueryAdmin. But, on the other hand, it's not very hard to implement. (It's already implemented in wbTemplate, which is part of the wblib I created.)
I don't know if there are already solutions for this. (Droplets or other modules.) Maybe someone else knows.
Just to fantasize a bit... I could think of an implementation like this:
* A plugin can have language files, like modules have.
* The jQueryAdmin droplets regard some kind of markup, for example: <!-- jquery begin translation --><Text><!-- jquery end translation -->
* If it finds a markup like this in the page, and if the plugin has language files, it tries to find a translation for the <text>, leaving it as is if none is found
With this solution, the <text> will still work if the jQueryAdmin droplet is not used (or a translation is not available).
A translation file may look like this:
'This is text to be translated' => 'This is the translation',
And the markup in the page would look like this:
<!-- jquery begin translation -->This is text to be translated<!-- jquery end translation -->
If the droplet finds a translation for that text, the markup will be replaced with that text. If not, you will still see the original text on the page.But!
As v1.x is in Beta state now, this would be a feature for a future version. (2.x or something)