Translations - Latest source language version of the map was not sent out

[sschnelbach]

I have a map file that wasn't sent out for translation. The AEM version is 1.7 (Rev I) and the last translated revision was Rev H. The map file wasn't sent out and is listed as "in sync", even though the source language file is Rev I and the current existing target language is Rev H.

Looking at the Translation pane, it looks like the system sees the source language version as 1.7 and thinks the target language should be going to 1.1 (first translated version would have been 1.0). The existing target language AEM version is 1.2 because I added some metadata to the map. Is this the reason the new map file wasn't sent out for translation?

Shouldn't the logic for sending out files for translation be if the current version (source language) is different from the last translated version (source language)? If the system is looking at the versions of the target language files, that would mean we could never make corrections/changes to the target language files (e.g. adding a language code to the part number in the map metadata, manually adding some hyphens to content within table cells since Adobe broke the hyphenation feature).

What am I missing?

AEM 6.5.21

AEM Guides 4.6

[DivrajSingh]

@sschnelbach : the version number (1.1, 1.2, ...) of source map are not created with same number in target language as a user cannot control that - neither the system sync status works based on that number.

The system works in a way that, when you at first translate a topic/map (say it was on version 1.3 in source) then the translated copy would create version 1.0 after translating the content. In the backend, AEM Guides keeps a mapping between source version on which translation was last requested and the version that was created after translating that to the selected language.

The comparison to show "Out of Sync" or "In Sync" is based on the last translated version of the source topic/map and the current version of the source topic/map

Is it possible that the topic/file of concern was selected and forcefully marked in-sync using the option available on translation UI ?

[sschnelbach]

No, I didn't not forcefully mark a changed .ditamap file as "in sync".

So you are saying that we can never edit a translated file to add metadata or corrections? That if we do that, the correlation between the last translated source language version and the translated target language version would be permanently wrong and any target file that was edited will never have its source file be sent out for translation again because of the version mis-match?

[1huntley]

Yikes. I hope that isn't true.

[DivrajSingh]

@sschnelbach I did not mean that in my last comment. The key rule that you should consider is:

The comparison to show translation status like "Out of Sync" or "In Sync", is based on the last translated version of the source topic/map (per language) and the current version of the source topic/map

To understand by scenario:
If the source topic is never translated to selected target language then status would be "Missing Copy"
If the source topic has same version that was previously translated then the status will be "In Sync"
If there are changes done to the source topic after it was previously translated, then the status would be "Out of Sync" (unless this topic version was selected and "Mark in sync" explicitly).

If you have made any edits in the translated copy (like you said updated metadata) - it will not affect the translation status when you check this from source map/topic.

Hence my main point was that the observation you initially stated seems to be due some action that cannot be depicted via usual translation workflow - you may have to provide more information around the scenario or some steps to reproduce to understand the content state you are seeing.