• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 137 subscribers
  • Views 922 views
  • Users 0 members are here
Options
Related

Can I cascade Automatic Generation of Target Languages to all children of a map

Ann Jensen

Hi,

I want to use https://docs.sdl.com/787645/421107/sdl-tridion-docs-14/translation-management and wonder if I can set the Requested Languages on a ditamap and have that selection cascade down to any child topics in the map?

Thanks,

Ann
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Hi Ann,

    Although your question looks short, it is a complex answer depending on your process, translation vendor/integration and more. So my answer will be highly generic.

    • First of all, the "In-Context Perfect Matching" (pretranslation) is deprecated, so nothing you want to roll-out in a new environment.
    • Your question seems to suggest the PULL translation management model. So the languages on a map (requested languages field) are inherited on the topics (inherited languages field) used in the map and in turn on the library topics used in the topics, etc. This model is not the primary solution anymore and is super-seeded by the PUSH translation management model. Main problem with PULL is that when you release you eventually gets translation stubs for all languages so requiring/suggesting translations. This might be your model, but still I would advise a conversation with PS before you go there.
    • The PUSH translation management model, and these days a push from publication versions (so exactly the versions used in the baseline) is what people use. Explicit control on which versions will be pushed for translation over Translation Organizer (so Translation Jobs).

    Best wishes,
    Dave
Reply
  • 0

    Hi Ann,

    Although your question looks short, it is a complex answer depending on your process, translation vendor/integration and more. So my answer will be highly generic.

    • First of all, the "In-Context Perfect Matching" (pretranslation) is deprecated, so nothing you want to roll-out in a new environment.
    • Your question seems to suggest the PULL translation management model. So the languages on a map (requested languages field) are inherited on the topics (inherited languages field) used in the map and in turn on the library topics used in the topics, etc. This model is not the primary solution anymore and is super-seeded by the PUSH translation management model. Main problem with PULL is that when you release you eventually gets translation stubs for all languages so requiring/suggesting translations. This might be your model, but still I would advise a conversation with PS before you go there.
    • The PUSH translation management model, and these days a push from publication versions (so exactly the versions used in the baseline) is what people use. Explicit control on which versions will be pushed for translation over Translation Organizer (so Translation Jobs).

    Best wishes,
    Dave
Children
No Data