Refactor locale module using Translation about forkcms

@WouterSioen i'll take a look at this when my essay is done, probably it will be during the summer if it still needs to be done then.
Are you guys planning to use the XLIFF format to store the translations?

[WouterSioen]

I think we will still store the translations in a database system to make them editable for clients who don't have access to the repo. Export/import in xliff would be great though.

I guess we better have a chat about this at the meetup 😊

-----Oorspronkelijk bericht-----
Van: "Wouter Sioen" [email protected]
Verzonden: ‎17/‎02/‎2015 8:59
Aan: "forkcms/forkcms" [email protected]
CC: "John Poelman" [email protected]
Onderwerp: Re: [forkcms] Refactor locale module using Translation (#408)

I think we will still store the translations in a database system to make them editable for clients who don't have access to the repo. Export/import in xliff would be great though.
—
Reply to this email directly or view it on GitHub.

[carakas]

@guytarded any update on this?

[jeroendesloovere]

Have the core devs talked about which file format they would prefer; XML, PHP or YAML?

[carakas]

I personally prefer yaml, I've seen those XLIFF and they are just unreadable

[jeroendesloovere]

What do you guys think of the following:

• Yaml files everywhere
• A "locale" module, which "shows" (read-only) all the translations from the yaml files. With the advantage that you can add your "custom overwrite", which will be added to a database table. So if you have no custom overwrites, this database table is empty.

Then the translator library can:

• Load in all yaml files - using its symfony caching mechanism.
• Inject an array in the translator with only the "custom" translations (which you have inserted in the locale module). Because custom overwrites are so rare.

So we have best of both worlds.
=> What do you think?

[jeroendesloovere]

Note to myself: check out this bundle https://github.com/lexik/LexikTranslationBundle

=> Which does exactly what I described.
Loading in files
Overwriting with custom translation.

[carakas]

why would you split that up in two different modules? That will only be confusing