At a glance it's looking good. I'll pull it down shortly and test it.

So we're going with ini files and keys....

Until #124 is merged, yes, since that's what's already in place.

Looks like duplicated work to me if we still consider merging #124...

Look here for example.. or here....

I've got no issue merging #124. So do we want to do it now or wait? I've still got to write my JWC session for this here project, so I'd rather larger changes like that get merged before I've written any slides... LOL

We could include a language switcher with flags - that would look nice on a slide, don't you think ? ;)

Totally!

Oh, but hey... a BIG for starting with client side validation @b2z

Well I did not know that we have decided to drop usage of ini :( #124 is the final decision? What is the right way of language string usage?

Nevermind I found it :)

// template.twig
<label>
    My String

    // change to:
    {{ translate("My String") }}

    // **OR** just use a pipe and a shortcut:
    {{ "My String"|_ }}
</label>

I don't think there is a "right" way...
The proposal of #124 is (also) making translations "lazy", so you don't need those COM_FOO_KEY's any more.. unless you want them (maybe for long descriptions) ;)

That's the cool thing about this project. The right way is what we decide. We aren't stuck in the confines of another application's structure or required to use the tools of a single entity, we can implement what we want and how we want, and if something on the market doesn't suit our needs, we can just as easily write it ourselves.

Amen :)

Nevermind I found it :)

Oh that's what you meant by "right" :)

Yeah, and speaking of which - (not which is "right"..) maybe you can find some 5min to test this - it might save you some 10min when working with language files ;)

So, on topic (apologies for previous OT..) while checking out this branch I noticed that I also get this beautiful error about the wrong Http object.. (see) - should I lower my error_reporting ? :(

He needs to sync up the branch, your PR to fix that is merged.

Yeah, that's why I was wondering if I am the only one....

@test works as expected.
Not tested with a non-english language ;)

Not too shabby