View Single Post
Old 11-14-2023, 12:04 PM   #18
nabsltd
Fanatic
nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.
 
Posts: 528
Karma: 9529956
Join Date: Aug 2013
Location: Hamden, CT
Device: Kindle Paperwhite (11th gen), Scribe, Kindle 4 Touch
Quote:
Originally Posted by DNSB View Post
I was under the impression ⁠ was just another way of saying Word Joiner though I haven't seen many differences between using ZWJ and WJ.
⁠ is the entity for "word joiner" (U+2060). It used to be that the dual-use code point for "zero width non-breaking space" and "Unicode byte order mark" (U+FEFF) was treated like "word joiner", but that use is deprecated since the new code point has been defined.

The difference between ‍ and ⁠ is that despite the definition, ⁠ means "avoid breaks unless there is absolutely no alternative", while ‍ means "the two characters on either side cannot be separated under any circumstances, because it would change the meaning of the text".

Likewise, using ‌ is not truly correct for avoiding stylistic ligatures, but should be used to avoid ligatures that change the meaning of the text.
nabsltd is offline   Reply With Quote