Does FmUuid remains same after we translate the DITA Topics/Map? | Community
Skip to main content
R
Rohan0794
Level 2
September 9, 2022
Question

Does FmUuid remains same after we translate the DITA Topics/Map?

  • September 9, 2022
  • 1 reply
  • 1095 views

Hello Community,

 

I created a translation project to translate the assets (DITA Topics/Maps) from source language folder (say en_us) to a new target Ianguage (say es).  I used the OOTB Microsoft's Machine Translation (free license) for doing the same. After assets are translated, when i go to CRXde and open the jcr:content of any translated DITA topic , I see that fmUuid value is exactly same as the fmUuid value of source language DITA topic. Is this behaviour expected?

 

The same behavior (consistent fmUuids) is expected when we try to integrate it with any 3rd party integrations like Lionbridge? Or it depends on the vendor?

 

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

A
Adobe Employee
AswiniLakshminarayananAdobe Employee
Adobe Employee
September 14, 2022

@rohan0794 

It depends on how the third-party applications process it. In Guides, the fmUuid of the translated topic is same as the source language topic but it has a translated locale code appended at the end. 


Eg: GUID-ea7a35ad-9c55-4269-934e-873a07d8235d (source)
GUID-ea7a35ad-9c55-4269-934e-873a07d8235d-es (translated)

R
Rohan0794Author
Level 2
September 14, 2022

@aswinilakshminarayanan Thanks for your reply.
You mentioned that translated locale is appended to GUID, but I don't see that happening in OOTB Microsoft Translation. Can you provide more details of your configuration and any steps to reproduce the same?

 

A
Adobe Employee
AswiniLakshminarayananAdobe Employee
Adobe Employee
September 19, 2022

Which version of Guides are you using? UUID filename patterns can be configured in the fmdita configuration com.adobe.fmdita.config.ConfigManager under UUID Filename Patterns property.  

Terms & ConditionsAccessibility statement

Loading footer...