Closed GoogleCodeExporter closed 9 years ago
I believe this should be fixed at the level of website's CSS. Noto Nastaliq
demands a more generous line-height than Jameel Noori Nastaleeq.
Original comment by saadat.m...@gmail.com
on 14 Nov 2014 at 7:02
Sorry. we dont beleive it has to be fixed at website's CSS level. Almost every
urdu blogger or urdu website owner uses 3 desktop unicode nastaliq fonts in its
body font-family i.e. Alvi, Jameel & Taj. and these three have same line-height
and size.
The problem occurs if we include Noto after these 3 and if a user's system
doesnt include the above said three unicode nastaliq fonts. So the content will
b shown to him/her in a much bigger font-size with lesser line-height.
Original comment by taem...@gmail.com
on 14 Nov 2014 at 7:49
@taemeer, are you suggesting that we reduced the glyph size in Noto Nastaliq to
be compatible with your CSS/existing Nastaliq font?
What harm would it be done if you increase the line-height (to, say, 1.9em or 2
em) ? Even if one of three Nastaliq fonts requiring less line-height is used,
giving more interline-spacing wouldn't hurt a lot. I'd rather claim that it'd
increase the readability even for those fonts.
Original comment by jshin@chromium.org
on 14 Nov 2014 at 6:20
Thanks for the report. We will check other Nastaliq fonts and adjust the font
height appropriately.
Do you think the glyph sizes of the font are appropriate and only line spacing
needs changing?
Original comment by behdad@google.com
on 20 Nov 2014 at 12:14
Dear Behdad
I am almost finish Nastaliq for Google in the name of "ALI Natstaliq" it is
character based true Dahelvi School Nastaliq Open Type Font.
Please see attached screen shot
Syed Manzar Hasan
Mumbai
Original comment by syedman...@gmail.com
on 21 Nov 2014 at 11:14
Attachments:
What you are seeing is a CSS issue. Read:
https://developer.mozilla.org/en-US/docs/Web/CSS/line-height
You can fix this by writing:
font-size: 18px 1.6;
Or try removing the "em" from line-height.
Original comment by beh...@chromium.org
on 22 Jan 2015 at 8:51
Original comment by behdad@google.com
on 22 Jan 2015 at 8:51
Original issue reported on code.google.com by
taem...@gmail.com
on 12 Nov 2014 at 10:04Attachments: