Under Community Review

Have read-only/hidden status and "translator" comments of target language in base project propagate to target languages in cascaded project

Hello,

We use cascaded projects to first copyedit our English GUI, and then translate into 8 languages.

In the base project the source language is en_GB ("Developer English") and the target language is en_US ("Copyedited English"). In the cascaded project, there are 8 target languages.

Before translation, I send an en_US bundle to our technical writer so she can copyedit the English strings. She may mark obsolete strings or strings that don't need to be translated "read-only" or "hidden." She may make a comment to explain the context of a word with multiple connotations.

Currently the read-only/hidden status and the comments do not get cascaded to the target languages in the cascaded project. It only works if we mark the source string (en_GB) read-only/hidden or add a comment there. 

It'd be great if we could cascade this from the copyedited English (en_US, target language in base project) to the foreign languages.

Thanks!

Di

Di Liu

  • Yes, sorry, to clarify our writer writes in the comment section if a string needs to be marked "read-only."

    Yes, I see that I could export 2 bundles. One of the source string list so the writer can mark things "read-only" and add comments. And one of the target string list so she can "translate" (edit) the strings.

    However, I was hoping that I could just send out 1 bundle and have her do all of these things in 1 place. It would streamline our process.

    Thanks,

    Di

  • I still do not understand how your writer is adding "read-only" and "hidden" as this is not possible with a translation list. And if the writer is just adding comments (instead of changing the text itself) the feature your have requested is already available. Just export the source list only in which the writer can directly change "read-only" and "hidden"  and add comments. Importing the source list bundle will import the changes the writer has done and updating the translation lists in t he main project will inherit the data to all languages.

  • Hi Achim,

    Currently I'm exporting the translation list to the writer, and transferring her "read-only/hidden" and comments to the source list myself.

    I guess I could export the source list to the writer too, and have her do those things. But I'd prefer to send just 1 bundle and have her do everything in one place.

    Thanks!

    Di

  • I’m struggling a lit bit with your workflow. What are you exporting into the bundle sent to the author? The source or the translation list?

    a) When exporting the source list the author can easily mark entries as “read-only” and “hidden” and add additional context as comments, but you can’t edit and change the developers text string.

    b) When exporting the translation list the author can’t mark entries as read-only and hidden and comments are stored as translator comment so they are not transferred to all other languages. But in this mode you can change the developers text entries.

    If the author just want to perform tasks from a) then please export the source list into the bundle. Doing both a) and b) is possible when exporting both source list and translation list.