Closed xfq closed 7 months ago
Name | Link |
---|---|
Latest commit | 2802f58e8f8f07979877352bf4753f11b250f2ab |
Latest deploy log | https://app.netlify.com/sites/bp-i18n-specdev/deploys/64785c67e3c7f00008474dd6 |
Deploy Preview | https://deploy-preview-104--bp-i18n-specdev.netlify.app/ |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
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.
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.
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