Segmentation problem with variables
Posted: Mon Sep 05, 2011 8:52 am
We are having problems in getting content with variables translated. When a variable is located at the end of a heading in the source file the segment generated by lingo stops just before the variable.
source: <h2>Calculating a <MadCap:variable name="GUI_Terms.Thing" /></h2>
target:<h2><MadCap:segment>Calculating a </MadCap:segment><MadCap:variable name="GUI_Terms.Thing" /></h2>
This means that our translators can't see the variable or move it to accomodate local syntax.
We are using lingo V3, this may have been fixed in the later versions. I see that in V4 this kind of behavior for bold, underlined etc. text was fixed, but was wondering if the same applies to variables.
source: <h2>Calculating a <MadCap:variable name="GUI_Terms.Thing" /></h2>
target:<h2><MadCap:segment>Calculating a </MadCap:segment><MadCap:variable name="GUI_Terms.Thing" /></h2>
This means that our translators can't see the variable or move it to accomodate local syntax.
We are using lingo V3, this may have been fixed in the later versions. I see that in V4 this kind of behavior for bold, underlined etc. text was fixed, but was wondering if the same applies to variables.