Dear Folks,
Can any one answer this query. I have got it from
one student.
- Original Message -
From: anu_x143
To: [EMAIL PROTECTED]
Sent: Thursday, July 24, 2003 6:34 PM
Subject: my query
"i've some problem in unicode.my problem is, i've a list box(itemsare
indian languages)
I like this idea too.
Not just for multilingual input; for ordinary use as well. I.E.
after pressing the dead key to generate an acute accent, all the
keys which support acutes would be shown as such (e.g. the E would
look like ) until the next key was pressed. This would simplify
life for people
Of course! LCDs!
The trouble with zero-travel keyboards, both the completely horrible (in
my opinion) projection type and the much more interesting TouchStream
type, has been that despite the great configurability, you can't touch
type on them. With LCD keycaps, my dream of using the Dvorak,
On 24/07/2003 23:10, Jony Rosenne wrote:
1. Vav Holam may convey two meanings, either just a vowel or a consonant Vav
with the vowel Holam.
Some typographers differentiate these two meaning, many do not. I don't now
if there is any Masoretic basis for the distinction or if it is late, and
On 24/07/2003 17:09, Chris Jacobs wrote:
Aleph with right holam is not a plain text issue, and thusly not an unicode
issue.
A right holam on an aleph belongs between the aleph and the preceding
consonant.
Indeed, logically though not always typographically.
As far as plain text goes it can be
People using an AZERTY keyboard (French or Belgian) might find it useful to
know of the excellent keyboard layout for polytonique unicode greek
available at
http://club.euronet.be/frederique.bouras/kbdhept.htm
Raymond Mercier
John Hudson quoted and wrote:
But what should be done when meteg is expected to be in the
middle? One
thought was to encode hataf_vowel - CGJ - meteg, but this is
not suitable
if CGJ is not supposed to promote ligation. Perhaps it is
better to note
that with the hataf vowels the
-Original Message-
From: Peter Kirk [mailto:[EMAIL PROTECTED]
Sent: Friday, July 25, 2003 12:56 PM
To: Jony Rosenne
Cc: [EMAIL PROTECTED]
Subject: Re: Hebrew hataf vowels (was: About CGJ)
On 24/07/2003 23:10, Jony Rosenne wrote:
1. Vav Holam may convey two meanings, either
Kenneth Whistler wrote:
Exactly. And frankly, I am finding it difficult to understand
why people are characterizing the CGJ proposal as a kludge
or an ugly hack. It strikes me as a rather elegant way of
resolving the problem -- using existing encoded characters and
existing defined
On 25/07/2003 05:14, Kent Karlsson wrote:
A possible solution to the particular problem at hand that
hasn't yet been mentioned (that I've noticed), is to use the
already encoded vowel characters for the most part (also
for biblical texts), but use new biblical vowels only for the
occurrences
On 25/07/2003 06:23, Jony Rosenne wrote:
What was the consensus in the SII on how the holam vav vowel
should be
encoded? And what is the normal practice in Israel and for pointed
modern Hebrew? Is that holam encoded after the vav or before it?
After.
And John Hudson encodes before.
As acomment on this, I dont think LCDs are the way to go.
eInk may be more interesting, though it would require sufficiently
robust and transparent coating. (Perhaps AlO?)
-JimC
Aluminum oxide, if your MUA is not utf-8 friendly :)
Pim == Pim Blokland [EMAIL PROTECTED] writes:
Pim I'm not sure if the cost would be too high, because this would
Pim mean manufacturers only need to build one model of keyboard
Pim instead of all those different ones for different countries.
More precisely, it means only one model of keyCAP for
- Original Message -
From: Kent Karlsson [EMAIL PROTECTED]
I find the entire idea with CGJ (for any use) a kludge...
A possible solution to the particular problem at hand that
hasn't yet been mentioned (that I've noticed), is to use the
already encoded vowel characters for the most
Changing (and worse, recycling) 3166 Alpha-2 codes puts us in mind of
all sorts of database-related disasters, but that's not all. Think of:
. Top-level Internet domains. Imagine the possibilities for spoofing
during the transition period.
. Postal-code country prefixes, which are
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peter Kirk
Sent: Friday, July 25, 2003 3:30 PM
To: [EMAIL PROTECTED]
Subject: SPAM: Re: Hebrew hataf vowels (was: About CGJ)
On 25/07/2003 06:23, Jony Rosenne wrote:
What was the consensus in
I think I have seen such a keyboard at NASA around 1976, but maybe it was
only a concept.
Jony
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of James H. Cloos Jr.
Sent: Friday, July 25, 2003 3:44 PM
To: Thomas M. Widmann
Cc: unicode
Subject: SPAM:
I like this idea too.
Not just for multilingual input; for ordinary use as well. I.E.
after pressing the dead key to generate an acute accent, all the
keys which support acutes would be shown as such (e.g. the E would
look like É) until the next key was pressed. This would simplify
life
On 25/07/2003 11:01, Jony Rosenne wrote:
But consider the seventh word in Jeremiah 52:19, which, as you would
encode it, ends qof hiriq yod zaqef-qatan vav holam tav.
(This hiriq yod
vav holam sequence is in fact unique in the WTS Bible text.) In this
case, is the yod a consonant followed by
To: [EMAIL PROTECTED]
Subject: RE: Yerushala(y)im - or Biblical Hebrew
Kent asserted in response to my comment:
Exactly. And frankly, I am finding it difficult to understand
why people are characterizing the CGJ proposal as a kludge
or an ugly hack.
I find the entire idea with CGJ (for
Tedd Hopp asked:
Tell me if I'm wrong please, but isn't moving characters (however
it's disguised) as much of a violation of the stability policy as is
changing combining classes of the existing vowels?
You're not wrong. It is a violation of the stability policy.
The Hebrew vowels interact
On 25/07/2003 11:44, Kenneth Whistler wrote:
I have always preferred the concept of an on-screen virtual
keyboard that mirrors the current state of a software-programmable
keyboard, while otherwise just keeping current, cheap
hardware that is (usually) optimized for fast touch typing.
Keyman 6
Kenneth Whistler scripsit:
I have always preferred the concept of an on-screen virtual
keyboard that mirrors the current state of a software-programmable
keyboard, while otherwise just keeping current, cheap
hardware that is (usually) optimized for fast touch typing.
Me too. It was my
Frank da Cruz wrote:
Changing (and worse, recycling) 3166 Alpha-2 codes puts us in mind of
all sorts of database-related disasters, but that's not all. Think of:
. Top-level Internet domains. Imagine the possibilities for spoofing
during the transition period.
. Postal-code country
The Unicode Technical Committee has posted a new issue for public review
and comment. Details are on the following web page:
http://www.unicode.org/review/
Review periods for the new item closes on August 18, 2003.
Please see the page for links to discussion and relevant documents.
It appears my response from this morning didn't make it to the list, so
here it is again. I apologize if this results in a duplicate.
Alex.
Since I did look into all the issues before that are mentioned in this
thread, let me respond to them.
The applications of dynamic keycaps are pretty
At 15:46 -0400 2003-07-25, John Cowan wrote:
When the United Kingdom hands back Northern Ireland to Ireland
in 2052, then obviously the numeric codes of both countries will have to
change, but not the codes for the names.
Presumably the name of the U.K. would change, however.
Why? It would be
On 25/07/2003 12:34, Kenneth Whistler wrote:
Tedd Hopp asked:
Tell me if I'm wrong please, but isn't moving characters (however
it's disguised) as much of a violation of the stability policy as is
changing combining classes of the existing vowels?
You're not wrong. It is a violation of
I think it really depends on how people work. I am using an on-screen
display frequently, but cannot afford to have it up all the time since it
eats up screen real estate and also won't travel when switching virtual
desktops/workspaces. I agree that these are fairly minor implementation
issues
On 25/07/2003 13:03, Rick McGowan wrote:
The Unicode Technical Committee has posted a new issue for public review
and comment. Details are on the following web page:
http://www.unicode.org/review/
Review periods for the new item closes on August 18, 2003.
Please see the page for links to
On 25/07/2003 13:28, Michael Everson wrote:
At 15:46 -0400 2003-07-25, John Cowan wrote:
When the United Kingdom hands back Northern Ireland to Ireland
in 2052, then obviously the numeric codes of both countries will
have to
change, but not the codes for the names.
Presumably the name of
Thomas,
It's all well and good to change the keyboard layout, but it can be
confusing if it becomes too different from the physical keyboard
(esp. if one has to type something in a totally different alphabet).
Now, if anybody would manifacture keyboards with tiny LCD displays on
each key,
Thanks, Ken. That sensitizes me to some of the problems involved with
breaking stability.
If I recall correctly, the suggestion for using CGJ for yerushala(y)im was
to encode it as: ...lamed, patah, cgj, hiriq, final mem. Also, I seem to
recall that this gave some people heartburn because CGJ was
Alex Bochannek wrote:
I think it really depends on how people work. I am using an on-screen
display frequently, but cannot afford to have it up all the time since it
eats up screen real estate and also won't travel when switching virtual
desktops/workspaces. I agree that these are fairly
Ted continued:
If I recall correctly, the suggestion for using CGJ for yerushala(y)im was
to encode it as: ...lamed, patah, cgj, hiriq, final mem. Also, I seem to
recall that this gave some people heartburn because CGJ was not intended to
join two combining characters. What if this case were
Peter wrote:
One thought: Ken has suggested CGJ be used to prevent reordering of
combining marks in fixed position classes such as the Hebrew vowels, and
also suggested that users should not need to be aware of the need for CGJ
for this purpose but that software can be implemented in a way
PASEQ is a word separator.
SOF PASUQ is used as the equivalent of a period also in other writings, such
as prayer books.
Jony
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peter Kirk
Sent: Friday, July 25, 2003 11:04 PM
To: Unicode List
37 matches
Mail list logo
