- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Apr 2019 17:03:10 +0000
- To: public-css-archive@w3.org
> I'm also not convinced this ZWSP should be used with Nastaliq... I could be convinced that you're right there. It certainly doesn't seem a good idea given what TUS expects wrt joining behaviour. I note, however, that Firefox and Edge both break the cursive joining, although Chrome and Safari don't. See https://r12a.github.io/pickers/urdu/?text=%DB%81%D8%B1%E2%80%8B%D8%B4%D8%AE%D8%B5%E2%80%8B%DA%A9%D9%88%E2%80%8B%D8%A7%D8%B3%E2%80%8B%D8%A8%D8%A7%D8%AA%E2%80%8B%DA%A9%D8%A7%E2%80%8B%D8%AD%D9%82 for an example. Note further, however, that a difference ZWSP and soft hyphen is that ZWSP is expected to expand when letter spacing or justification is applied to a line. This makes it not quite a simple line-break opportunity indicator. (TUS describes it as "indicates a word break or line break opportunity" and goes on to describe how justification algorithms are likely to add space on p860 of v12.) I'm wondering now how that fits with justification of cursive scripts.... Would it be expected to create kashida-like behaviour when justified, but shrink back to nothing otherwise (unlike tatweel)? -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3861#issuecomment-485890059 using your GitHub account
Received on Tuesday, 23 April 2019 17:03:12 UTC