Not Considering

Add a choice in the Autocomplete of the baseline to select all Latest Translated versions of an object

Hi,

Many of our users need to ensure all object versions selected in a publication are the latest translated versions for the Requested Language in the output.

It would be very helpful to add an option when Autocompleting the Baseline for Latest Translated Version along with an option to select the related language layer whose translations are required.

Regards,

Ann

Ann Jensen
Parents

  • Hello  ,

    One of the benefits of Tridion Docs our customers value, is that it stores and delivers the same content (having a single source of truth) in different languages through various channels.

    This is to make sure that content consumers will receive the same message across all the languages it was translated into.

    Around this baseline functionality is built. As Joe said “The baseline is language agnostic, and mainly serves to say which versions of which objects are to be in a given publication. The idea is that for a particular object version (say topic version), then all the languages of that are saying the same thing. They are different-language mirrors of the meaning of the source language, whatever that is.”  

     

    This core model drives a lot of functionality in the product and adding a new layer on top would require a lot of effort not only from R&D but also from customers to adopt it.

     One example, the changes in baseline functionality that you are requesting might lead to a situation where the final delivered content will have differences between different languages that are hard to predict and control.

     

    As you correctly pointed out for cases where language has more priority than the message you can use separate publications where you can set a working language to the one that you want to publish.

     So, currently, we are not considering this idea but we appreciate the input and will continue to think of improving use cases such as this.

Comment

  • Hello  ,

    One of the benefits of Tridion Docs our customers value, is that it stores and delivers the same content (having a single source of truth) in different languages through various channels.

    This is to make sure that content consumers will receive the same message across all the languages it was translated into.

    Around this baseline functionality is built. As Joe said “The baseline is language agnostic, and mainly serves to say which versions of which objects are to be in a given publication. The idea is that for a particular object version (say topic version), then all the languages of that are saying the same thing. They are different-language mirrors of the meaning of the source language, whatever that is.”  

     

    This core model drives a lot of functionality in the product and adding a new layer on top would require a lot of effort not only from R&D but also from customers to adopt it.

     One example, the changes in baseline functionality that you are requesting might lead to a situation where the final delivered content will have differences between different languages that are hard to predict and control.

     

    As you correctly pointed out for cases where language has more priority than the message you can use separate publications where you can set a working language to the one that you want to publish.

     So, currently, we are not considering this idea but we appreciate the input and will continue to think of improving use cases such as this.

Children
No Data