Wikipedia talk:Niqqud

message: Jason's (Yosl's) page Recommendations for Displaying Yiddish text on Web Pages explains how punctuation is handeled
* by different platforms / operating systems
* used browsers
* affected characters
* (fonts)
Jason (Yos'l) asked me to compare
# http://mysite.verizon.net/jialpert/Yiddish/PartizanerHymn.htm (where pre-combined characters are used)
# http://jadesukka.homelinux.org:8180/golem/%D7%96%D7%90%D6%B8%D7%92_%D7%A0%D7%99%D7%98_%D7%A7%D7%B2%D7%A0%D7%9E%D7%90%D6%B8%D7%9C (where NON-pre-combined characters are used)
I am using Windows XP and Mozilla Firefox and both pages are loking fine. I could not compare the pages at Unicode level - page source did not show unicode entities coded as &#nnnn; which would allow to distinguish precombined characters from NON-precombined ones.
Using "copy and pasts" from both page sources I could see that MediaWiki is performing some normalisation. This is required because else "duplicate entries" could be created using the different methods:
# :yi:User:Gangleri/tests/אָ
# yi:User:Gangleri/tests/%EF%AC%AF
# yi:User:Gangleri/tests/%D7%90%D6%B8
I assume that the following scenario could be the reason for "what happened":
* original pages where created with unicode entities coded as &#nnnn;
* the page was using precombined characters which displayed properly at some platforms in some browsers
* at some point when :en: changed from Latin-1 to UTF-8 type wiki and / or "normalisation" changed someone made an "minor edit" but the page(s) where then generated differently addressing known "weekpoints" / "bugs" 
Regards Gangleri | [ Th] | T 22:29, 27 October 2005 (UTC)
thread_title:  Precombined characters - NON-precombined characters 

message: I tried to get the dagesh before the tsere in the menuqqad spelling of Esther, and it was pretty much impossible... AnonMoos 06:22, 27 September 2006 (UTC)
thread_title: Esther

message: What does:
:::"But any attempt to revert to a version with the correct coding is automatically destroyed."
mean? the MediaWiki software deletes this version on it's own?! The Transliterator • talk 12:30, 19 December 2006 (UTC)
thread_title:  automatically destroyed? 

message: I use Firefox in Windows and I also get rendering problems.  I don't think it is a font issue, as I can just copy/paste the text in Word, use the same font, and it gets rendered fine.  I believe this is a FF issue.  
On Windows, IE7 works much better than FF in Hebrew vowel rendering.  Opera and Safari both have the same problems as FF.  —Preceding unsigned comment added by 67.96.163.10 (talk) 15:34, 3 January 2008 (UTC)
thread_title: Jonathan

message: BabelPad is a powerful Unicode text editor for the Windows platform. The most recent versions have an option for the custom normalization of Hebrew text. This option implements the special Canonical Combining Class scheme recommended in the SBL Hebrew Font manual issued by the Society of Biblical Literature. This may prove useful for repairing damaged Hebrew text. DFH (talk) 19:10, 24 August 2015 (UTC)
thread_title:  The BabelPad Unicode text editor for Windows and the custom normalization for Hebrew 

message: In case anybody wonders... This page's current contents are quite outdated. They mostly discuss bugs that were happening on old operating systems and web browsers, that are hardly used by anybody today. Most of the current content should be summarized to one short paragraph and removed entirely when these operating systems and browsers go totally out of use.
However, a modern guide for using niqqud would be quite useful. I might find time to write one some day, but feel free to do it yourself, as I've got a bunch of other things on my plate :) --Amir E. Aharoni (talk) 06:51, 10 September 2017 (UTC)
thread_title:  Needs update