- changed status to resolved
Markdown filter: when text that has *emphasis* at the beginning of a paragraph, a separate DocumentPart is generated for the first "*"
Issue #701
resolved
Currently, when a paragraph starts with an inline markdown, for example:
*RED WINE* is a nice beverage.
the markdown filter separates the first marker character from the rest, and generates two event, a DocumentPart that contains only the marker character, and a TextUnit that contains the rest.
Because of this, the extracted text in XLIF looks like this:
<source xml:lang="en">RED WINE<x id="1"/> is a nice beverage.</source>
Suppose a translation requires a change of the word order, and the translated word corresponding to RED WINE moves to a different position. For example:
<target xml:lang="zz">Egareveb ecin a si ENIW DER<x id="1"/>.</target>
The merged markdown file will look like this:
*Egareveb ecin a si ENIW DER*.
causing the entire paragraph to be emphasized.
Markdown filter should not separate the first marker character from the rest and make a TextUnit that contains the entire paragraph. The extraction should result in something like:
<source xml:lang="en"><x id="1"/>RED WINE<x id="2"/> is a nice beverage.</source>
Comments (1)
-
- Log in to comment
Fixing issue 701. Adding UI to the new htmlSubfilter config param.
→ <<cset aac253cff49c>>