Greek and Hebrew in Google Docs and Windows Live SkyDrive

I copied/pasted these texts here, but one can type in Hebrew and Greek with the use of an Unicode keyboard AND you must the Tahoma font to see acceptable results onscreen. Using another font will result in box characters, but do note that the correct Unicode is actually in place. I.e., if you copy/paste your strange looking text into a Word document and then convert the text to a font which includes all the accented characters (such as Cardo), it will all be fine.
The way Hebrew is rendered with Tahoma, the 12pt text isn't too much smaller than the English 12pt. In order to accommodate points and accents which enlarge the font height in Times New Roman Hebrew, the font has to be noticeably smaller than its English counterpart. I increased the size for visibility purposes here.
Note that in Firefox, I have designated Cardo as my default Greek font.
In IE8, I have not changed the default which is Times New Roman.

Windows Live SkyDrive
Firefox 3.5
VIEW	EDIT


Internet Explorer 8
VIEW	EDIT

I'm not quite sure why, but viewing a document in SkyDrive has some font display problems. Once you click to Edit, you can see that it does a better job of figuring out what to do. The differences in the Edit mode between Firefox and IE8 are largely due to the fact that I have my default Greek font in FF set to Cardo. It's set to the default TimesNewRoman in IE8. In both browsers, TimesNewRoman doesn't have a full set of accented Greek characters, so it automatically replaces those characters with the Tahoma font. (If you look closely, you can see that is the case in TNR at 12pt, but it is quite clear w/ TNR at 14pt.)

Open and Edit in MSWord (2007) from IE8	Copy into MSWord (2007) from IE8

Note that the option to open and edit an online document in SkyDrive in MSWord on your computer requires that you be running it in IE8.
Wondering about all those boxes when you open the file in MSWord? Have no fear. It's just that the fonts don't have those characters, but the Unicode coding is correct. So, you can simply apply a font like Cardo, and all the text will display correctly.
In the right hand box, the last 3 lines are added to show the Cardo font.

Note that Google Docs does not offer Calibri as a font option and so changes it to Arial when copy/pasted in.

In FF, Times New Roman actually looks fine at 12pt, but that's because it is using the Cardo font. At 14pt, it can be clearly seen that the accented characters are substitutes for where TimesNewRoman is lacking, and the differences between Cardo and Times New Roman are more evident. A similar situation would apply with Garamond, but Cardo shares a similar x-height with Garamond and thus looks better.
GoogleDocs does not offer Calibri as an option, and when I copied the text in, it converted the Calibri to Arial.