RE: Unicode Hebrew proposal: nomenclature..

2003-10-03 Thread Asmus Freytag
At 04:24 PM 10/3/03 -0700, Peter Constable wrote:
> HEBREW BABYLONIAN (SIMPLE) ATNACH

I don't know that parens in names are acceptable. Also, might it make
sense to hyphenate the first two words (the first word in the name of
characters in the Hebrew block doesn't need to be "HEBREW"). Hence,
HEBREW-BABYLONIAN SIMPLE ATNACH. Or, maybe it's just an ordering thing
that's striking me as odd: BABYLONIAN HEBREW SIMPLE ATNACH, perhaps?
Parens may not be used this way.

Names are always adjusted in WG2 and UTC. Just propose a name that gives
your best shot, but never expect it to come out verbatim.
A./



Unicode Public Review Issues update

2003-10-03 Thread Rick McGowan
The Unicode Technical Committee has posted some new issues for public  
review and comment. Details are on the following web page:

http://www.unicode.org/review/

Review periods for the new items close on October 27, 2003.

Please see the page for links to discussion and relevant documents.  
Briefly, the new issues are:


21  Changing U+200B Zero Width Space from Zs to Cf
There have been persistent problems with usage of the U+200B Zero Width  
Space (ZWSP). The function of this character is to allow a line break at  
positions where it normally would not be allowed, and is thus functionally  
a format character with a general category of Cf.

22  Collation Mechanism for Syllabic Scripts
In UTS #10: Unicode Collation Algorithm, there is discussion of a  
mechanism for handling syllabic scripts, notably Korean Hangul. The  
alternative mechanism discussed in the  above-linked document is proposed  
to allow the UCA and tailorings to deal with syllabic collation.

23  Terminal Punctuation Characters
In Unicode 4.0.1, the new property Sentence_Terminal will be added. This  
consists of characters that terminate a sentence; in particular, a sentence  
(unless quoted) should not span one of these characters based on UAX #29  
(Text Boundaries).


If you have comments for official UTC consideration, please post them by  
submitting your comments through our feedback & reporting page:

http://www.unicode.org/reporting.html

If you wish to discuss issues on the Unicode mail list, then please
use the following link to subscribe (if necessary). Please be aware
that discussion comments on the Unicode mail list are not automatically
recorded as input to the UTC. You must use the reporting link above
to generate comments for UTC consideration.

http://www.unicode.org/consortium/distlist.html

Regards,
Rick McGowan
Unicode, Inc.





RE: Unicode Hebrew proposal: nomenclature..

2003-10-03 Thread Peter Constable
Elaine:

> Now NOMENCLATURE
> 1) BLOCK NAME:  does the Hebrew block need to permanently be 
> called Hebrew?  If a better name would be HEBREW-ARAMAIC 
> SQUARE SCRIPT, should that be added as a note?  
> 2) SUB-BLOCK:  can the sub-blocks have a different headers, 
> so they can be called "Tiberian cantillation marks" or 
> "Tiberian vowels"  ??  

Changing the block name would be a problem as there will be existing
systems that assume that name. The sub-block names are simply
informative text in the names list file, though. I would think those
could be changed without creating problems.



> Babylonian  accents, vowels, punctuation
> has ~2 systems with some overlap
> may need "The Mongolian Option"

By "The Mongolian Option", do you mean the use of variation selectors?


> So should the names be.
> 
> HEBREW BABYLONIAN (SIMPLE) ATNACH

I don't know that parens in names are acceptable. Also, might it make
sense to hyphenate the first two words (the first word in the name of
characters in the Hebrew block doesn't need to be "HEBREW"). Hence,
HEBREW-BABYLONIAN SIMPLE ATNACH. Or, maybe it's just an ordering thing
that's striking me as odd: BABYLONIAN HEBREW SIMPLE ATNACH, perhaps?


Peter
 
Peter Constable
Globalization Infrastructure and Font Technologies
Microsoft Windows Division




Article on cuneiform encoding

2003-10-03 Thread dzo
The September 2003 issue of Johns Hopkins Magazine has a nice piece on the 
Initiative for Cuneiform Encoding (ICE) entitled "Clay, Paper, Code." See 
http://www.jhu.edu/%7ejhumag/0903web/code.html

Don Osborn
Bisharat.net








Unicode Hebrew proposal: nomenclature..

2003-10-03 Thread Elaine Keown
 Elaine in Central Texas

Hi,

Ok, font underway, what a relief.  

Now NOMENCLATURE
1) BLOCK NAME:  does the Hebrew block need to
permanently be called Hebrew?  If a better name would
be HEBREW-ARAMAIC SQUARE SCRIPT, should that be added
as a note?  
2) SUB-BLOCK:  can the sub-blocks have a different
headers, so they can be called "Tiberian cantillation
marks" or "Tiberian vowels"  ??  

The current Unicode Hebrew accents and vowels are
supposedly from Tiberias, on the western edge of the
Sea of Galilee  

3) Now, for individual new items.  The new
stuff--which people from Holland started asking for a
year ago, by the way---divides into groups:

Babylonian  accents, vowels, punctuation
has ~2 systems with some overlap
may need "The Mongolian Option"
Palestinian accents, vowels, punctuation
some serious diversity--
also a good candidate for
"The Mongolian Option"
Samaritan*  vowels, punctuation
Epigraphic* punctuation

Starred items come with some built in controversy

So should the names be.

HEBREW BABYLONIAN (SIMPLE) ATNACH
HEBREW BABYLONIAN (SIMPLE) METEG
HEBREW BABYLONIAN (COMPLEX) ATNACH
or
HEBREW SIMPLE BABYLONIAN ATNACH
HEBREW COMPLEX BABYLONIAN ATNACH

For the epigraphy:
HEBREW HIERATIC-EPIGRAPHIC NUMBER FIVE
HEBREW HIERATIC-EPIGRAPHIC NUMBER TEN

And BTW, the new stuff is regional/dialectal,
presume different underlying Hebrew dialects,
with no simple one-to-one mapping between
Tiberian and the other stuff

Please adviseElaine 

__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com



RE: FW: Web Form: Other Question: British pound sign - U+00A3

2003-10-03 Thread Marco Cimarosti
> This (Peter's) answer is, in my understanding, the nearest to the 
> truth.

He made the same assumption I did: you declared that your file was UTF-8 but
actually it wasn't. :-)

> Here is the problem:
> 
> How do I make my keyboard which only produces 8-bit [...]

The keyboard has nothing to do with it. The problem is how you save the
file.

You should see if the "Save as..." command of your text editor (or HTML
authoring tool) has an option like "Save as UTF-8".

If it doesn't, see if your Notepad utility has it option. If it's there (I
don't remember in which version of Windows it was added). You just open your
file and save it selecting "Save as UTF-8".

You can also use an utility to convert the character set. E.g., try the
"iconv.exe" utility from libiconv
(http://sourceforge.net/project/showfiles.php?group_id=23617).

Ciao.
Marco