As a follow-up to my question on Translation Manager check out and localize behavior I wanted to confirm additional details for Translation Jobs (and correct any assumptions I might have suggested).
I couldn't find mention in the docs, but to be sure, can we create and send Translation Jobs that have checked out items?
What happens to the items in Target Publications when a job starts and completes?
Lars explained when starting a Translation Manager Job will:
- Attempt to checkout (target items)
- Localize the target item if needed
- Not prevent the job from being sent (though we'll have issues on retrieval if items are still checked out)
Is there any unlocalization involved?
I think I've misread an implementation suggestion where editors (or the Event System) could synchronize a Target item to its Source (or at least closest localized parent) by unlocalizing the item, but I'm not sure this is the default behavior.
Here's what I've read about unlocalizing as an "implementation suggestion" (approach, technique, or option). This could help keep non-translatable parts of items (e.g. permissions or Component Presentations) synchronized with their parents:
- SDL Live Content mentions unlocalizing child Folders or Structure Groups as a way to keep permission settings the same as their parents while still translating their names (or metadata)
- Nickoli Roussakov mentions unlocalizing pages as a way to match their Component Presentations
So unlocalizing can help, but to keep history in Target items, we'd avoid doing so.