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

Myanmar: Glyphs should not look the same #18

Open
agguser opened this issue May 9, 2020 · 6 comments
Open

Myanmar: Glyphs should not look the same #18

agguser opened this issue May 9, 2020 · 6 comments

Comments

@agguser
Copy link

agguser commented May 9, 2020

Font

NotoSansMyanmar-Regular.ttf, …
NotoSerifMyanmar-Regular.ttf, …

Font Version

2.001

Issue

Some single/combined glyphs look the same, hard to be differentiated. Please make them distinct (like ဈ vs စျ (စ+ျ)).

A B
၀ (0)
ဦ (ဥ+ီ)
သြ (သ+ြ)
သ (သ+ြ+ေ+ာ+်)

NotoSansMyanmar-Regular:
NotoSansMyanmar-Regular-14

NotoSerifMyanmar-Regular:
NotoSerifMyanmar-Regular-14 png

compare with ZawDecode-Regular:
ZawDecode-Regular-14

@nizarsq
Copy link

nizarsq commented May 25, 2020

I can see the single and combined glyphs are rendered the same for all characters mentioned, for ဦ (U+1026), single/combined looks identical same as well in ZawDecode.
Screen Shot 2020-05-25 at 3 16 56 PM

@ohbendy
Copy link

ohbendy commented Sep 28, 2020

If I understand correctly, agguser would like these four sequences to differ in appearance:

  • Consonant Wa uni101D ≠ Burmese zero uni1040;
  • Independent vowel UU uni1026 ≠ independent vowel U uni1025 + vowel ii uni102E;
  • Independent vowel O uni1029 ≠ consonant θa uni101E + medial Ra uni103C;
  • Independent vowel Au uni102A ≠ consonant θa uni101E + medial Ra uni103C + vowel e uni1031 + vowel aa uni102C + asat uni103A.

The first of these is fairly common in digital typefaces, though not in handwriting. It is a good idea for Noto to differentiate the Wa from the zero, to avoid the possibility of spoofing.

I've just consulted with a Burmese expert, and we are puzzled by the latter three suggestions. While I understand the principle of making different character sequences look visually distinct, there's no tradition of making these three look different in either handwriting or in digital typefaces. If you have examples where these differ, I'd be very interested to see. I don't consider the Zawdecode solution elegant, it doesn't look like an intentional design decision to me — I think more users would complain about the wraparound having a gap than about distinguishing independent vowels from medial Ra sequences.

I'd also suggest that there's not really a possibility of confusion between the sequences, as the sequences with medial Ra would always have a dependent vowel sign. The independent vowels could never take an independent vowel sign.

@agguser
Copy link
Author

agguser commented Sep 30, 2020

With different appearance, you can know real characters used by just looking, same benefit as differentiating I/l/1 or O/0. Even when there is no ambiguity, the differentiation let you know typo (or wrong conversion from Zawgyi).

@ohbendy
Copy link

ohbendy commented Sep 30, 2020

Yes, I don't disagree. It's just that the script doesn't have a tradition of differentiating the shapes. We can't just invent new forms to make them differ.

@agguser
Copy link
Author

agguser commented Sep 30, 2020

Well, I don't think that we "must" follow tradition, especially when the change is for the better (clarity in this case).

@ohbendy
Copy link

ohbendy commented Sep 30, 2020

I'm all for experimentation and new ideas, but if we make glyphs that users are unfamiliar with, that's going to cause readability problems and bug reports. In the case of ZawDecode, I'm not sure how many users would be happy with the disconnected wraparound and whether it's evident which version is O and which version is θra. If you have examples of a better way to disambiguate them, I'd be very interested to see.

The design brief for Noto is not to be experimental, but to 'maintain authenticity' and be 'conservative'.

@simoncozens simoncozens transferred this issue from notofonts/noto-fonts Jun 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants