This page was last revised on: 21 December 2008 (previously: 12/30/06)
What is the Best Way to Display Yiddish / Hebrew Text on Websites?

Kosher Yiddish Website
Click here for the Homepage.
These links are to locations below on this page:
Recommendations for Displaying Yiddish text on Web Pages
Precombined Character Chart   NON-Precombined Character Chart
List of Links to Yiddish Websites Worldwide

How To Navigate This Web Page
Some links on this page are to OTHER websites. These "off site" links are designed to open in a NEW browser window. To return to where you were on THIS page, just CLOSE that new browser window.

Other links on this page are to different locations right here on this same page (below). After clicking on one of THESE links, just click the browser's BACK button to return to where you were (or press the Alt+Left-Arrow key-combination).

Background

On the Internet, Yiddish is sometimes displayed as real text, i.e., text that can be searched. This is ideal.

For this reason, Israeli Hebrew websites are almost universally created with real searchable Hebrew text. (In fact, if you enter Hebrew text into a Google Search dialog box, you'll get many hits. Try it! You'll even find THIS website.)

Unfortunately, Yiddish on the Internet (unlike Hebrew) is usually displayed in GIF or PNG images -- which cannot be searched. Some websites that display Yiddish as GIF images are the Yiddish Forward and Yugntruf.

So the obvious question is (שטעלט זיך די פֿראַגע): If indeed real text is so much better, then why do many Yiddish websites use GIF images?

In a nutshell, the answer is simply because the aforesaid Yiddish websites insist that the Yiddish text that they display must have nikud (diacritics, nekudes, n'kudot). And Yiddish / Hebrew characters with nikud (diacritics) often do not display properly on the user's monitor.

The Israeli Hebrew websites -- and even the Israeli Yiddish websites (see list below) -- avoid this problem by almost universally displaying Hebrew / Yiddish text entirely without nikud.

On her excellent and definitive website http://www.shoshke.net/uyip/sum-web.htm, Shoshke-Rayzl Yuni (Susannah R Juni) discusses this matter. The following is paraphrased from Shoshke's website: "If you want to create web pages with nikud that all Yiddish readers can read, regardless of which computer system is used to visit the web pages, then the only current option is to create pictures of the Yiddish text, and to display it on your pages as graphics, e.g., GIF images."

Shoshke-Rayzl writes further, "While you can create (real text) Yiddish web pages in Unicode (UTF-8) (e.g., using Word 2000/2 in Windows 2000/XP), not everyone will be able to read the complete text (i.e., the characters that contain nikud) without errors, depending on their operating system. Therefore, Unicode web pages are not recommended at this time, unless you create alternative sites (e.g., with GIF files representing the Yiddish text) - double work for the web page author." [End of quote from Shoshke-Rayzl's website] (Or unless, I might add, you just leave out the nikud entirely.)


As mentioned above, Yiddish /Hebrew characters with nikud often do not display properly on the user's monitor.

The obvious way to avoid this problem is to simply create websites entirely without nikud. And, frankly, I am tending to lean more and more in this direction. Perhaps this is indeed the best approach to use -- at least for the time being.

Nevertheless, I will try to present you below with a thorough analysis of the difficulties of creating website (HTML) documents with nikud, and the best possible advice on how to actually go about producing just such website documents.


Problems in Displaying Yiddish Characters That Have Nikud (Diacritics)

When does one encounter the problem of nikud not displaying properly? This depends not only on which operating system is used (as Shoshke-Rayzl writes), but also on which browser is used. And it also depends on which type of Unicode UTF-8 characters are used to represent the character that has the nikud (diacritics) -- i.e., whether Unicode precombined or NON-precombined characters are used, as will be explained below.  Meanwhile, let's take a look at some examples of the actual problem.

Illustration of Problems in Displaying Yiddish Characters That Have Nikud (Diacritics)

Table 1 contains all of the Yiddish characters and character-combinations that have diacritics (Nikud/Niqud). Because these characters contain nikud, they may not display properly (on your monitor) under all Operating Systems.

Table 1. GIF Images of Yiddish Characters That Contain Nikud
Single Characters with nikud
pasekh alef
komets alef
veyz melupm vov khirek yud
pasekh alef komets alef veyz vov yud

kof pey fey sin tof
kof pey fey sin tof

A Character Combination with nikud (pasekh tsvey-yudn)
i as in ride



Table 2. GIF Images of Yiddish Character-Combinations That Do NOT Contain Nikud
tsvey vovn
zayen-shin daled-zayen-shin tes-shin vov-yud tsvey-yudn
v as in victor zh as in Zhitomir j as in Jewish tch as in Tchekhov
oy as in toy
ey as in they
v as in violet s as in measure j as in judge ch as in cheese oy as in toy a as in date

Because they contain no nikud, the characters in Table 2 above do display properly under all Operating Systems.

NOTE: The characters in the two Tables above are from YIVO's Transliteration Chart.

Back to Top
Definition of Diacritics and Character-Combinations (Ligatures)
Diacritics (a/k/a nekudes / n'kudot / n'qudot / nikud / niqud) are Hebrew "non-spacing marks." Table 1 above contains GIF images of  the Yiddish characters (and a character combination) that contain diacritics. Examples of diacritics include the pasekh or komets under the alefs in Table 1 above. Other diacritics there are the pasekh under the tsvey-yudn, the horizontal line above the pey (that transforms it into a fey); the dot (dagesh or pintl) in the tof; etc.

The word diacritics does NOT include whole Yiddish character combinations (ligatures), such as the pasekh-alef or komets-alef or pasekh tsvey-yudn in Table 1 above.

Yiddish Character-Combinations are Hebrew letters combined with other Hebrew Letters, as illustrated in Table 2 above, as well as the pasekh tsvey-yudn that is illustrated in Table 1 above.


Illustration of Display Problems That Occur When Running Windows ME and Lower

Here is an example of some real searchable UTF-8 Yiddish text. It is from the Yiddish Dictionary Online:

Table 3. Real Searchable UTF-8 Yiddish Text
ייִדיש װערטערבוך אַפֿן װעב
Transliteration: Yidish Verterbukh Afn Veb

I
f you are running Windows XP or 2000, and if your browser's character encoding (on the View menu) is set to Unicode (UTF-8), then the Yiddish text above should display correctly no matter which browser you use.

But if you are running Windows 95/98/ME, and using the Netscape 7.2 or Firefox 1.0 Browser, then the text above does not display properly. Rather it displays as shown in Table 4.

Table 4. GIF Image of How the Above Text Displays in Win 95/98/Me When Using the Netscape 7.2 or Firefox 1.0 Browser
YiddishME.gif

In this case, you must use Microsoft's Internet Explorer Browser (version 5 or higher) for the text to display properly (as shown in the GIF image in Table 5, below).

Note: If you use Netscape 4.8 or earlier -- or another outdated browser, the Hebrew letters will appear backwards (left-to-right rather than right-to-left). To view Yiddish real-text web pages, you must use an up-to-date browser!


Table 4 graphically illustrates the problem of displaying Yiddish letters with nikud. Reading the text in the above GIF image, you will observe that the Hebrew text (from right-to-left) is Yud -Yud - Khirek, where the Khirek is under a blank space to the left of the Yud. But the Khirek (Chiriq) should NOT be under a blank space. Rather it should be under the second Yud (Yod) itself!

Reading further from right-to-left in the above Hebrew, you will see an Alef followed by a Pasekh which is also under a blank space. But, again -- the Pasekh should be under the Alef, NOT under the blank space to the left of the Alef.

Finally, the horizontal line that is supposed to appear above the Pey (to transform it into a Fey) actually appears above the blank space that is to the left of the Pey!

As mentioned above, these display problems occur only when running Windows 95/98/Me, and when using browsers other than Internet Explorer. They do not occur when running Windows XP.

Table 5. GIF Image of How the Above Text Displays in Windows XP When Using ANY Browser, or in Windows 95/98/Me When Using Microsoft's Internet Explorer Browser
YiddishXP.gif


A very technical discussion of the above issue is presented on the Bugzilla-Mozilla website. There, the problem is described as follows: When Unicode web pages containing Hebrew/Yiddish Diacritic marks are displayed ....... they appear BESIDE the character that they should appear BENEATH.

On that website, they present an excellent GIF image that clearly illustrates this problem. At the left side of the illustration, you see how Yiddish text displays incorrectly in Mozilla (Mozilla is basically the same as Netscape and Firefox), and at the right, you see how Yiddish text does display correctly in Microsoft Internet Explorer. Click here to see this illustration.



Now that we've seen actual examples of the problem of displaying Yiddish characters that have nikud, let's focus our attention on measures that we can employ to solve (or at least mitigate) this problem.

As mentioned before, when this problem occurs depends not only on which operating-system is used, but also on which browser is used. And it also depends on which type of Unicode UTF-8 characters are used to represent the characters that have the nikud -- i.e., whether Unicode UTF-8 precombined or NON-precombined characters are used. We'll now discuss in detail the subject of Unicode UTF-8 precombined and NON-precombined characters.

Back to Top

Yiddish Precombined & Non-Precombined Characters Under Unicode

In an email dated 17 December 2004,  Professor Raphael A. Finkel describes the two methods for encoding combinations of letters with nikud that Unicode (UTF-8) provides. I have paraphrased his remarks below.

Unicode (UTF-8) provides two methods for encoding letters that are combined with diacritics (nikud).
1. Using "precombined" characters.

Some examples of precombined characters are á (a acute), ö (o umlaut), and אַ (pasekh alef).
2. Using "NON-precombined" characters, -- i.e., combining characters by using base letters followed by zero-width combiners.

Some examples of non-precombined characters are á (a acute), ö (o umlaut), and אַ (pasekh alef).

Using non-precombined characters has the advantage of allowing vastly more possibilities than are available using precombined characters. This is because every precombined character uses up a code point (code location) in the Unicode UTF-8 Chart (PDF)., and the total number of available code locations, although huge, is still limited.

Thus, e.g., if one wants an alef-acute  א́ or an alef-umlaut   א̈, he can create it only by using non-precombined characters. Odd-ball character combinations such as an alef-acute or an alef-umlaut cannot be displayed using precombined characters, because there exist no precombined characters for them. (No precombined characters have been defined for these, because they are in the category of milso d'loy she-KHI-kho, and you know what the Gemore says: Milso d'loy she-KHI-kho, loy gozru bo rabonon.)

Unfortunately, this second method, although much more productive than the first method, sometimes leads to misprints in display, as described hereinabove.

To further illustrate the difference between these two methods, let's look at some identical text that's been typed using both methods. This appears in the Table below. It is Yiddish text for the phrase "Graf Pototski -- Der Vilner Ger-Tsedek."

1. Created using precombined characters גראַף פּאָטאָצקי ־ דער װילנער גר־צדק
2. Created using non-precombined characters גראַף פּאָטאָצקי ־ דער װילנער גר־צדק
(I used the above text created using precombined characters for an article on my synagogue's website at www.chelseashul.org/Judaism/Pototzky.htm.)
If you are using Internet Explorer, both of the above lines of Yiddish text should appear identical.
But this is NOT the case if you are using Netscape or Firefox under Windows 98 or Me.

Because of the above-illustrated display problems that are encountered when using Netscape or Firefox under Windows 98 or Windows Me, I personally recommend, for the present, using precombined characters (method 1, above) for creating Yiddish web pages. When one uses this method, the web page's text appears correctly using ALL up-to-date browsers under ALL Operating Systems (as far as I know....).

In the future, when newer improved versions of the Netscape or Firefox browsers are released, we will be able to use NON-precombined characters (method 2).


To facilitate the use of precombined (a/k/a
precomposed) characters, I have compiled this Chart. You can simply copy characters from Column 2, below, and paste them into your document:
Back to Top
Chart of Unicode Precombined Hebrew/Yiddish Characters That Contain Nikud
1
2
3
4
5
6
7
GIF or PNG Image

Unicode Name Unicode Hex
Windows
Core /
Hebrew
Fonts
Arial
Unicode
MS /
Guttman /
Ezra SIL
HTML Entity (decimal)

pasekh alef Hebrew Letter Alef with Patah
(Pasekh Alef in Yiddish)
FB2E yes yes אַ
komets alef Hebrew Letter Alef with Qamats
(Komets Alef in Yiddish)
FB2F yes yes אָ
bet.gif
Hebrew Letter Bet with Dagesh
(Beyz in Yiddish)
FB31 yes yes בּ
veyz Hebrew Letter Bet with Rafe
(Veyz in Yiddish)
FB4C yes yes בֿ
vov Hebrew Letter Vav with Dagesh
 (Melupm-Vov in Yiddish)
FB35 yes yes וּ
kholam.png

Hebrew Letter Vav with Holam FB4B
yes yes וֹ
kof Hebrew Letter Kaf with Dagesh
(Kof in Yiddish)
FB3B yes yes כּ
pey Hebrew Letter Pe with Dagesh
(Pey in Yiddish)
FB44 yes yes פּ
fey Hebrew Letter Pe with Rafe
(Fey in Yiddish)
FB4E yes yes פֿ
shin.png Hebrew Letter Shin with Shin Dot FB2A yes yes שׁ
sin Hebrew Letter Shin with Sin Dot FB2B yes yes שׂ
tof Hebrew Letter Tav with Dagesh
(Tof in Yiddish)
FB4A yes yes תּ







yud Hebrew Ligature Yiddish Yod with Hiriq
(Khirek-Yud in Yiddish)
FB1D no
יִ
i as in ride Hebrew Ligature Yiddish Yod Yod Patah
(Pasekh Tsvey-Yudn in Yiddish)
FB1F no yes ײַ
Hebrew Punctuation - (Not characters with nikud - just inserted below for your convenience)
Maqaf.png
־ Hebrew Punctuation Maqaf
05BE yes
yes
־
Left Double Quotatiion Mark.png

Left Double Quotation Mark
U201C


“
Right Double Quotation Mark.png

Double Low-9 Quotation Mark
U201E


„

1
2
3
4
5
6
7
This Chart has been adapted from a chart on the website www.jewish-languages.org. Additional characters have been added from a more complete character chart that is found at www.fileformat.info. The Images in Column 1 above are from YIVO's website and from the fileformat.info website. Values for the .HTML Entity in Col. 7 were also obtained from the fileformat.info website.


Problems Displaying Khirek-Yud and Pasekh Tsvey-Yudn Using Precombined Characters

On many computers (including mine), the precombined khirek-yud and the precombined pasekh tsvey-yudn in Column 2 above do NOT display properly. On my computer they display as question marks when I use Netscape or Firefox, and as rectangles when I use Internet Explorer.

This is because the Windows Core Fonts -- the fonts that always come preinstalled in Windows -- do NOT support the precombined khirek-yud nor the precombined pasekh tsvey-yudn (as noted in the Character Chart above). In order for these precombined characters to display, the user must install on his computer an additional font -- such as Arial Unicode MS (mentioned in the heading of Column 6 above), which does support these.

(Note that the Windows Core Fonts do support the other precombined character combinations needed by Yiddish. And, of course, they support all characters created using Method 2 (NON precombined characters). See the Jewish-languages.org website for a full discussion of this.)

To me, the fact that the khirek-yud displays improperly does not matter. I think that the khirek-yud is ugly, and I can get along without it quite well. I'll stick with Yudel Mark, and use the Shtumer Alef instead. (For example, I'll write העברעאיש and not העברעיש.)  Note, though, that my Yiddish guru holds that for certain words -- such as tsiyen, fliyen, geshriyen, and diyalekt --  the khirek-yud is indispensable. While I agree that using the khirek-yud for these words DOES make them more legible, I feel that most people who read Yiddish will recognize that, for example, ציען is TSI-YN and not TS-YEN. So I don't quite agree that the the khirek-yud is indispensable. It's nice to have it, but we can get along without it.

But the pasekh tsvey-yudn is different. The fact that the pasekh tsvey-yudn displays improperly is most unfortunate. I guess that for the time being we'll just have to substitute a plain tsvey-yudn for the pasekh tsvey-yudn. Alternatively, we can right now use the pasekh tsvey-yudn, but the one that is created using method 2 -- because this method is supported by the aforesaid Windows Core fonts. That would mean that one lousy character combination, the pasekh tsvey-yudn, won't display quite perfectly under Windows Me using the Netscape or Firefox browser -- until newer improved versions of these browsers are released.

Professor Raphael Finkel seems to agree that for the time being, some of us might want to settle for using precombined characters, even though he would prefer to use method 2 (non-precombined characters).

In an email dated January 25, 2005, Professor Finkel writes (paraphrased):
I have also noticed that Firefox on Unix does not handle non-precombined characters correctly.
 
Although I think that in the long run, Unicode with non-precombined characters (Method 2 above) is the right way to represent text, we might choose in the meanwhile to use precombined characters.

I have added a facility to my shraybmashinke to let you generate UTF-8 with precombined characters.  It seems to work fine, although my fonts (on the professor's computer) apparently don't include khirek-yud.

Back to Top
Conclusion: Recommendations for Displaying Yiddish Text on Websites

On http://www.jewish-languages.org/windows.html it states that "precomposed (precombined) Hebrew characters exist only for the sake of backward compatibility with legacy encodings, and it is therefore recommended to avoid them and use combinations of characters (i.e., NON-precombined characters) instead."

Despite this, it is MY recommendation that for the present time and for Yiddish (but NOT Hebrew) web pages, we should ignore the above advice, and instead use davke precombined characters.

Or else, we should create Yiddish web pages using no nikud at all.


(See also below the section entitled Displaying Hebrew With Nikud vs Displaying Yiddish With Nikud.)

By "for the present time" I mean -- until browsers (other than Internet Explorer) have been upgraded so that they permit Yiddish characters with nikud to display properly (i.e., without "misprints in display") when operating on all platforms (Windows 95/98/Me included, as opposed to the more advanced Windows 2000 or XP).

Note also that if following the recommendations herein results in not using the so-called "YIVO standard Yiddish orthography" -- then so be it. As is obvious from my Notes on YIVO's Yiddish Spelling Conventions, below, I am no great fan of the YIVO standard anyway.


new4a.gifBefore proceeding with the discussion of how to enter Yiddish text WITH nikud into your HTML (website) document using UTF-8 precombined characters,  please read the following comments on how to go about creating HTML (website) documents WITHOUT nikud:

An Alternative - Creating Yiddish Web Pages Without Any Nikud At All
Even though I personally prefer to show as much nikud as possible, still -- there is a compelling reason to consider just leaving out the nikud entirely.

The advantage of leaving out the nikud is two-fold:

1. You can enter Hebrew / Yiddish text into your HTML document by just using the keyboard support that comes built into Windows. (How to activate Windows'  built-in Hebrew keyboard support is explained below.) You do not need to download and install any special Yiddish keyboard layouts. Windows' built-in Hebrew keyboard layout does not, of course, support any of the Yiddish character combinations mentioned above -- but these are not needed when you leave out the nikud.)

2. If your website contains no nikud, then search engines will much more readily succeed in finding strings of text (words and phrases) on it.

This  is best illustrated by the following real-life example:

My Yiddish Glossary contains the title אידישער ווערטערשאַץ --with a precombined alef (אַ).

Accordingly, I did a Google Search for אידישער ווערטערשאַץ -- with the precombined alef (אַ).

And guess what -- the only hit was my above Yiddish Glossary.

Sounds good, right?

Wrong.

Because I THEN did a Google Search for אידישער ווערטערשאץ  -- with just a PLAIN alef (א).

I got no results.

The unfortunate situation is, that someone searching for the phrase "אידישער ווערטערשאץ" will have to search for it by using three different spellings: 1) with a plain alef, 2) with a precombined patekh-alef, and 3) with a non-precombined patekh-alef -- in order to be sure to find it.

Likewise, Professor Finkel, in a posting to UYIP on 07 Feb. 2005 wrote:

"I can confirm Jason's (Yosl's) observation that Google (and most likely other search engines) store and match text exactly, making no allowances for combining-characters (= non-precombined characters) and precombined characters. It's all just sequences of bits. The result is that manana, mañana (precombined), and mañana (combining tilde) are three separate words as far as search engines are concerned."

Perhaps the above situation is the main reason that most of the Yiddish websites in Israel, and some here in America, too, use real Hebrew text that is totally WITHOUT any nikud whatsoever -- or in some cases, with a minimum of nikud.

Update - December 2008: Yiddish Searches Now Done Right at Google.com
In an email to fellow members of UYIP on 19 Dec. 2008, UYIP moderator Mark H David wrote:

"I'm very pleased to report that Googling is great in Yiddish.  This is because the searching now folds in all variants in nekudes and use of special Yiddish digraph characters (tsvey vovn, tsvey yudn, and vov-yud) -- such that you get the same (or nearly the same) results. 

For example, the yiddish word "vayb" is commonly spelled a couple of ways, e.g.,

tsvey-vovn tsvey-yudn beys װײב
tsvey-vovn pasekh-tsvey-yudn beys װײַב

Unicode provides a multitude of possible ways encode these two variants:

vov vov yud yud beys ווייב
tsvey-vovn tsvey-yudn beys װײב
tsvey-vovn yud yud beys
װייב
vov vov tsvey-yudn beys ווײב
vov vov pasekh-tsvey-yudn beys ווײַב
tsvey-vovn pasekh-tsvey-yudn beys װײַב

What should happen?  Spelling the word "vayb" any of the two ways, using any of the possible encodings, should match all occurances of any of the spellings or encodings.  This is analogous to case folding with Latin-script
languages.  E.g., searching for "WiFe" will find "wife", "WIFE", "wifE", etc.

I have tried Yahoo! search, and they don't do this right.  Kuddos to Google for doing this!"


Here, for example, are some Israeli Yiddish Websites that leave out the nikud:

Website of the Israeli National Authority for Yiddish Culture

Website of “YiddishShpiel,” the Yiddish Theater in Israel

This EXCELLENT Australian Yiddish site leaves out the nikud (as well as the phony Weinreich neologisms!):

SBS Radio's Yiddish Language Program (Also: Listen to streaming Yiddish radio broadcasts on SBS Radio!)

This Russian website has Yiddish text without nikud:

Yiddish poetry by Yakov Glatstein (Яков Глатштейн)

And here are some American Yiddish Websites that follow suit (mostly on Algemeiner Journal.com ):

Article by Rabbi Dr Heshil Klepfish Entitled "Dos Gezang Fun Akdomes"

Obituary of Gershon Jacobson by Elie Wiesel

Obituary of Gershon Jacobson by Yehoshua Dubrowski

Chassidic website that discusses whether a pious Jew is allowed to go on the Internet while alone

Website for NYC Mayor Mike Bloomberg's 2005 Campaign

The Best of Both Worlds

In my Yiddish Glossary I try to list Yiddish entries in two forms:

1) with nikud -- which is more legible for the visitor, and
2) without nikud
-- so that search engines will more likely find words contained in the Yiddish Glossary.

And I recommend that if possible you should do likewise in your HTML (website) document.

That is, try to include on your web page duplicate copies of any Yiddish text that you want to be found by search-engines -- one copy with nikud, and the second copy without nikud.

Furthermore, (as stated above) the Yiddish text that is with nikud should use Unicode UTF-8 precombined characters -- NOT the NON-precombined characters.

If it is not practical for you to have duplicate copies, then just follow the example of the multitudinous Yiddish websites in Israel -- enter your Yiddish text totally WITHOUT using any nikud whatsoever.

This is still better (IMHO) than resorting to GIF images, as do the
Yiddish Forward and Yugntruf, mentioned above. Those websites -- notwithstanding their rich content -- get ZERO hits (on their Yiddish text content) from search engines.

Now please read below the details about how to enter Yiddish text with nikud into your HTML (website) document.


I recommend using Unicode Precombined characters for the following character combinations:

אַ - pasekh Alef
אָ - komets Alef
בּ - beyz
בֿ - veyz
וֹ - khoylem vov
וּ - melupm vov
כּ - kof
פּ - pey
פֿ - fey
שׁ - shin
שׂ - sin
תּ - tof
All of these are presented in the Character Chart above.

Recommendation for Khirek-Yud and Pasekh Tsvey-Yudn

However, for the Khirek-Yud and Pasekh Tsvey-Yudn, my recommendation is different.

Khirek-Yud: Even though there does indeed exist a Unicode precombined khirek yud, I still advocate either 1) not using the khirek yud at all [i.e., replace it with the original (pre-YIVO) shtumer alef followed by a regular plain yud, as in פייאיק] or 2) using the Unicode NON-precombined khirek yud (see chart below).

Pasekh Tsvey-Yudn:  Similarly, even though there does indeed exist a Unicode precombined pasekh tsvey-yudn, I still advocate either 1) using the Unicode NON-precombined pasekh tsvey-yudn (see chart below), or 2) not using the pasekh tsvey-yudn at all [i.e., replace it with two regular plain yuds, יי].


To facilitate the use of NON-precombined characters for the Khirek-Yud and the Pasekh Tsvey-Yudn, I have compiled this Chart. You can simply copy characters from Column 2, below, and paste them into your document:
Back to Top
Chart of Unicode NON-Precombined Khirek-Yud and Pasekh Tsvey-Yudn
1
2
3
4
5
6
7
GIF or PNG Image

Unicode Name Unicode Hex
Windows
Core /
Hebrew
Fonts
Arial
Unicode
MS /
Guttman /
Ezra SIL
HTML Entity (decimal)

yud יִ Hebrew Letter Yod + Hebrew Point Hiriq
(Khirek-Yud in Yiddish)
05D9 + 05B4 yes yes
י + ִ
i as in ride ײַ Hebrew Letter Yiddish Ligature Double Yod + Hebrew Point Patah
(Pasekh Tsvey-Yudn in Yiddish)
05F2 + 05B7 yes yes ײ + ַ
This Chart has been adapted from a chart on the website www.jewish-languages.org. The Images in Column 1 above are from YIVO's website. Values for the .HTML Entity in Col. 7 were obtained from the website www.fileformat.info.


Why is my recommendation for the khirek yud and the pasekh tsvey-yudn DIFFERENT than for the other character combinations listed above? This has already  been discussed in great detail hereinabove.





Back to Top
Notes on Unicode (UTF-8) for Yiddish
The description below is adapted from Shoshke-Rayzl Yuni's website http://www.shoshke.net/uyip/unigen.htm. The reader is urged to visit Shoshke-Rayzl's website, and read the Unigen.htm document in its entirety. (Even though the Unigen.htm document has not been revised since 04/14/2002, the information in it is still highly accurate and informative.)
There's a universally accepted scheme which allows computers to recognize a character (i.e., a letter of the alphabet, a number, punctuation, diacritic, nikud, etc.). This scheme has been around since the beginning of computers. It's called ASCII.

Unicode is a new system for coding character sets (i.e., letters of the alphabet) which is similar to ASCII, in which a code (say a number) is assigned to each letter. The difference between Unicode and ASCII is that Unicode exponentially increases the number of code locations available, making it possible to create a standardized code with a unique computer-readable code for every letter of many different alphabets. (There just weren't enough slots within the ASCII system to accommodate all the letters of all of the alphabets of the world.)

Standardized Unicode alphabet codes already exist for many languages, including Yiddish thanks to UYIP, whose Moderator, Mark David, has been corresponding with appropriate people at Microsoft and Apple to make this happen. To see the official list of Unicodes for Hebrew and Yiddish, see http://www.unicode.org/charts and http://www.microsoft.com/globaldev/reference/WinCP.asp.

Advantages: An advantage of Unicode is that it uses actual text in which one can search for a word. Also, text is usually smaller than say an image and so it takes up less memory. Someday, it will probably be universal; i.e., anyone will be able to share the text between computers, regardless of the type of system.

Disadvantages: The disadvantage is that the current Unicode version which supports Yiddish (UTF-8) is not yet usable consistently by everyone. [End of quote from Shoshke-Rayzl Yuni's website]


Technical Stuff for Nerds

This Section is Still Under Construction!
An expert in both Yiddish and Computer Programming, describes the above problem as "misprints in display." He writes that this problem is purely the fault of the display engine (the code that renders text onto screens, accommodating fonts and formatting), and NOT the encoding of the original text.

Evidently the display engine in Windows 98 or ME is not as advanced as the display engine in Windows 2000 or XP. The Internet Explorer's built-in display engine seems to overcome the deficiency of the Windows 95/98/Me operating system, but Netscape and Firefox (so far) do not.

The expert notes that over the past few years, display engines have improved. They often handle bi-directional text well, although seldom perfectly. They often handle combining characters, but not always (as in Windows 95/98/Me).

In particular, the expert says, the Firefox browser under Linux does bi-directional text well, but does not properly render combiners, giving each character its own space (which is why the Khirek described above is under a blank space to the left of the Yud, and not under the Yud itself, where it belongs). Firefox on Windows 2000 does a far better job.


Back to Top
Displaying Hebrew With Nikud vs Displaying Yiddish With Nikud
To display Hebrew with nekudes, the use of NON-precombined characters is essential. An excellent example is Mr. Carl Goldin's website Pirkei Avot - Hebrew Text with Nikkudot. This website must be viewed with "Internet Exploder" -- because Firefox and Netscape mess up the nekudes/nikkudot (unless you are running Windows XP or 2000). Try it!

But IMHO their use is totally unnecessary for Yiddish. For Yiddish, precombined characters are just fine.

Let me explain.


As is quoted above in the name of Shoshke-Rayzl, Unicode exponentially increases the number of code locations available, making it possible to create a standardized code with a unique computer-readable code for every letter of many different alphabets.

Still, the total number of code locations even within Unicode is limited (finite).

Creating a precombined character for every possible combination of letters and nikud for Hebrew would be impossible, because the number of such possible combinations is staggering. That is, the required number of code locations would approach infinity.

However, for Yiddish this is no problem at all.

Unicode has a precombined character for every glyph in Table 1 (11 glyphs) and Table 2 (6 glyphs) because these only takes up 17 code locations in the Unicode chart.

[Actually, there is really no need for a precombined character for 3 of the glyphs in Table 2 -- namely, the zayen-shin, the daled-zayen-shin, and the tes-shin. This is because, as noted above, these character combinations can be input into a document by simply typing the individual characters that make them up.]

IMHO, using Unicode precombined characters makes it possible to correctly display Yiddish on the web with all the proper nikud, under ALL operating systems, and using ALL browsers. The only problems encountered (as discussed above) are the khirek-yud and the pasekh-tsvey yudn.


Back to Top
How to Install Hebrew Keyboard [and Hebrew Language] Support in Windows

The text below is quoted from an email sent by Carl D. Goldin :

You can "install" a Hebrew keyboard [and Hebrew language support] (with W98) by clicking "Start > Settings > Control Panel > Keyboard > Language". Then scroll down to until Hebrew is highlighted, click on it, and click "OK". Check the "Left-Alt-Shift" and "enable indicator on taskbar" options, and click "OK". You will be prompted for your Windows Installation CD, and may be required to reboot.

The process for W2000 is similar, but "Language" is "Input Locales", and there are more options. [A variation of] the same process should work with Windows Me or XP.

When the "installation" is completed, you can shift between English and Hebrew by pressing "Left-Alt-Shift" or by clicking the [HE/EN] Icon on the taskbar.

The keyboard installed is the standard "Israeli" keyboard layout, which matches the layout of your IBM Hebrew-English keyboard, and can be used for Yiddish as well. To type nikkudot, press the caps lock key, hold down the shift-key, and type one of the keys on the top row (See http://www.qsm.co.il/Hebrew/wniqud.htm for details). It doesn't take long to memorize which key represents which nikud, so you don't have to refer to the table. Or, you can use "keycaps", or simply write (or print) the information on a strip of tape (or paper) placed above the top row on the keyboard!

This allows you to type Hebrew or Yiddish (with or without nikkudot) from most Windows applications (including MS Word, Outlook Express, Wordpad, etc.) although each application has its own quirks, and the inconsistency is quite annoying.

The fonts created by this input method are "complex fonts" which are encoded as Unicode UTF-8 characters. Theoretically, these fonts should be readable and displayable by any application --- unlike the proprietary fonts used by most Hebrew/Yiddish word processor programs.

Another option is to purchase either the Dagesh Pro or DavkaWriter word processors, which provide full more complete Hebrew and Yiddish language capabilities. It is much easier to enter nikkudot and trop with these word processors, and they have elementary spell checking as well. Then you can convert from their format to HTML for web pages (or importing to other Windows applications). Unfortunately, both word processors are expensive, and have more bugs and poorer support than Microsoft products --- and the fonts are of poorer quality.
 
"I could have done it in a much more complicated fashion", said the Red Queen to Alice [obviously Bill Grates' mentor].
 
-- David ben Yosef Goldin


Back to Top
Notes on YIVO's Yiddish Spelling Conventions

My statement above condemning the khirek-yud places me at odds with those who blindly follow the spelling rules promulgated by the YIVO. I am of the old school (די אַלטע גוואַרדיע) that does not hold YIVO's spelling conventions to be sacrosanct. On my website I have a whole article on this subject. Click here to read the article.

Note also that in the former Soviet Union, thousands (if not hundreds of thousands) of Yiddish books were published using a plain alef instead of a pasekh-alef. Although I personally LIKE the pasekh-alef (I even like the tseyre tsvey-yudn), the fact remains that in the former Soviet Union, YIVO's spelling conventions were NEVER accepted.

Question: Isn't it about time that the YIVO revised its spelling rules and went back to using the Shtumer Alef instead of the khirek-yud?

Leyt mayn meynung iz es sheyn di hekhste tsayt vos di firershaft funem YIVO zol zikh optreysln fun der hashpoe fun di "Vaynraykhistn" un take "mesaken zayn" di "takones fun YIVO" -- eyb nit ingantsn opshafn zey!

Back to Top

Valid HTML 4.01! Made with Nvu