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
New check: Check that U+FBB2–FBC2 are not marks #4295
Labels
New check proposal
We expect new check proposals to include a detailed rationale description and a suggested check-id
Milestone
Comments
khaledhosny
added
the
New check proposal
We expect new check proposals to include a detailed rationale description and a suggested check-id
label
Oct 5, 2023
felipesanches
added a commit
to felipesanches/fontbakery
that referenced
this issue
Oct 20, 2023
Unicode has a few spacing symbols (U+FBB2–FBC1) representing Arabic dots and other marks, but they are purposefully not classified as marks. Many fonts mistakenly classify them as marks, making them unsuitable for their original purpose as stand-alone symbols to used in pedagogical contexts discussing Arabic consonantal marks. Added to the Universal Profile com.google.fonts/check/arabic_spacing_symbols (experimental) (issue fonttools#4295)
felipesanches
added a commit
to felipesanches/fontbakery
that referenced
this issue
Oct 20, 2023
Unicode has a few spacing symbols (U+FBB2–FBC1) representing Arabic dots and other marks, but they are purposefully not classified as marks. Many fonts mistakenly classify them as marks, making them unsuitable for their original purpose as stand-alone symbols to used in pedagogical contexts discussing Arabic consonantal marks. Added to the Universal Profile com.google.fonts/check/arabic_spacing_symbols (experimental) (issue fonttools#4295)
felipesanches
added a commit
that referenced
this issue
Oct 20, 2023
Unicode has a few spacing symbols (U+FBB2–FBC1) representing Arabic dots and other marks, but they are purposefully not classified as marks. Many fonts mistakenly classify them as marks, making them unsuitable for their original purpose as stand-alone symbols to used in pedagogical contexts discussing Arabic consonantal marks. Added to the Universal Profile com.google.fonts/check/arabic_spacing_symbols (experimental) (issue #4295)
felipesanches
added a commit
to felipesanches/fontbakery
that referenced
this issue
Nov 28, 2023
Originaly implemented in v0.10.2 No longer marked as experimental. On the Universal Profile com.google.fonts/check/arabic_spacing_symbols "Check that Arabic spacing symbols U+FBB2–FBC1 aren't classified as marks." (issue fonttools#4295)
felipesanches
added a commit
to felipesanches/fontbakery
that referenced
this issue
Nov 28, 2023
Originally implemented in v0.10.2 No longer marked as experimental. On the Universal Profile com.google.fonts/check/arabic_spacing_symbols "Check that Arabic spacing symbols U+FBB2–FBC1 aren't classified as marks." (issue fonttools#4295)
felipesanches
added a commit
that referenced
this issue
Nov 28, 2023
Originally implemented in v0.10.2 No longer marked as experimental. On the Universal Profile com.google.fonts/check/arabic_spacing_symbols "Check that Arabic spacing symbols U+FBB2–FBC1 aren't classified as marks." (issue #4295)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
New check proposal
We expect new check proposals to include a detailed rationale description and a suggested check-id
What needs to be checked?
Check that the Arabic dot symbols are not marks in GDEF.
Detailed description of the problem
Unicode has a few spacing symbols representing Arabic dots and other marks, but they are purposefully not classified as marks. Many fonts mistakenly classify them as marks.
Resources and steps needed to reproduce the problem
The current version of Noto Sans Arabic ans Noto Naskh Arabic has this issue.
Suggested profile
Suggested result
Severity assessment
4 as making them marks make them unsuitable for there original purpose (stand-alone symbols to used in pedagogical contexts discussing Arabic consonantal marks).
The text was updated successfully, but these errors were encountered: