<div dir="ltr"><div>> <span class="gmail-im">IranNastaliq had broken Kashida justification in IE6 but not in IE7,</span> [..]</div><div><br></div><div>This is probably inaccurate as from IE6 to Microsoft Edge / Microsoft Word, Kashida justification results in broken shaping like this,</div><div><br></div><div><div><img src="cid:ii_k2x33jhz0" alt="image.png" style="margin-right: 0px;" width="209" height="43"><br></div></div><div>Isn't it great…<br></div><div><br></div><div>> Interesting. Can you provide test results for this? Let's understand what changed.</div><div><br></div><div>However there is still another some difference between IE versions,</div><div><br></div><div>Open this link <a href="https://ebraminio.github.io/extra/kashida.html">https://ebraminio.github.io/extra/kashida.html</a> in this tool <a href="https://netrenderer.com/index.php">https://netrenderer.com/index.php</a><br></div><div><br></div><div>IE 9: (broken)<br></div><div><div><img src="cid:ii_k2x3azuz2" alt="image.png" width="475" height="72"><br></div></div><div><br></div><div>IE 11: (same page, Kashida justification is skipped for some reason)<br></div><div><div><img src="cid:ii_k2x3bo3b3" alt="image.png" width="475" height="74"></div><div>Not sure how this can be explained, maybe someone has attempted to prevent some fonts to get Kashida justification and maybe the detection was font based, the reason it is still failing for IranNastaliq but not for Amiri, but in any case it is imperfect.<br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Nov 13, 2019 at 7:48 AM Behdad Esfahbod <<a href="mailto:behdad@behdad.org">behdad@behdad.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Tue, Nov 12, 2019 at 5:30 AM Ebrahim Byagowi <<a href="mailto:ebraminio@gmail.com" target="_blank">ebraminio@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">This is very interesting Behdad. Can this have Kashida priority also, like what <a href="https://github.com/harfbuzz/harfbuzz-old/blob/master/src/harfbuzz-arabic.c#L402" target="_blank">harfbuzz-old</a> had.</div></blockquote><div><br></div><div>I'm hesitant to do that. The reason I want to expose this is such that clients can do that while we figure out how to implement justification.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>> [..] even the ones that do NOT use cursive joining.</div><div><br></div><div>Guess this a property of a font rather than a buffer?</div></div></blockquote><div><br></div><div>It's property of how font is designed. Some glyphs in the font might, and others not.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div> IranNastaliq had broken Kashida justification in IE6 but not in IE7, so Microsoft probably has some insight to this, how to detect a font (or a buffer) is not useful for Kashida justification.</div></div></blockquote><div><br></div><div>Interesting. Can you provide test results for this? Let's understand what changed.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>> [,,] The latter definitely belongs to the pos buffer</div><div><br></div><div>Guess can't provide much help here. Just about shape of the API, maybe like the way unsafe to break, hb_buffer_get_glyph_flags, is exposed, would be useful for Arabic joining info and guess exposing priority can be done in the some way but we can just forget about it for now.</div><div><br></div><div>Thanks!</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 31, 2019 at 11:12 PM Behdad Esfahbod <<a href="mailto:behdad@behdad.org" target="_blank">behdad@behdad.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi,<br><br></div>For reason that many of you know (letter-spacing, Arabic elongation, other postprocessing) I like to expose attachment data to the shaping clients. There's two separate pieces so far:<br><br>- The Arabic joining info, which is applicable to all Arabic-like fonts even the ones that do NOT use cursive joining.<br clear="all"><div><div><div><br></div><div>- Mark attachment and cursive attachment. These form a tree with a attachment-type enum.</div><div><br></div><div>I'm not sure which slots in the pos buffer to expose this in. The latter definitely belongs to the pos buffer, whereas the former is more a property of the text. So I feel like we should expose them separately.</div><div><br></div><div>Ideas?</div><div><br></div><div>-- <br><div>behdad<br><a href="http://behdad.org/" target="_blank">http://behdad.org/</a></div>
</div></div></div></div>
_______________________________________________<br>
HarfBuzz mailing list<br>
<a href="mailto:HarfBuzz@lists.freedesktop.org" target="_blank">HarfBuzz@lists.freedesktop.org</a><br>
<a href="https://lists.freedesktop.org/mailman/listinfo/harfbuzz" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/harfbuzz</a></blockquote></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr">behdad<br><a href="http://behdad.org/" target="_blank">http://behdad.org/</a></div></div>
</blockquote></div>