Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

export to XLIFF: note element attributes value and postreq element

Explorer ,
Dec 04, 2024 Dec 04, 2024

FM 17, Windows 11.

 

My documents are going to publish in two languages, so the note and postreq elements must be translated, too. 

 

I currently use the [othertype], in the hope to expose the text for translation.

 

Somehow, the <ExposeAttributeValues>true</ExposeAttributeValues> in the .XTS doesn't work as expected.

 

Original XML:

 

 

 

<entry namest="1" nameend="4">
<note type="other" othertype="forbidden">
<p>We recommend solid-state drive (SSD).</p>
</note>

 

 

 

The XLIFF file produced with expose attributes enabled:

 

 

 

 

 

<trans-unit resname="entry" restype="cell" id="ID0E5D"><source xml:space="preserve" xml:lang="en">HDD/SDD</source><seg-source xml:space="preserve"><mrk mtype="seg" mid="24">HDD/SDD</mrk></seg-source></trans-unit></group><group resname="row" restype="row" id="ID0ECE"><group resname="entry" restype="cell" id="ID0EFE"><group resname="note" id="ID0EIE"><trans-unit resname="p" id="ID0ELE"><source xml:space="preserve" xml:lang="en">We recommend solid-state drive (SSD).</source><seg-source xml:space="preserve"><mrk mtype="seg" mid="25">We recommend solid-state drive (SSD).</mrk></seg-source></trans-unit></group></group></group></group></group></group></group

 

 

 

 

'forbidden' doesn't get exposed in the XLIFF text.

 

I also need to expose this prefix:

Prefix rules
In all contexts.
Prefix: After Completing This Task:
Text range.
Use character format: step.callouts

 

Am I missing a step?

 

Regards,

Andy

TOPICS
Structured
276
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Dec 05, 2024 Dec 05, 2024

If you don't get any response (not a lot of XLIFF users in here), I suggest you ping the FM folks - see https://helpx.adobe.com/contact/enterprise-support.other.html#framemaker for your Adobe Support options. I'd recommend using the tcssup@adobe.com e-mail address as it reaches a team dedicated to Technical Communication Suite products including FrameMaker.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 05, 2024 Dec 05, 2024
LATEST

Good morning, Jeff.

 

Thank you for the advice. Looks like XLIFF isn't quite a popular feature just yet. 

 

I will reach out to the support as you suggested. Otherwise, I would have to ditch those elements and opt for simple paragraph for the time being.

 

Regards,

Andy

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines