Prepublished Translations FAQ
Q: Is prepublishing useful in a non-GDN project?
Yes, it can be. Prepublished translations are included when downloading published translations. However, it might require some examination of what triggers the translation downloads to occur.
Q: Do connectors download prepublished translations?
When connectors download translations, prepublished translations are included. However, a connector might not trigger a download to happen unless all strings are in the Published step of the workflow. For some connectors, you can trigger a download manually. Alternatively, enabling a callback on prepublish might be appropriate in some situations.
Q: Are prepublished translations used by Smart Match?
If the prepublished translations are written to the translation memory (which they are usually except for certain external-step/MT scenarios), they’re considered published translations in the TM and can be used by SmartMatch.
Q: Will moving (not submitting) a translation past a workflow step with ‘prepublish on submit’ enabled cause the translation to be prepublished.
No. The translation has to be submitted from the step in order for the prepublish action to occur.
Q: How do I find prepublished strings?
Prepublished strings are identified by a small blue dot under the translation in the strings view. In addition, the strings view has a filter for prepublished strings.
Q: Does prepublishing work with ‘external step’ workflow steps?
Yes. Both ‘on-save’ and ‘on-submit’ options on the external-step workflow step will result in translations from an external step being prepublished.
Q: Does prepublishing affect the TM?
Yes. Prepublished translations are written to the TM as published. As a result prepublished translations can be used by Smart Match.
Q: If I submit from the CAT tool without explicitly saving, will prepublish-on-save take effect?
Q: If translations are submitted through a prepublish-on-save step, will they be prepublished?
No. The translation needs to be modified and saved in that step for this prepublish option to take effect.
Q: Does Job progress reflect prepublished translations?
No. Job progress reflects the actual workflow step that a translation is in, regardless of whether it’s been prepublished.
Q: Does downloading translations from a job download prepublished translations?
Currently, downloading translations from a Job uses the ‘pending/current translations’ retrieval type, and so downloads all saved translations regardless including ones that have not been prepublished. As a result, it will usually include prepublished translations, but won’t do so in the case that translations have been updated after prepublishing. This behavior seems unexpected and might change. As a workaround, you can download from the Files page and choose the ‘published’ option to download published and prepublished translations.
Q: Can I undo a prepublish action?
Not directly, but if you know what the active translation was before prepublishing, you could prepublish that to make it active. However, you might need to also remove it from the TM if it was the source string.
Q: Does prepublishing trigger Smart Match to run in the same way that moving a translation to the Published step does?
Yes. When a string is prepublished, Smart Match is triggered to check if any strings will Smart Match against the newly prepublished string.
Q: If Smart Match moves a translation to a prepublish-on-save step, will the string be pre-published?
No. The translation needs to be modified and saved in that step for this prepublish option to take effect. However, the behavior can be achieved by using the prepublish option within the Smart Match settings.
Q: Can I prepublish fuzzy matches?
It’s not possible to automatically save a fuzzy match--it has to be done by a person. Once it’s saved it can be prepublished like any other translation.
Q: What happens if a prepublished translation is deactivated and reactivated? For example, when a file it’s from is deleted and re-uploaded.
The prepublished translations are not retained. Prepublished strings behave the same as normal ‘in progress’ strings rather than Published strings in this case: in-progress translations are lost but can be recovered on reactivation if the ‘restore translation’ Smart Match option is used. If they are recovered in this way, the fact that they were previously prepublished is not retained, and they may need to be prepublished again.
Q: What happens if a job containing prepublished translation is cancelled?
As above, the prepublished translations are not retained. Prepublished strings behave the same as normal ‘in progress’ strings rather than Published strings in this case: in-progress translations are lost but can be recovered on reactivation if the ‘restore translation’ Smart Match option is used. If they are recovered in this way, the fact that they were previously prepublished is not retained, and they may need to be prepublished again.
Q: How does GDN Static Cache work with prepublishing?
The Static Cache system looks at the workflow step of a translation in determining whether a page is fully translated and ready to cache; so it won’t automatically refresh the cached version of a page if the page contains prepublished strings. However, if the cache is refreshed manually, then the prepublished strings will be included in the newly cached page.
Q: Are jobs callbacks invoked on prepublish?
No. The job completion callback is not sent until all strings have reached the Published workflow step.
Q: Does the ‘recently published files’ API endpoint include files that were prepublished?
No. Only files that had all authorised strings moved to the Published step in a locale are listed by this endpoint.