You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docx output will result the following screenshot:
Which should not be the case. The "Sequencing 1" should have been removed in the output, yet it still appears. This is possibly caused by overcomplicated span tags (but also need to find out why the second line works okay even with such complicated nested tags).
For the initial workaround, the users are not encouraged to have individual text formatting (e.g., multiple different formatting with different text colors/font sizes) within a line/paragraph.
UPDATE: The workaround is to make the whole paragraph/line/block have a similar span root. This can be done in the TinyMCE editor by selecting the text block that is supposed to have a similar span root and setting the font size to be similar. More tests needed.
The text was updated successfully, but these errors were encountered:
Consider the following screenshot of a KVMU pair:
In which the first line is represented by the following snippet:
and the second line is represented by the following HTML snippet:
The docx output will result the following screenshot:
Which should not be the case. The "Sequencing 1" should have been removed in the output, yet it still appears. This is possibly caused by overcomplicated span tags (but also need to find out why the second line works okay even with such complicated nested tags).
For the initial workaround, the users are not encouraged to have individual text formatting (e.g., multiple different formatting with different text colors/font sizes) within a line/paragraph.
UPDATE: The workaround is to make the whole paragraph/line/block have a similar span root. This can be done in the TinyMCE editor by selecting the text block that is supposed to have a similar span root and setting the font size to be similar. More tests needed.
The text was updated successfully, but these errors were encountered: