I read some posts on this forum about the best architecture to adopt. I am aware that separate projects for each language are strongly advised, as well as the use of Lingo. However, our translation team already has some processes in place and they think having one project with all languages is the best option. It probably means I have to maintain separate TOCs for each language, but I can figure something out. Or they can handle it.
Based on these requirements, I came up with a proof of concept that handles translation quite well by relying on Condition Tags (which is also a best practice, from what I have heard). There is but one remaining item to be translated: auto-numbering. It is currently handled at the CSS level. Here is an example for h1 headers:
Code: Select all
h1
{
mc-auto-number-class: ChapAutoNum;
mc-auto-number-format: 'CH:LESSON {chapnum} ';
}
My question is: Is there a simple way to handle the translation of this 'LESSON' term? I would like to handle the routing at the Target level, again with Condition Tags. So far, I have created a Condition Tag Set called i18n with as many fields as supported languages (EN, FR, DE...). Ideally, I would like to include or exclude some languages at the Target level, and the auto-numbering would automatically adapt.
Is this achievable? I could not apply Condition Tags to CSS stylesheets as I did for the other Resources (Page Layouts, Topics).
Do you think I need separate stylesheets for each language?
Thanks in advance for any tip/experience you might share,
Laurent