Issue with <br/> and capitals #603
Labels
Comments
|
This was fixed when we upgraded to Dotify 1.0.1 (daisy/pipeline-modules@fe3a41c) |
|
Not completely fixed yet because with pre-translation enabled the translation will still be wrong. |
bertfrees
added a commit
that referenced
this issue
May 28, 2024
Inline ::before and ::after pseudo-elements are now taken into account when pre-translating the containing element. 'content' properties that are not inside a ::before or ::after pseudo-element, or that are inside a ::before or ::after pseudo-element stacked onto a different kind of pseudo-element or other rule, are now not pre-translated anymore. Fixes issues #652 and #603.
bertfrees
added a commit
that referenced
this issue
May 28, 2024
Inline ::before and ::after pseudo-elements are now taken into account when pre-translating the containing element. 'content' properties that are not inside a ::before or ::after pseudo-element, or that are inside a ::before or ::after pseudo-element stacked onto a different kind of pseudo-element or other rule, are now not pre-translated anymore. Fixes issues #652 and #603.
bertfrees
added a commit
that referenced
this issue
Aug 15, 2024
Inline ::before and ::after pseudo-elements are now taken into account when pre-translating the containing element. 'content' properties that are not inside a ::before or ::after pseudo-element, or that are inside a ::before or ::after pseudo-element stacked onto a different kind of pseudo-element or other rule, are now not pre-translated anymore. Fixes issues #652 and #603.
bertfrees
added a commit
that referenced
this issue
Nov 1, 2024
Inline ::before and ::after pseudo-elements are now taken into account when pre-translating the containing element. 'content' properties that are not inside a ::before or ::after pseudo-element, or that are inside a ::before or ::after pseudo-element stacked onto a different kind of pseudo-element or other rule, are now not pre-translated anymore. Fixes issues #652 and #603.
bertfrees
added a commit
that referenced
this issue
Nov 21, 2024
Inline ::before and ::after pseudo-elements are now taken into account when pre-translating the containing element. 'content' properties that are not inside a ::before or ::after pseudo-element, or that are inside a ::before or ::after pseudo-element stacked onto a different kind of pseudo-element or other rule, are now not pre-translated anymore. Fixes issues #652 and #603.
bertfrees
added a commit
to daisy/pipeline-modules
that referenced
this issue
Jan 4, 2025
Inline ::before and ::after pseudo-elements are now taken into account when pre-translating the containing element. 'content' properties that are not inside a ::before or ::after pseudo-element, or that are inside a ::before or ::after pseudo-element stacked onto a different kind of pseudo-element or other rule, are now not pre-translated anymore. Fixes issues daisy/pipeline#652 and daisy/pipeline#603.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
We try to process the following DTBook paragraph:
<p>A<br/>Aa</p>The expected output would be:
or,
{capital mark}A{line-break}{capital mark}AaActual Behavior
This is the actual erroneous output.
or,
{permanent capital mark}A{line-break}a{recovery sign}aSteps to Reproduce
<p>A<br/>Aa</p>Details
None.
Environment
Logs
Relevant fragment from the generated OBFL:
<marker class="resumed-title/if-not-set-next" value=""/>⠘⠁<br/>⠁⠠⠁</block>The generated OBFL already contains the mistake. This indicates that it is a Pipeline issue (and not an issue in Dotify).
The text was updated successfully, but these errors were encountered: