Yung-Fong Tang ftang at netscape dot com wrote:
I remember there were some study to show although UTF-8 encode each
Japanese/Chinese characters in 3 bytes, Japanese/Chinese usually use
LESS characters in writting to communicate information than alphabetic
base langauges.
Any one can point
- Original Message -
From: Dean Snyder [EMAIL PROTECTED]
To: Unicode List [EMAIL PROTECTED]
Sent: Wednesday, March 05, 2003 10:11 PM
Subject: Re: The display of *kholam* on PCs
The case of (written) Yo'MaR is not an exception. The pronunciation is
yomar, the aleph not being pronounced;
Moreover, RA + VIRAMA + YA cannot represent Ra-yaphalaa
as Ra+Virama
is relied upon as being representative of Reph.
For example, in the Indic OpenType secifications, you will
see that a
Ra+Virama is recognised as reph before any other
processing is applied.
If this is the case
Chris Jacobs wrote at 11:54 AM on Thursday, March 6, 2003:
The case of (written) Yo'MaR is not an exception. The pronunciation is
yomar, the aleph not being pronounced; and therefore the KHOLEM is
written after the consonant which directly precedes it in pronunciation.
But not above that
At 06:29 AM 3/6/2003, Dean Snyder wrote:
The most elegant fonts I am aware of for classical Hebrew are produced by
Linguist's Software, http://linguistsoftware.com/. Their HebraicaII is
used by Biblia Hebraica, the Oxford Hebrew Bible Project, and the Dead
Sea Scrolls Project.
The Society of
Yung-Fong Tang wrote:
I remember there were some study to show although UTF-8 encode each
Japanese/Chinese characters in 3 bytes, Japanese/Chinese usually use
LESS characters in writting to communicate information than alphabetic
base langauges.
For my commercial Japanese-to-English translation
- Original Message -
From: Dean Snyder [EMAIL PROTECTED]
To: Unicode List [EMAIL PROTECTED]
Sent: Thursday, March 06, 2003 3:29 PM
Subject: Re: The display of *kholam* on PCs
[ ... ]
Do you have an example of SIN with two dots? I have never seen it. This
would make for ambiguous
John Hudson wrote at 7:31 AM on Thursday, March 6, 2003:
At 06:29 AM 3/6/2003, Dean Snyder wrote:
The most elegant fonts I am aware of for classical Hebrew are produced by
Linguist's Software, http://linguistsoftware.com/. Their HebraicaII is
used by Biblia Hebraica, the Oxford Hebrew Bible
At 09:00 AM 3/6/2003, Dean Snyder wrote:
From http://www.sbl-site.org/Newsletter/12_2002/SBLfont.html:
SBL is pioneering the design of three unicode fonts for Hebrew, Greek,
and Latin, in conjunction with a professional type foundry,
Tiro... SBL and the font foundation will lobby
Chris Jacobs wrote at 6:02 PM on Thursday, March 6, 2003:
BoSeM, is written with a SIN with two dots in
Ben Yehuda's Pocket English-Hebrew Hebrew-English dictionary.
It translates as perfume, spice there.
I see the spelling in Ben Tehuda's is inconsistent.
In the English-Hebrew section under
John Hudson wrote at 11:23 AM on Thursday, March 6, 2003:
At 09:00 AM 3/6/2003, Dean Snyder wrote:
From http://www.sbl-site.org/Newsletter/12_2002/SBLfont.html:
SBL is pioneering the design of three unicode fonts for Hebrew, Greek,
and Latin, in conjunction with a professional
At 12:08 PM 3/6/2003, Dean Snyder wrote:
Has this Windows-only model of distribution been widely aired amongst the
membership of the Society of Biblical Literature? I know that many SBL
scholars use Macintosh computers, and for publishers to accept only
Windows-generated documents seems an
1. open you file with n7 and change the encoding to UTF-8
2. select and copy all the text
3. paste into the first textarea of the attached html file
David Oftedal wrote:
Hello!
Sorry to make this a mass spam, but I need a program to convert UTF-8
to hex sequences. This is useful for embedding
Francois Yergeau wrote:
[EMAIL PROTECTED] wrote:
I remember there were some study to show although UTF-8 encode each
Japanese/Chinese characters in 3 bytes, Japanese/Chinese usually use
LESS characters in writting to communicate information than
alphabetic base langauges.
Francois Yergeau wrote:
http://www.unicode.org/iuc/iuc9/Friday2.html#b3
Reuters Compression Scheme for Unicode (RCSU)
Misha Wolf
Unfortunately, no information about Germany or Japanese. :(
It only have Chinese, Frasi, Urdu, Russian, Arabic, Hindi, Korean ,
Creole, Thai, French, Czech,
thanks, everyone. But I want to point out the punct and itself
should also be consider in your future caculation. Japanese and Chinese,
Thai do not use between word, and Latin based (or Greek,
Koeran,Cyrillic, Arabic, Armenian Georgian, etc) does use and when
used for estimate size,
On Thursday, March 6, 2003, at 01:42 PM, John Hudson wrote:
The problem you have is that Apple, despite being involved with
Unicode from the earliest days, have only recently shipped an OS with
native Unicode text processing available;
This isn't quite true. Unicode support has been available
There is also some information at
http://oss.software.ibm.com/icu/docs/papers/binary_ordered_compression_for_unicode.html#Test_Results
Not sure if this is what you are looking
for.
Regards,
Ram Viswanadha
- Original Message -
From:
Yung-Fong
Tang
To: Francois Yergeau
Thanks for taking the time to prepare a detailed response, John (Jenkins).
You know I'm only hammering in the hope that it will have some effect,
perhaps with those people 'who actually call the shots'.
It is frustrating as a font developer to now be able to do some incredibly
clever things
19 matches
Mail list logo
