Don’t set font on fragments without font when processing fallback #263 #743
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue comes from the difference in how
Prawn::Text::Formatted::Box
andPrawn::Text
handle styles. The fragments that are passed fromPrawn::Text
toPrawn::Text::Formatted::Box
don't specify a font, relying on the font set on the document. AfterPrawn::Text::Formatted::Box#analyze_glyphs_for_fallback_support
, the fragments are rewritten with font families specified but no styles. This patch preserves the original (:font-less) state for resulting fragments that don't require fallback.Example that reproduces the issue (starting from example in manual):
In this version, styles have no effect. Commenting
fallback_fonts ["Times-Roman"]
shows the styles working.