Skip to content

Update DP Sans Mono to version 17#1582

Open
cpeel wants to merge 1 commit into
DistributedProofreaders:masterfrom
cpeel:update-dpsm
Open

Update DP Sans Mono to version 17#1582
cpeel wants to merge 1 commit into
DistributedProofreaders:masterfrom
cpeel:update-dpsm

Conversation

@cpeel
Copy link
Copy Markdown
Member

@cpeel cpeel commented May 26, 2026

This updates DP Sans Mono to version 17.

Sandbox: https://www.pgdp.org/~cpeel/c.branch/update-dpsm/tools/charsuites.php

@cpeel cpeel requested review from 70ray, chrismiceli and srjfoo May 26, 2026 00:10
@cpeel cpeel self-assigned this May 26, 2026
@chrismiceli
Copy link
Copy Markdown
Collaborator

do we cache bust fonts? If not, I wonder if versioning would help everyone have a consistent experience throughout the cache window.

@cpeel
Copy link
Copy Markdown
Member Author

cpeel commented May 26, 2026

do we cache bust fonts? If not, I wonder if versioning would help everyone have a consistent experience throughout the cache window.

Good question and we don't. The fonts are brought in via CSS which don't have/use our cache-control system for the font URLs. Beyond renaming the files -- which I'd prefer not to do -- I'm unsure of an easy way to manage this. Any ideas?

@chrismiceli
Copy link
Copy Markdown
Collaborator

do we cache bust fonts? If not, I wonder if versioning would help everyone have a consistent experience throughout the cache window.

Good question and we don't. The fonts are brought in via CSS which don't have/use our cache-control system for the font URLs. Beyond renaming the files -- which I'd prefer not to do -- I'm unsure of an easy way to manage this. Any ideas?

Not really. Though I wouldn't worry about it until someone says something based on the low impact.

@cpeel
Copy link
Copy Markdown
Member Author

cpeel commented May 26, 2026

do we cache bust fonts? If not, I wonder if versioning would help everyone have a consistent experience throughout the cache window.

Good question and we don't. The fonts are brought in via CSS which don't have/use our cache-control system for the font URLs. Beyond renaming the files -- which I'd prefer not to do -- I'm unsure of an easy way to manage this. Any ideas?

Not really. Though I wouldn't worry about it until someone says something based on the low impact.

To minimize the impact, I've temporarily reduced the cache duration for the woff/woff2 files from 1 month to 1 day to reduce the caching until this is rolled out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants