Open GoogleCodeExporter opened 9 years ago
The results I am getting using the latest version of HarfBuzz are different
from the attached screenshot. Would you please tell us which version of Windows
you are using?
I am attaching the HarfBuzz rendering of the same three sequences from Noto. Do
they look right?
Original comment by roozbeh@google.com
on 28 Aug 2014 at 5:34
Attachments:
Thank you for your feedback!
I am using Windows 8.1. I am not sure what HarfBuzz is.
If you type a U+1081, U+102F/U+1030, then U_1088/U108A (tone marks), do you now
have overlapping of the last two elements?
If there is no overlapping then again, they are "correct" in that they are
readable. However, they are not "pretty" in that U+102F or U+1030 should really
be under U+1081, not off to the side. And the U+1083 should have the "tail"
because that is the way it is specified in the Unicode standard (which is
rendered in Padauk).
Please see: http://www.unicode.org/charts/PDF/U1000.pdf
Thank you!
Original comment by ray...@gmail.com
on 30 Aug 2014 at 2:16
[deleted comment]
I wanna to use Noto Myanmar Font with Windows 7 . Font ver is 1.04.
I am not sure it needs Keyboard Installer or not.
If need, where and how can I get?
I can't type
ကၠ တၱ မၼ
ွ ွ
Out Ka Myint aslo overlapped.
Original comment by leo.born...@gmail.com
on 22 Oct 2014 at 6:32
Attachments:
Original comment by roozbeh@google.com
on 16 Jan 2015 at 6:07
Original comment by roozbeh@google.com
on 2 Apr 2015 at 6:20
I believe Windows 7 does NOT support Myanmar. Nothing we are going to do about
that.
Note that the font works fine in Firefox and Chrome, even on Windows 7.
Original comment by behdad@google.com
on 2 Apr 2015 at 7:22
Behdad, you are answering comment #4 (which is irrelevant to the reported
issue). What about the original report and comment #2?
Original comment by roozbeh@google.com
on 3 Apr 2015 at 3:40
Original comment by roozbeh@google.com
on 3 Apr 2015 at 3:41
Ok I see. Something for our design reviewers then. Sorry about the noise.
Original comment by behdad@google.com
on 3 Apr 2015 at 4:53
Original issue reported on code.google.com by
ray...@gmail.com
on 9 Aug 2014 at 3:09Attachments: