Skip to content

fix(pdf): For monospaced text, Add Noto Sans Mono before NOTO_SYMBOLS #1261

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 14, 2025

Conversation

dkg
Copy link
Contributor

@dkg dkg commented Jun 26, 2025

This is an attempt to address #1245

@dkg
Copy link
Contributor Author

dkg commented Jun 26, 2025

The idea here is to keep in the Roboto and Noto families, but to increase the range of covered glyphs in a fixed-width font.

I'm not sure how well this will work, because i don't think i have the same font environment that the RFC editor's toolchain uses when it works. but hopefully this makes it easier to test, at least.

@kesara
Copy link
Member

kesara commented Jun 27, 2025

This is a better solution and this change stops leaking non-RFC fonts.
But monospace arrows are not aligning well. See pdf generated with this change.

Screenshot 2025-06-27 at 16 46 45 Screenshot 2025-06-27 at 16 46 54

@kesara
Copy link
Member

kesara commented Jun 27, 2025

@dkg If you want to use the same fonts as RFC editor, you can get them from xml2rfc-fonts or you xml2rfc docker instace with ./run from project root dir. Just make sure xml2rfc docker images are up-to-date.

@@ -133,10 +133,12 @@ def get_mono_fonts(self):
fonts = set()
scripts = self.root.get('scripts').split(',')
roboto_mono = "Roboto Mono"
noto_sans_mono = "Noto Sans Mono"
dejavu_sans_mono = "DejaVu Sans Mono"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PDFs have been restricted to Noto and Roboto Mono fonts.
I guess this needs attention of rapt/rswg.

@kesara kesara added the rpat Issues needing attention from RFC Production Advisory Team label Jun 27, 2025
@dkg dkg changed the title For monospaced text, Add Noto Sans Mono before NOTO_SYMBOLS For monospaced text, Add Noto Sans Mono and DejaVu Sans Mono before NOTO_SYMBOLS Jun 27, 2025
@dkg
Copy link
Contributor Author

dkg commented Jun 27, 2025

OK, how about just merging the first patch of this series (since it's just Roboto and Noto), and then we can pursue one of the other resolution strategies discussed in #1245?

@dkg dkg force-pushed the monospace-rendering branch from aa8449e to 00dae38 Compare July 11, 2025 19:09
@dkg dkg changed the title For monospaced text, Add Noto Sans Mono and DejaVu Sans Mono before NOTO_SYMBOLS For monospaced text, Add Noto Sans Mono before NOTO_SYMBOLS Jul 11, 2025
@dkg
Copy link
Contributor Author

dkg commented Jul 11, 2025

I've dropped the commit from this series that included DejaVu Sans Mono, to focus specifically on Noto Sans Mono, as it should be sufficient for a BOX-DRAWINGS-only resolution to the specific issues.

Maybe this is safe to merge as-is now, regardless of the outcome of the rpat discussion? I can always open up a separate MR for further discussion related to DejaVu Sans Mono.

@kesara kesara changed the title For monospaced text, Add Noto Sans Mono before NOTO_SYMBOLS fix: For monospaced text, Add Noto Sans Mono before NOTO_SYMBOLS Jul 14, 2025
@kesara kesara changed the title fix: For monospaced text, Add Noto Sans Mono before NOTO_SYMBOLS fix(pdf): For monospaced text, Add Noto Sans Mono before NOTO_SYMBOLS Jul 14, 2025
@kesara kesara merged commit cd93225 into ietf-tools:main Jul 14, 2025
35 of 36 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rpat Issues needing attention from RFC Production Advisory Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants