Crowdin in-context translation integration

[bdunogier]

EZP-26828

Adds the javascript code that integrates Crowdin's in-context translation UI.

Usage

To trigger translations, the ach-UG translation, specific to crowdin, must be installed. It can be done by running composer require ezplatform-i18n/ezplatform-i18n_ach_ug. The requirement will be added to ezsystems/ezplatform by default.

To trigger the in-context UI, ezsystems/ezpublish-kernel#1889 is required.

TODO

• BazingaTranslationBundle patch (Accept three letters languages willdurand/BazingaJsTranslationBundle#191)
• Clarify where the ach-UG translation files should be taken from / hosted (added instructions + downloadable file)
• Behat scenario ?
• Unit test the subscriber
• Consider changing the subscriber's folder (talk to Nicolas)
• Make the name of the crowdin project configurable (or follow-up ?).
  Would allow any project to use in-context translation.

[nicolas-bastien]

@bdunogier for that point :

Clarify where the ach-UG translation files should be taken from / hosted (added instructions + downloadable file)

I guess it will be distribute in https://github.com/ezplatform-i18n/ezplatform-i18n-ach_UG. ?

[bdunogier]

I guess it will be distribute in https://github.com/ezplatform-i18n/ezplatform-i18n-ach_UG. ?

It would work, yes.

But my issue with that is that you would have to install something else in order to get working a feature that is supposed to work. In-context will just not work without it. I'd rather have it shipped with the product, so that anybody can translate.

[bdunogier]

About the open question above, my plan turns out to be a little more complex:

Given that in-context has been proven to work here, we could:

• move the cookie listener to the CoreBundle.
• keep the shell.html.twig changes in this pull-request and merge them. They're totally harmless unless you trigger the custom language
• add ezplatform-i18n/ezplatform-i18n-ach_ug to the ezplatform requirements. That way, users are free to remove it (note that we MUST tell people to add it to their own composer.json)

Any opinion @dpobel or @nicolas-bastien ?

[nicolas-bastien]

@bdunogier

• Moving the listener to core make sense cause translation collector is already there

• I agree for the two other points

[bdunogier]

Cleanup done !

[bdunogier]

Ping @yannickroger @nicolas-bastien (for the cleaned up version).