For the Open Siddur Project, we have plain text files encoded in UTF-8 available for direct download. Thing is that web browsers will display plain text files just as well as web pages. Now that shouldn't be a problem when instructed to use UTF-8 in a properly written web page. Chrome on Windows and other browsers have their character encoding set by default to ISO-8859-1. (Or just not use a table - but I think the align attribute is deprecated on all elements since HTML 4 even though browsers still support it for legacy pages.) On the table that includes the reference image you probably want style="text-align: right" (either as an attribute or in the style sheet) rather than align="right".the latter makes the table float right and the result table wrap around it which I don't think is that you want (the third image attached to Ze'ev message shows this). What does the column mean - how is that different from the Ezra (or Miriam) columns? Is there a reason you don't include a column for the system font result?Ĥ. If you're still having an issue there let me know and we can try to figure out why you're getting different results than I am.ģ. I don't have an issue with the system font with IE 9 on Windows 7. It sounds like you are saying "dagesh preceding dagesh" but maybe you mean something else? Also there's a typo in "including".Ģ. What do you mean: "dagesh preceding all other niqud in letters inlcuding dagesh (dot) and niqud (vowel)" Rely on the console's settings) that doesn't respect the declaredġ. Not something ancient like IE6 or that's systematically forced to useĪnother character encoding, like any of the console-based browsers that Put another way: Aharon, do you know of any modern browser (that means Hebrew) will display, he/she should not put much faith in fallback If the web designer cares at all about how something exotic (like That's likely to be different on any computer and for any different That's why I don't think the "system font" test is instructive at all
(2) Some browsers (eg, Firefox) have user-specified default fonts for a The encoding should be declared in the XMLĭeclaration, in a meta tag, and/or in the HTTP response headers. (1) The default character encoding - in a proper web page, this should I *think* that Aharon may be referring to two settings: Problems) but the system font diacritic placement is much better than Miriam CLM and Ezra SIL with (this is probable because I can display those fonts in a UIWebview without On iOS 5.0 on the iPhone, Safari produces LOUD diacritic errors for Attached are screenshots of the 3 tests (from Mac The default system fontĭiacritic positioning is not always pretty (but you don't have aĬolumn for that anyhow), but the Ezra SIL, Miriam CLM, and seem to be ok. (unless I misinterpreted what you're testing). I tried the test page on:Īnd it looks (to me) like both are passing some of the tests now You indicate n/a, FAIL, FAIL for the 3 test results and say skipped Miriam CLM. In your browser results table, for Mac OS X 10.6.6 and Safari 5.0., > The good news is that most modern browsers are performing well. > browsers I tested in Windows 7, GNU/Linux, and Android. > I made some changes for clarity of language and updated the results for the > Just updated the web browser tests for and Hebrew diacritic In any case, please take what I've done here and if it inspires you, you are free to take the source and make improvements. With some JS indicating to the user that their browser may not be setup correctly to view a website with Hebrew, users could be better informed. I've seen browsers set to other encodings display Hebrew correctly even when the code should be instructing the browser to use utf8. It would be really great to have some javascript to report back on what the browser has set as the default character encoding. Links (CLI) will not do unicode Hebrew and although its GUI version will, it will display asterisks in place of niqqud. Unfortunately, Hebrew only displays LTR, rather than RTL. I saw improvement with Lynx (CLI) and Links (the GUI version) which will now display Hebrew without having to make any settings changes. In my tests, Epiphany also is still having trouble positioning Hebrew with niqqud correctly. The bad news is that I'm still seeing niqqud positioning errors on Android's browser and Firefox on Android. The good news is that most modern browsers are performing well. I made some changes for clarity of language and updated the results for the browsers I tested in Windows 7, GNU/Linux, and Android. Just updated the web browser tests for and Hebrew diacritic positioning.