Basic concept for Flare projects with multiple source languages

[mareike]

Hello,

We are looking for a suitable translation concept for our Flare projects. We would like to use MadTranslations as our translation service provider.

Current status:

• We use several brand-specific Flare projects within a corporate group. Example: One Flare project for company A, one Flare project for company B, one Flare project for company C
• There are two Flare projects for company A, one is English-language (let's call it A-EN), the other is German-language (A-DE).
  Companies B and C only use one English-language Flare project each.
• We have a superordinate template Flare project from which the brand-specific Flare projects import shared files (stylesheets, snippets, layouts). The template also contains language-dependent snippets, e.g. headers and footers for PDF targets.
• In the two Flare projects A-EN and A-DE, certain topics are now to be translated from English into German and other topics are only to be translated from German into English.
• The Flare projects A-EN and A-DE therefore have a different number of topics, of which only some exists in both languages. There is therefore no leading language, but both Flare projects each have their own source topics that have to be translated into the other language. This should remain the case, as the topics are sometimes written in German, sometimes in English, depending on the author.
  
  Projekte_Schnittmenge.png

• PDF attachments and graphics exist redundantly in both A-EN and A-DE.

Objectives:

• We do not want to use redundant data (PDF attachments, graphics, etc.).
• While a translation is in progress, it must be possible to continue working on the projects.
• It must still be possible to use the template project.

Possible Solution:

• We merge A-EN and A-DE into a new Flare project, which would then be bilingual.
• We would divide the content between the two main folders EN and DE.
• German-language and English-language topics would be marked with condition tags for the respective language.

Example:

• English-language topic: Content Explorer\DE\Machine-Instructions.htm
• German-language topic: Content Explorer\EN\Machine-Instructions.htm
  
  Example.png

Questions:

• How is it ensured that the correct language-dependent layout (header and footer) is used?
• How is the translation into other languages (except DE and EN) handled? Is a new Flare project created for each translation? When translating into a Spanish Flare project, do the main folders \DE and \EN remain as they are in the source project?
• Which concept do you use for translations?

[trent the thief]

I think this might be a discussion to start have your MC sales rep and MC support. They'd have a better idea of what's possible than most users.