docs: the name is a translated string, in the reader's script - #25
Merged
Conversation
The typography note said the name is "identical in both languages" and therefore safe in the editorial face. It is not identical: Дмитрий Машков and Dmitrii Mashkov are different scripts, which is exactly why Instrument Serif, having no Cyrillic, would drop the Russian half onto a fallback family. #24's proposal spotted that contradiction and resolved it by rendering Latin on both sides. That resolution is wrong, and the reason is not typographic. Every other string on the home page is properly bilingual; if the name is the single exception it becomes the one element that looks machine-made, on a site whose whole argument is that it was not. Stated here rather than fixed in that pull request because it is a standing rule the implementer reads on every run, not a one-off correction. The answer to "our editorial font has no Cyrillic" cannot be "then write the name in the wrong script". Claude-Session: https://claude.ai/code/session_01MPpAwcFk2L1B94VT8LiKVx
|
Claude finished @mashkovd's task in 14s —— View job Review
This is a documentation-only change (a new bullet point in Approving with no inline findings. |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
This was referenced Sep 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why
The typography constraint said the name is "identical in both languages" and therefore safe in the editorial face. It is not identical —
Дмитрий МашковandDmitrii Mashkovare different scripts, which is precisely whyInstrument Serif, shipping no Cyrillic, would drop the Russian half onto a fallback family.#24's proposal found that contradiction and resolved it by rendering Latin on both sides. The contradiction was real; the resolution should go the other way, and the reason is not typographic.
Every other string on the home page is properly bilingual. If the name is the one exception, it becomes the single element that looks machine-made — on a site whose entire argument is that it was not. A Russian reader shown a transliteration of a Russian name reads a page that was translated rather than written.
The rule
Dmitrii MashkovДмитрий Машков.l.en/.l.rupair, like any other copyInstrument Serif<title>This goes in
AGENTS.mdrather than into #24 because the implementer reads this file on every run, and a comment on one pull request reaches neither it nor the next cycle. Three findings this evening have been lost that way.It does leave
Instrument Serifwith little to do on the home page. That is a real design question for whoever needs the face; the answer to "our editorial font has no Cyrillic" cannot be "then write the name in the wrong script".🤖 Generated with Claude Code
https://claude.ai/code/session_01MPpAwcFk2L1B94VT8LiKVx