Skip to content
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

Arabic thousand- (U+066C), decimal- (U+066B), and date separators (0+060D) don't render correctly #763

Open
skycommand opened this issue Aug 29, 2024 · 0 comments

Comments

@skycommand
Copy link

skycommand commented Aug 29, 2024

Cascadia family version

2404.23

Cascadia family variant(s)

Cascadia Code (the version with ligatures), Cascadia Mono (the version without ligatures)

Font file format(s)

.ttf (variable)

Platform

Windows

Other Software

No response

What happened?

On a web page with lang="fa" attribute, Cascadia Code and Cascadia Mono don't render the following characters correctly:

  • U+060D: Arabic Date Separator ( ؍ ): Should be longer, almost like a division sign
  • U+066B: Arabic Decimal Separator ( ٫ ): Should resemble a half division sign centered vertically on the baseline
  • U+066C: Arabic Thousands Separator ( ٬ ): Should resemble a single quotation mark aligned with the top of the digits

This issue, however, is not specific to web pages. The same happen in Microsoft Word and Microsoft Excel when the text language is set to Persian.

The following image compares the Cascadia rendering with the venerable Arial. The green Arial sample is correct. The red Cascadia Code sample is not.

Arabic separators

Here is my test code for reference.

Test sample for Cascadia Code.zip

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

No branches or pull requests

1 participant