![ms word hebrew font rtl ms word hebrew font rtl](https://community.rws.com/cfs-file/__key/communityserver-discussions-components-files/90/pastedimage1548073588070v1.png)
This version of the example string will behave the same as the original example string on any normalizing "triple." Examples of normalizing triples would be any triple where HarfBuzz is the shaper or where the application is a web browser. Possibly include outputs (images) for a version of the example string where the marks are in the desired RTL visual mark (vowel) order.Possibly show actual & expected under a differently-behaving shaper/OS/application "triple." For example I think you will find that both actual and expected look bad under DirectWrite/Windows/MS Word, where again "expected" is defined by a font like Taamey Frank CLM.This can be done using a more Biblically-capable font like Taamey Frank CLM, using the same shaper, OS & application.
![ms word hebrew font rtl ms word hebrew font rtl](https://i.ytimg.com/vi/Ge2QcTb7v9k/mqdefault.jpg)
![ms word hebrew font rtl ms word hebrew font rtl](https://jewishsoftware.com/pub/media/catalog/product/cache/dae578f4bd4296164c1825d9e2ef43e8/s/i/simply-script-fontsb_1.jpg)
Specify what the expected behavior looks like.Specify what shaper (and while you're at it, OS & application) was used to generate the actual outputs (image).Thus, this bug could be improved in the following ways: Thus, what behavior one should expect from the example string depends on the shaper in use. But other shapers (notably MS DirectWrite (descended from MS UniScribe)) will leave the string alone.
MS WORD HEBREW FONT RTL CODE
Some shapers (notably HarfBuzz) will transiently re-order the code points of this string to the desired order before the font ever sees it. NFD) order, which is an order not corresponding to the desired RTL visual mark (vowel) order. Note that the example string is given in normalized (e.g. While fonts for non-Biblical Hebrew should probably have some degree of support for vowel marks (though even that is debatable), it may be unreasonable to expect such fonts to handle this weird, Biblically-specific use of vowel marks. So that's how you end up with the "illegal" situation of two vowels on a single consonant ( lamed): in the (implied) qere, there's a yod consonant after the lamed that renders the situation at least sensible if not "legal." Ketiv/qere situations are notated in a variety of ways, but in the cases we're concerned with here, the way they are notated is by putting the vowel marks of the (implied) qere on the consonants of the ketiv. A ketiv/qere situation occurs when what is traditionally read aloud for a word (its qere) is incompatible with the consonants that are traditionally written for that word (its ketiv). These special cases contain only vowel marks.īut the way that these special cases use the vowel marks is specific to a Biblical situation known as ketiv/qere. Thus one could say they are not Biblical Hebrew, according to one definition of Biblical Hebrew. These special cases do not include trope (aka cantillation or accent) marks. (I'm guessing the Noto fonts only strive to support non-Biblical Hebrew.) On the substance of the bugs themselves, I'm not sure how important these bugs are, because I'm not sure how common it is to expect these special cases to be handled in fonts for non-Biblical Hebrew. Simon and I are both using collidoscope under fontbakery on our own projects but I don't think there is any "official" use of collidoscope in fontbakery yet.
![ms word hebrew font rtl ms word hebrew font rtl](http://ilidadirector.weebly.com/uploads/1/2/4/0/124005047/198842716.png)
Are the Noto fonts tested by fontbakery? If so, these bugs could be "formally" caught by passing the handy test string you made to a collision check done by collidoscope. Thanks for at-including me on this, Whenever I see a bug I always wonder whether and how it could have been caught automatically. U+05DD HEBREW LETTER FINAL MEM Screenshots See Firefox bug 662055 or ask for more information. Various inflections of “Jerusalem” in the Tanakh include two vowel signs side by side after the lamed, but in Noto, the vowel signs overlap. NotoSerifHebrew-Regular.otf Where the fonts came from, and when