WebsiteBaker 2.13.8 is now available!
R.I.P Dietmar (luisehahne) and thank you for all your valuable work for WBhttps://forum.websitebaker.org/index.php/topic,32355.0.html
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 likeCode: [Select]<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 foundWith 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:Code: [Select]<?php$LANG=array( 'This is text to be translated' => 'This is the translation',);?>And the markup in the page would look like this:Code: [Select]<!-- 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.
<a id="toTop" href="#">^ <?php echo translate('Scroll to Top'); ?></a>
<?php$LANG=array( 'This is text to be translated' => 'This is the translation',);?>
<!-- jquery begin translation -->This is text to be translated<!-- jquery end translation -->
Well, the solution I suggested was meant for jQueryAdmin only. But maybe someone likes to create an independent module.
<!-- jQueryAdmin: unable to load preset [4] --><!-- jQueryAdmin: unable to load preset [featureList] -->
[[jQueryInclude?plugin=<Name>]]
[[jQueryInclude?preset=<Name>]]
[[jQueryInclude?plugin=galerij]]
<!-- jQueryAdmin: unable to load preset [default] -->