Closed GoogleCodeExporter closed 5 years ago
Original comment by xian...@google.com
on 1 Apr 2015 at 6:14
cc @xiangyexiao
please label this bug as Script-Javanese, thanks!
See pertinent response under https://github.com/googlei18n/noto-fonts/issues/149
It might be useful to say a bit about how and why this style was chosen. Is it one that Javanese who have learned to read and write their script are comfortable reading? Is it in common use (relative to other Javanese styles), or is it a historic outlier?
Design was closed a while ago for the current release.
I agree with Norbert some description of the choices made in the design would be helpful.
@bennylin : this is unrelated to the problem listed here. However, I'd like to hear your opinion/feedback on two proposals for the replacement of the current Javanese which is included in the PDF below (the original is grey, the suggested change is in black). Please look at the pages # 2 and # 3 in the PDF and tell use what version do you prefer and why?
@bennylin : BTW, we are leaning toward page # 3 (low contrast design option) because it is matching better Noto Sans and Roboto font design. If you are opposed to it, what would be the major critique or argument against page # 3 (low contrast design option) becoming the new design?
hi @marekjez86, I really like the first one (page 2) because there's difference in boldness between the upward stroke and downward strokes, just like in handwriting. also, the "adeg-adeg" is better.
The "da", however, could be modified more to resemble the shape that we're most familiar with.
I'm eager to see the full set of the 20 basic "aksara" and their "pasangan"s.
My critique for page 3 are:
Other than that it's a wonderful font.
This is a comparison glyph that I made that's useful to see how well those rare forms look like.
Original issue reported on code.google.com by
xian...@google.com
on 28 Mar 2015 at 1:13