<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">From a programmer’s perspective it is usually much nicer to not have special cases: if U+200B were just a space (i.e. eligible for line breaks) then the rest would follow normally. Now, it could make sense to retrofit a font during font loading with a trivial definition of U+200B if it does not already provide one.<div class=""><br class=""></div><div class="">Disclaimer: I am not familiar with the XeTeX codebase, just commenting from the peanut gallery.</div><div class=""><br class=""></div><div class="">Regards,</div><div class=""><br class=""></div><div class="">Roland<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">30 sep. 2019 kl. 11:57 skrev Suki Venkat <<a href="mailto:suki.venkat@gmail.com" class="">suki.venkat@gmail.com</a>>:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:"times new roman",serif">Exactly!</div><div class="gmail_default" style="font-family:"times new roman",serif">That's how all the browsers seems to behave anyway,</div><div class="gmail_default" style="font-family:"times new roman",serif">i.e., treating 200B as potential point for a line-break,</div><div class="gmail_default" style="font-family:"times new roman",serif">even if it is not defined in the font.</div><div class="gmail_default" style="font-family:"times new roman",serif"><br class=""></div><div class="gmail_default" style="font-family:"times new roman",serif">Suki</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 30, 2019 at 4:55 AM Mike Maxwell <<a href="mailto:maxwell@umiacs.umd.edu" class="">maxwell@umiacs.umd.edu</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 9/29/2019 3:02 PM, Suki Venkat wrote:<br class="">
> Then went on to hack the hyph-ta.texfile and did "mktexfmt xelatex"<br class="">
> to produce nice results using XeLaTeX.<br class="">
> It turned out the uni200B was not defined in the font, although uni200C <br class="">
> and uni200D were defined.<br class="">
> Then managed define uni200B in fontforge and it does seem to produce the <br class="">
> same result even if the uni200B (ZWSP or DLB) is defined in the font or not.<br class="">
<br class="">
I'm speaking from ignorance here--I know nothing of the internal <br class="">
workings of xetex--but it seems to me that the question of defining a <br class="">
glyph for U+200B is beside the point. It should not, it seems to me, <br class="">
have a glyph. Instead, xetex should break the line or not when it <br class="">
encounters this code point, and then--regardless of the line <br class="">
break--delete the character. It's a zero width character, and its <br class="">
height is irrelevant (unlike a strut), so there's no shape to show.<br class="">
-- <br class="">
Mike Maxwell<br class="">
"I am, by a flood, borne back to that wondrous<br class="">
period, ere time itself can be said to have begun;<br class="">
for time began with man." --Herman Melville,<br class="">
Moby Dick<br class="">
</blockquote></div>
</div></blockquote></div><br class=""></div></body></html>