Mention combining characters in the template #104
Conversation
✅ Deploy Preview for bp-i18n-specdev ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
| @@ -2187,6 +2187,15 @@ <h5>Character naming template</h5> | |||
| <span class="uname">U+XXXX Unicode_character_name</span></span> | |||
| </pre> | |||
|
|
|||
| <p>For combining characters (such as <span class="codepoint" translate="no"><bdi lang="en">◌̀</bdi><span class="uname">U+0300 COMBINING ACCENT GRAVE</span></span>), if the specification uses a font which supports display with a <span class="codepoint" translate="no"><bdi lang="en">◌</bdi><span class="uname">U+25CC DOTTED CIRCLE</span></span>, then a dotted circle should be used before the combining character:</p> | |||
There was a problem hiding this comment.
This is ambiguous? Does it mean "... uses a font which supports the dotted circle character with combining marks..."? How does a specification author know this? I think this is getting too complex and would rather not having folks flinging 25CCs about.
I think we should discuss automation of using an image? Or whether we can live with the combining mark showing without dotted circles?
|
I think we should abandon this PR, since we now have guidance on using images. |
|
The current text says "For invisible characters (such as control characters) or for whitespace, use an image instead of the character", but does not mention combining characters. I think we should add that. By the way, I think whitespace are also "invisible", and some of them are also control characters. |
|
The combining characters often work ok without the need for images. If the font behaves well, it will typically add a dotted circle when displaying isolated combining marks. So an image is only needed sometimes. |
|
Any update? Should we keep this or abandon? |
|
I still think it's useful to mention combining characters in the template. Since there are merge conflicts, I will close this PR and craft a new one. |
I found that the font didn't behave well on my system (without changing any font-related preferences), so it may appear for other users as well. Maybe we should use images? Screenshot: 
It's Chrome 120 on macOS 14.2. The rendered font seems to be Hiragino Sans. |
Fix #103.
Preview | Diff