David Perry wrote:
I have a polytonic keyboard for
Windows that I have created using Keyman, which is not available for the
Mac. I'd be happy to share the documentation for this
Would you be willing to share the Keyman keyboard itself? I just downloaded
Keyman 5.0 after some people on this
Lukas Pietsch wrote:
Would you be willing to share the Keyman keyboard itself? I just downloaded
Keyman 5.0 after some people on this list told us what wonderful things it
can do. But I have no keyboards as yet to go with it.
There are four keyman keyboards available from Tavultesoft's
11digitboy wrote:
If they don't put it in this minute, there is something
WRONG. It is a CURRENCY symbol, for Pete's sake! I
mean, DOLLAR SIGN is not LATIN LETTER S WITH STROKE
And it is *UNI*code
Currency symbols should probably be encoded without
delay, but is this really a
On Tue, 3 Apr 2001, Michael (michka) Kaplan wrote:
Like Doug, I am a little curious as to the decision on where the symbol
would go... would you really want it in the presentation forms that are
merely for backwards compatibility? I think there are two options for
currency symbols:
But
On Wed, 4 Apr 2001 [EMAIL PROTECTED] wrote:
Oh. You didn't tell us whether it goes to the left
or to the right of the digits, did you?
Is this needed in the proposal for the character itself?
--roozbeh
On Tue, 3 Apr 2001 [EMAIL PROTECTED] wrote:
I would think you would want this symbol to be encoded in the Currency
Symbols block (U+20A0 through U+20CF), not in the largely deprecated Arabic
Presentation Forms-A block.
No, I like it in the Arabic Presentation Forms, because it's only a
On Wed, 4 Apr 2001, James Kass wrote:
Currency symbols should probably be encoded without
delay, but is this really a currency symbol? It appears
to be the word "rial" written in Arabic.
I agree. But we need it for round-trip compatiblity with the national
character set. There is a
What is the best "way" to display unicode charatcers on an intel
platform running redhat Linux??? What environment variables (LANGUAGE,
LC_ALLc, etc, etc ) need to be set, what routines should be used
(gettext, iconv, etc, etc), what data type (unsigned short, wchar_t,
etc, etc), and is
On Sun, 25 Mar 2001, James Kass wrote:
The HTML title is displayed in the title bar of the browser.
The font for Windows' title bars can be reset under the
Control Panel. ( [Start] - [Settings] - [Control Panel] -
[Display] - [Appearance] - "Item" and "Font" )
Japanese characters can
Mon, 12 Mar 2001, Parvinder Singh(EHPT) wrote:
Perhaps, you've already solved the problem. Just in case.
I am able to see japanese characters in java applet on Netscape browser 4.7
on NT (while activating Richwin utility on my NT workstation ) but not using
netscape 4.7 on Solaris ? My
Roozbeh Pournander wrote:
You can find a proposal for encoding Iranian Rial sign in Unicode at:
http://developer.sharif.edu/farsiweb/proposal/rial.html
I have two minor points.
First one is about the bidi category. I see that you suggest "AL" (Arabic
Letter):
Recommended
DG What is the best "way" to display unicode charatcers on an intel
DG platform running redhat Linux???
This is an interesting question, and one that is currently the subject of
much debate.
One possible answer is that you need to use version 2.2 or later of
the C library, version 4.0.3 or
Michka You need to stop this sort of nonsense. NEVER has the UTC refused
Michka to look at a proposal, but do you think that somehow procedure is
Michka neglected merely because someone thinks it is an "obvious" point?
I think you are totally over-reacting, Michael. You are reading
James In an older book covering Iranian coinage one can find, in addition
James to "rial", other monetary units like "dinar", "toman", "kran
James (qiran)", etc. The letters forming any of these monetary unit
James words might combine calligraphically to form unique and
Roozbeh,
It doesn't have any international use, because it may be mistaken
by Saudi Arabic Rials or things like that.
I am sorry to see that much of the Arabic support has left out Farsi Urdu
support because of short sightedness. They could have planned ahead and
gone the extra bit to add the
On Wed, 4 Apr 2001, Marco Cimarosti wrote:
But all other characters in general category "Sc" (Currency Symbol) have
bidi category "ET" (European Number Terminator), so I would suggest to
avoid this exception.
This makes sense, because currency symbols are normally associated with
numbers
In a message dated 2001-04-04 3:42:20 Pacific Daylight Time,
[EMAIL PROTECTED] writes:
On Wed, 4 Apr 2001 [EMAIL PROTECTED] wrote:
Oh. You didn't tell us whether it goes to the left
or to the right of the digits, did you?
Is this needed in the proposal for the character itself?
On Wed, 4 Apr 2001, Mark Leisher wrote:
The explanation I was given was that words like "toman" are used more like
"dollar" as opposed to "rial," which is used like "$" (i.e. they are "spelled
out" in a sense).
No. "Toman" is the unofficial name for "10 Rials". Although Rial is the
official
On 04/04/2001 06:06:45 AM unicode-bounce wrote:
My own position in HCI (national governmental body responsible for IT
standards) has been against asking for encoding it. But after I found that
we cannot map a key to a sequence of characters in X, that changed.
So, we have some broken
Might I make one suggestion, to make life easier for recipients of msgs?
(NB. Advice not for list owners, but for users.)
If you wish to make [EMAIL PROTECTED] one recipient among several, would
you mind making it the _first _ recipient? Not doing so had the effect of
force-filing the attached
On 4 Apr 2001, Juliusz Chroboczek wrote:
DG What is the best "way" to display unicode charatcers on an intel
DG platform running redhat Linux???
One possible answer is that you need to use version 2.2 or later of
the C library, version 4.0.3 or later of the XFree86 libraries and
fonts, and
On 04/04/2001 09:34:25 AM unicode-bounce wrote:
Michka You need to stop this sort of nonsense. NEVER has the UTC
refused
Michka to look at a proposal, but do you think that somehow procedure
is
Michka neglected merely because someone thinks it is an "obvious"
point?
I think you are
On Wed, 4 Apr 2001, Roozbeh Pournader wrote:
It won't be. It's nothing more than a rendering of word Rial, sometimes
narrower to fit in one column in fixed-width fonts. It doesn't have any
international use, because it may be mistaken by Saudi Arabic Rials or
things like that.
Well - the $
On Wed, Apr 04, 2001 at 11:03:41AM -0500, [EMAIL PROTECTED] wrote:
Given all those circumstances, maybe not. Would you propose that it have a
canonical or compatibility decomposition? If so, I believe that would be
problematic with respect to stability of normalization forms.
The only thing
Marion,
I find that unless you have a recipient that is not on the Unicode mailing
list it is best to clear all other recipients.
1) It save the person from receiving 2 messages that are duplicates.
2) More important, is that even if you list Unicode first, often the
recipient will receive the
On Wed, 4 Apr 2001 [EMAIL PROTECTED] wrote:
So, we have some broken technology. One way to fix it is to add a
presentation form to Unicode. But isn't there another fix -- to build into
X the ability to map a key to a sequence of characters (which surely would
be useful in other situations)?
D.V. Henkel-Wallace wrote:
At 16:03 2001-04-04 +0200, Marco Cimarosti wrote:
U+20A5 (MILL SIGN): which currency is so worthy to
require a special
symbol for 1/1000?
And it is also true for many currency symbols in other blocks:
U+00A4 (CURRENCY SIGN): who ever used
Stephen:
I have a few points to add to this thread. Most of your questions are about
MacOS X and other OS's, which I can't really speak to, but I do know
something about fonts. Apologies for the delay in replying.
At 06:13 PM 3/16/2001 -0800, Stephen Cremin wrote:
I didn't catch Steve Job's
On Wed, 4 Apr 2001, Michael Everson wrote:
We are not adding characters to the presentation forms. It is likely
that the answer to this proposal will be "please use one-to-many
mapping".
Would you please give me the reference? I once heard this, but after
seeing a new proposal for "Arabic
At 23:27 +0430 2001-04-04, Roozbeh Pournader wrote:
On Wed, 4 Apr 2001, Michael Everson wrote:
We are not adding characters to the presentation forms. It is likely
that the answer to this proposal will be "please use one-to-many
mapping".
Would you please give me the reference?
The
I'm curious if anyone on the list makes use of concordance software and if
so whether there are any Unicode savvy programs that might be recommended?
I've come across a program "WordSmith Tools" from Oxford University Press,
On Wed, 4 Apr 2001, Marco Cimarosti wrote:
U+20A3 (FRENCH FRANC SIGN), U+20A4 (LIRA SIGN), U+20A7 (PESETA
SIGN), U+20AF (DRACHMA SIGN): will disappear next year with euro. Moreover,
Franc and Lira are obsolete symbols ("FF" and "Lit" are now more common).
The drachma sign too; I lived
On Wed, 4 Apr 2001, Carl W. Brown wrote:
I find that unless you have a recipient that is not on the Unicode mailing
list it is best to clear all other recipients.
1) It save the person from receiving 2 messages that are duplicates.
But the person may have been using filters that assign
Roozbeh asked...
Would you please give me the reference? I once heard this, but after
seeing a new proposal for "Arabic Tail Fragment" approved by UTC to be
encoded in "Arabic Presentation Forms-B" block (SC2/WG2 document N2322), I
thought I was wrong.
That proposal and this follow-on
All my unicode messages go to a folder which I read when I have
time. Messages that include me on the header however go to my inbox
so that I see them sooner. So deleting the header names will bury
the messages.
Personally, I don't think we should be tuning headers this much.
There are no
On Wed, 4 Apr 2001, Rick McGowan wrote:
If memory serves me, Unicode and 10646 were already well established
at the time both this standard and the IBM standards containing "tail
fragment" were created (one of the code pages shown in the proposal
even has a Euro sign in it!). At least one
Roozebeh wrote...
Oh, I just found it! It's also encoded as a character in the national
standard ISIRI 2900, dated 1989 (which is a 7-bit character set standard).
I will update the proposal. So you can be sure that you have not disobeyed
the rules ;)
Oh good! Nice bit of research...! This
At 19:50 +0430 2001-04-04, Roozbeh Pournader wrote:
I noted that, but the point is that it's not a unique sign for
international use. It's only a compatiblity character, and it will be used
only in "legacy" Persian texts that are converted from ISIRI 3342 (which
has its own bidi, with only three
On Wed, 4 Apr 2001, Michael Everson wrote:
What's this mean? That in Word 200x, with full Persian support, you
would not use a unitary code point for the rial sign, but instead you
expect users only to type the four letters that make up the word?
No. The keyboard mapper should generate
I have begun using the Unihan tables much more extensively recently.
It troubles me that I keep stumbling over obvious errors and
omissions in the tables, including errors carried over from version 2
to version 3. Can anyone tell me why U+4E00 has neither pronunciation
nor definition given?
On Wednesday, April 4, 2001, at 08:26 PM, Edward Cherlin wrote:
I have begun using the Unihan tables much more extensively recently. It
troubles me that I keep stumbling over obvious errors and omissions in
the tables, including errors carried over from version 2 to version 3.
Can anyone
At 06:09 +0430 2001-04-05, Roozbeh Pournader wrote:
Then your solution is that your round-trip is achieved by a mapping
table that maps one-to-many and many-to-one depending on direction. --
No. Such a mapping table does not respect the difference between the Rial
sign and the string "Reh
42 matches
Mail list logo
