By Elisa Foltyn on 2018-05-29 07:18 in GSoC 18 Multi-language Association

GSoC Team Meeting 14.05.2018

Present at the Meeting:

Christiane Maier-Stadtherr (Mentor)

Elisa Foltyn (Mentor)

Marco Dings (Mentor)

João Reys Santos (Mentor)

Wang Yuchao (Student)

  • Elisa prepared some (quick) Drafts for the multilanguage Associations in Joomla 4 (See Attachments for Details)

  • Workflow:  if the article is completely untouched: The article shows the frontend information specified in the language settings (Attachment 3) or specified in Core with the content of the article in the root language, as long as the setup fallback language is not available.

    • Means for contents: Article is showing its specified language -> if not available -> associated Article in fallback language -> if not available -> associated Article in root language

    • If no other specified, the fallback language is always the root language

    • Marco Dings mentioned to keep an eye on language strings too. They should have the same fallback logic (currently Joomla falls back to en-GB if string is missing). We should not confuse article contents with language strings.

    • Example:

      • Root language is Italian
        Content (Article) language is Portuguese
        Fallback is set to Spanish

        If Article is not translated yet

      • Looking for associated Spanish Article

      • If fallback Spanish is not existing
        fallback to root language Italian
        if associated article in Italian is missing
        fallback to English anyway

(Same logic for language strings)

  • Wang already implemented parameters in the code

  • Automatic states and Change states: Example: User clicks on “Save” in a German article. 5 Articles with automatic associations are created at this point. They need a State (published, unpublished ...) Or when hopefully the workflow process will be included in Joomla 4 it can have a workflow state (like untranslated).

  • Christiane mentioned to keep care of what happens if a content language is deleted / root language changed. This needs thoroughly testing.

  • Shared Link from Amazon where the Idea for the project was born: This documentation does not exist in German yet. So they fallback to English and show a frontend information that this content has not been translated yet. But at least it's there.

  • Automatic Associations have to be done for Menu items, Categories, Articles

  • Wang gave a project scope of 2 weeks (28.05.2018) for that tasks

  • João created the staging branch during the meeting

We welcome a new team member and Mentor Lavinia Popa-Rössel, she can't attend our Monday meetings now, but possibly later. Lavinia is writing her Master Thesis on the German university of Gießen about Multilanguage Associations. The topic of the Thesis is to retrieve that the root language has been changed and give this information back to the translated articles. With a view that shows "what" has been changed in the root. Lavinia will work independently on that topic on our GSoC staging but will be also in our team for general discussions, help as a mentor and member of our team.

Thank you everyone for your great work in the team!

Attachment 1

ml rootlanguage

Setting language as root

Draft of the content language overview, where the user can set up the root language of the site and the fallbacks

Attachment 2

ml params

Parameters for each language:

Draft shows that a new settings tab is available in the language with multi language options (appears only on Multilanguage sites of course) - Parameters have to be discussed.



Attachment 3

ml modal

Dialog after saving a Multilingual Article for the first time:

  • User clicks on Save in an article on a multilingual website the very first time and gets this popup (Settings are later available in a plugin)
  • Possibly the user could inline edit the title of the new items, if user does not want to, just the language tag is added in the title alias (open for other ideas)