Many thanks @George - thatās a great solution. I think this will be a very useful feature generally and works perfectly for language switching.
I was wondering about how to set defaults in case no cookies are set, at least for critical text - now itās just a matter of setting a defaut in the normal way with the data formatter. For inner text, I was pleased to see dmx-html also works too.
Wappler Translation Tutorial
Took me hours to gather all informations of the 3 steps you mentionned but it was fun to learn many other things along the way. And I wanted to contribute to thank this amazing community.
So here is a quick tutorial (hopefully) from A to Z.
I'm not really comfortable with Wappler terminology yet but the step by step approach should allow anyone to understand the workflow.
Step by step video :
Ressource :
SQL dump : Dropbox - translations.sql - Simplify your life
Any feedback/improvements are welcomed ! 
Thank you Jeoff, very well presented and I love the accent.
Hi,
Cannot make it work. Translations are properly loaded from the database, but data doesn't to be stored in the array (after toKeyedObject) to be displayed after. Is there a way to control this array (if exists and what is in) with chrome debugger ?
Usually, this is because the formatter script is not included in the code :
If you can send a screenshot or the actual page link, it will be easier to help you though ! 
I have already added it with no success. But if i add it, do i need to add this script also as @george wrote previously ? Should we have both ?
No itās not needed anymore as itās shipped with the formatter script now.
Ok, thankās for you help, i think i will have to start from scratch again.
Iām still interested to know if there is a solution to control whatās going on in the chrome debugger
@jeoff75, how do I convert an array into keyed object? I tried looking for this formatter, but no luck. Thanks.
Look at the source here :
https://login-boilerplate.usa-sandbox.space/app_create_user.php
Iāll try to upload the project to git this week-end so that you can have a look from within wappler.
Thanks lot mate. I did watch the video you put together and figured it out, it was a lifesaver. The toKeyedObject is not available through the UI formatter, entered it manually, thanks again 
It is available in the formatter - not originally, but I think it was added quite a few versions ago:
Thanks @TomD
Not finding at my end on an array variable. I wonder what the difference, is your screenshot from a server action?
Also, would you know if Keyed Object just another term for Keyed Array aka Associate Arrays in javascript?
My screenshot was not from a server action. I think the difference is that I used a variable rather than an array component. This was the variable and value:
<dmx-value id="lang" dmx-bind:value="sc_lang.data.qry_lang.toKeyedObject('textkey', 'text')"></dmx-value>
The query returns an array of keys and text (translations). Eg this displays the translation for 'terms' (based on a cookie storing the selected language):
{{lang.value.terms}}
although I actually include a default: {{lang.value.terms.default("Terms")}} (in case the cookie is not set).
Just implemented all of this, and it worked like a dream!
Many thanks to @jeoff75 for the great video and cool accent, @George for putting the toKeyedObject function into Wappler, and @TomD for the screen shot of how to access it!
@George, it would be great when something new is put in Wappler if posts like this one could be updated to note the changeā¦ it looks like it could have saved @djeorges quite some hassle!
It took me ages to find the toKeyedObject conversion in the Wappler GUIā¦ so here is what to do:
My Implementation
A few points about how I implemented it that I hope will help those following this path:
My index is a number. Felt like it may be faster on indexing and saved me inventing yet another naming scheme. Numbers are 4 digit, in the form xyyz, where x is the area of the app (1=contacts, 2=orders, 3=finances, 4=products), yy is the specific field/view being described (01=first name, 02=last name), and z is the aspect to describe (0=item title/content, 1=description, 2=placeholder, 9=help text).
So for example, help text for First Name field is 1019 and placeholder for Last Name field is 1022.
I use the 5 digit language codes, so en-GB, en-US, es-ES etc. It is important an american user sees the word ācolorā rather than ācolourā to feel really at home with the app.
Sometimes I wonāt have all the translations for every piece of text in the app, especially when translating en-US for example, so I have the idea of a fall-back languageā¦ most commonly en-GB, but could be es-ES.
To implement the fall-back language, I access the complete text for the application (apptext) via a mySQL procedure get_apptext(language). When called, that finds all the apptext in that language and then then substitutes all that is missing from the fall back language.
I will have users who have āis_language_editorā and āedit_languageā fields. When both are enabled, there will be tiny button next to each piece of text which will enable a modal where they can go in and edit their language version for that piece of text.
The app will be developed in en-GB which I call the base language. I plan for each field in the database to have a modified_date field, and some system where the language editors can see when the en-GB modified date field for an apptext is later than that for their language, so they are highlighted to the need to update their content. Details of that to be worked out!
I hope all that helps!
Best wishes,
Antony.
Well we try but sometimes we miss some topics as there are many.
You can actually post such tips directly as docs! Just make a post under the Docs category and it will be automatically included in our official docs.
You can also add it to the index by linking to it from an āabout xxx category@ from the docs category that it fits.
We plan to restructure the docs categories and organization soon and any help will be greatly appreciated.
Hey @George, yes, I understand the challenge of trying to manage soooo many wonderful posts from that point of view! I guess it is upon all of us to try to update a post we know about when a new feature is added.
Iām not so confident that my ramblings consitute a Wappler doc, but you are welcome to move it over there if you think it meets the grade!
Thanks for all your wonderful input,
Antony.
I have a new project that requires localization. I am fiddling with the i18next library.
So far so good. As I am just testing I switch languages clicking the form button.
My implementation relies on json files instead of querying the database I have files for each page and language. This means that it is blazing fast as you can see 
I still need to take a deeper look to check the implications as I might be losing some App Connect goodness like bindings and formatters that could come in handy.
You could potentially do something similar with the App connect json data source component and skip the database call. Although you would be missing on the translation goodies that come with this library like plurals, fallbacks and things of the sort.
