From: Kenneth Whistler [EMAIL PROTECTED]
On the other hand, for many English speakers, RSVP is simply
learned as an unanalyzed verb, pronounced aressveepee, meaning
send a response to this message. And to castigate such speakers
for politely prepending a please to that verb is a little
too
From: Stefan Persson [EMAIL PROTECTED]
I haven't used M$ IE for many years, though, and my
memory might be wrong.
Blinded by the misspelling of the product name, maybe? :-)
See http://msdn.microsoft.com/msdnmag/issues/0700/localize/ and the section
entitled Choosing Character Sets for info on
This is JScrript tags in HTML -- client side script.
I do not if other browsers have solutions for this problem?
Michael
- Original Message -
From: Christopher Fynn [EMAIL PROTECTED]
Cc: Michael (michka) Kaplan [EMAIL PROTECTED]; Unicode List
[EMAIL PROTECTED]
Sent: Sunday, November 21
From: kefas [EMAIL PROTECTED]
That is easily done by assigning the U-codes to some
keys on the keyboard, but I dont know how to combine
this with the pressing and releasing of CAPS.
MSKBLC.exe , keyboard-layout-creator, does not allow
for that.
Hmmm actually, if one puts the alternate
Not really a Unicode issue
And not really a bug. Whether one calls the first item #0 or #1 is a
regional or technical matter that is honestly somethind that does not
matter. International standards (like 8859), football fans (we're #!!),
and elevators (floor 1 in e.g. the US, floor 0 in e.g.
From: John Cowan [EMAIL PROTECTED]
http://www.livejournal.com/users/gwalla/39856.html is a page about
(and a link to) a truly excellent Windows keyboard driver that
provides full access to the Latin-1 range but is completely compatible
with the US-ASCII keyboard except for AltGr (the right
From: Peter Kirk [EMAIL PROTECTED]
But Kaplan is referring to something quite different, optionally
ignoring diacritics in search operations. This is indeed desirable, so
that a single search can match both Dvorak and Dvok for example, and
so that the one doing the search does not need to
From: Michael Everson [EMAIL PROTECTED]
I think it's stupid (in general) to argue for stripping a letter of
diacritics. If a reader is ignorant of their meaning, that can be
cured. But if they are meaningful, stripping them is just misspelling
the words they belong to. Why would anyone want
From: Michael Everson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 5:35 AM
Subject: Re: Proposal to encode dominoes and other game symbols
At 13:09 +0100 2004-05-26, Michael Everson wrote:
Just because someone hasn't put them on a web page (in a clumsy
graphic) yet
Fix the typo and the kingdom shall be your bounty
MichKa
P.S. Hint: the subject is smarter than the body.
- Original Message -
From: Mahesh T. Pai [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, May 20, 2004 7:49 PM
Subject: Re: ISO 15924
Michael Everson said on Fri, May 21,
I would respecfully suggest that Dr. Stephen A. Kaufman will need to come up
with a more convincing or (and probably and) professional argument than this
one if he wants it to be taken seriously by people who have a very good
understanding of both Unicode and glyphs, and who further have a serious
From: Philippe Verdy [EMAIL PROTECTED]
And my comment here was not about Microsoft should manage its business
snip the rest
Its still offtopic. Please take it to alt.microsoft.sucks or whatever
other forum you feel might be appropriate. :-)
Once a thread goes bad it is hard to convert it back
the codepage warnings in the View|Options dialog.
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies
- Original Message -
From: African Oracle [EMAIL PROTECTED]
To: Michael (michka) Kaplan [EMAIL PROTECTED]; Unicode List
[EMAIL PROTECTED]
Sent
From: Michael Everson [EMAIL PROTECTED]
At 08:49 -0700 2004-04-25, Mark Davis wrote:
There is a different committee mailing list than the one for the UTC.
However,
for the public [EMAIL PROTECTED] list it didn't seem worth having
separate
public list yet. (After all, much of the material on
If the officers believw that rather than the UTC that a new committee is
needed to govern the repository, then it stands to reason that the Unicode
List is the wrong place for locales a separate list for discussions
related to that standard is the most sensible approach.
MichKa [MS]
NLS
From: Marion Gunn [EMAIL PROTECTED]
Irish in Roman script is written i with dot above, Irish in traditional
script is written i without dot above. The current flooding of our local
advertising and publishing markets by various non-native uncial fonts to
write our language goes against
This is one of those really hard to define questions, given how many pieces
actually define what gets bundled under the term Windows. The KB article
is not being entirely fair by taking the lowest level that exists and
assuming that the entire platform must be designed that way. Given that core
From: Antoine Leca [EMAIL PROTECTED]
Well, I do not believe this is the most adequate place to discuss this,
For what it is worth, I agree with you on that point. :-)
Now, the file in XP is still exactly 262144 bytes in size. To me, this is
evidence that only the BMP characters did receive
From: Patrick Andries [EMAIL PROTECTED]
[PA] Yes, the GUI tool is very nice. So easy to use in theory that I
don't understand why it is only available in English (i.e. one does not
need to be a techie and thus know English to be able or want to use
this tool).
Well, the tool is localizable,
From: Patrick Andries [EMAIL PROTECTED]
I have the same question for MS SQL Server 2000...
Similar answer to the one Chris gave for Word, though with a slightly older
version of the Windows sort tables
Finally, I would like to know if it is possible for a user to add
an
Not really a Unicode question, but
For just adding keyboards, you will likely be able to more easily use the
LoadKeyboardLayout API. To change individual settings within a chosen user
locale, you can use the SetLocaleInfo API.
For other settings, see
From: Philippe Verdy [EMAIL PROTECTED]
Exactly. However the conversion to UTF-8 from UTF-16 (the Windows
WideChar
encoding used in the Win32 Unicode API) is supported natively in
MultibyteToWideChar() as if it was a SBCD/DBCS character set, even on
Windows 95.
This is incorrect. UTF-8
From: Philippe Verdy [EMAIL PROTECTED]
From: Michael (michka) Kaplan [EMAIL PROTECTED]
This is incorrect. UTF-8 support did not exist until Win98 for the Win9x
family, and did not exist until NT4 for the WinNT family.
Even after system updates?
Even after system updates. The support does
From: Michael Everson [EMAIL PROTECTED]
At 09:03 -0800 2004-01-03, Peter Kirk wrote:
But in the light of naming errors like this one implementers should
be advised not to use character names, because they are not reliably
helpful.
I wouldn't say that. It would better to advise them, as we
From: Doug Ewell [EMAIL PROTECTED]
Michael is right, of course, that the differences between keyboards
amount to more than just the basic layout and Shift and AltGr keys.
There are custom shifting keys, dead keys, and unusual uses of Caps
Lock, not to mention Far Eastern IMEs. But I don't
From: Adam Twardoch [EMAIL PROTECTED]
I agree with Michael that the simplistic approach I have envisioned would
be
rather incomplete -- I'm willing to accept that limitation. I am aware of
many issues involving IMEs, chaining dead keys etc. I would be willing
to
leave them out of the scope,
Such a format for Windows would be quite inadequate since it is missing many
things, such as:
1) The version of Windows in which it first shipped (there were minor
differences in what was in 9x vs. NT, and on NT some characters were added
to keyboards in later versions).
2) The fact that many
From: Philippe Verdy [EMAIL PROTECTED]
If the intent is to display in a user interface which keystroke the user
must press to create a character sequence it can be useful to know the
character generated in the default state without modifiers (or the
character
generated in CAPSLOCK mode).
I would have to say (as someone who is presenting at both of them!) that it
really depends on the platform upon which you are developing and to some
extent how much you really feel you need to know about particular topics.
The GDDC will cover more info about Microsoft technologies than the IUC
From: Carl W. Brown [EMAIL PROTECTED]
I use Microsoft WEFT to embed fonts. I have had complaints that it does
not
run on non-Windows platforms but then Bitstream does not either. The
problem with Bitstream is that it requires an active-x control to be
installed and many people will not do
You are correct, Mark. I could probably intrigue people with tales of
attempts at file systems that change their rules based on locale settings,
but mostly it would just cause nightmares for anyone who understood what a
bad idea that would be. Suffice to day that Windows will not boot if I !=
i in
I know I'll end up regretting this
From: Philippe Verdy [EMAIL PROTECTED]
That far? So why isn't there correct support of UTF-16 on Windows
95OSR2, 98, 98SE and ME (notably for their FAT32 filesystem)? I can
understand it for Windows 95 and 95OSR1 as they were designed before,
and may be
I also sincrely doubt that MSKLC will create keyboards that will work on a
CE device, to tell you the truth. Maybe they do, but they have never been
tested there and I would be surprised if they had no problems (never forget
the First Tester's Axiom!).
MichKa [MS]
NLS Collation/Locale/Keyboard
From: Frank Yung-Fong Tang [EMAIL PROTECTED]
so.. in summary, how is your concusion about the quality of GB18030
support on IE6/Win2K ? If you run the same test on Mozilla / Netscape
7.0, what is your conclusion about that quality of support?
In Summary?
Well, in summry, I fail to see how
From: Patrick Andries [EMAIL PROTECTED]
I was enquiring about ways of using Unicode on
a popular platform (Windows).
I'm terribly sorry to enquire about a practical issue.
No need to apologize. How about a practical answer? :-)
If you install the Chinese (Traditional) - Unicode IME as an
From: [EMAIL PROTECTED]
input of this interesting IME that is expecting UTF-16 code units ...
Oh, you did mention that, didn't you? I wonder if surrogate
pairs will work here...
They will. Its fairly cool, if you ask me.
Ignore Philippe's ramblings here, they are offtopic and hav nothing
From: Philippe Verdy [EMAIL PROTECTED]
May be that's something to suggest to Microsoft for inclusion in a future
version of its wonderful MSKLB tool,
You mean MSKLC? I hope the B in your exposition stands for Bodacious or
something
which works great to create keyboard
drivers for
From: Peter Kirk [EMAIL PROTECTED]
On 15/11/2003 09:08, Philippe Verdy wrote:
... (also in Hebrew and Arabic
for vowel points and marks which should better be entered with a logical
order after the base letter, even if they produce combining sequences to
the
application through the WM_CHAR
From: Patrick Andries [EMAIL PROTECTED]
I would like to input arbitrary hexadecimal Unicode values in an
application (XMetal) which does
not seem to use the RichEdit control.
See my other post for the answer to this question.
Unfortunately, I don't seem to be able to key in a large decimal
From: Philippe Verdy [EMAIL PROTECTED]
As far as I know, an application has little control on the subset of
character it can accept from an IME, or keyboard driver, and if some
characters in the generated combining sequence are ignored, and some other
are accepted, it creates a new sequence
From: Toyin Ryan [EMAIL PROTECTED]
I am trying to type the 'hacek' diacritic mark above 'c' and 'e' and
also a straight line (not a tilda) above characters too.
The hacek is a diacritic mark used in the Czech and Lithuanian
languages. It looks like an upside-down circumflex or a pointed
These collation tables have one and only one of the following two problems:
A) If these are intended to be language-specific tailorings then a strong
warning about the linguistic inapplicabilty needs to be added, since the
data is actually incorrect for the use of most of these scripts.
B) If
From: John Cowan [EMAIL PROTECTED]
If you have ever wondered if you are in hell, John Cowan
it has been said, then you are on a well-traveled
http://www.ccil.org/~cowan
road of spiritual inquiry. If you are absolutely
http://www.reutershealth.com
sure you are in hell, however, then
From: Peter Kirk [EMAIL PROTECTED]
On 24/07/2003 04:33, [EMAIL PROTECTED] wrote:
How to map the code values of the key boards with the code values for
the alphabet given with different Code pages of any scripts such as
devanagari, gujarati etc.
If you are using Windows, you might
From: Michael Everson [EMAIL PROTECTED]
I don't know what the i in
the iLifestyle suite (iChat, iPhoto, iBook,
iThis, iThat) means.
For developers, a capital I usually means interface -- in code certainly
but then often applied in life as only geeks can do. I have fond memories of
not too
Well, I thought Arial Unicode MS is a little pricey for just putting it
anywhere? I may be wrong here (and I have no idea how much is costs,
really), but the huge size compared to megafonts like Code2000, which is
based in part on the rich Arial typeface heritage, also makes it a font of
some
A question mark is a sign of a bad conversion from Unicode (to a code page
that did not contain the character). This would likely happen on the Mac too
rather than the Last Resort font, wouldn't it?
On Windows, the cannot find a font for it situation is the NULL glyph. The
Last Resort font is
Subject: Re: About the European MES-2 subset
At 15:45 -0700 2003-07-18, Michael \(michka\) Kaplan wrote:
A question mark is a sign of a bad conversion from Unicode (to a code
page
that did not contain the character). This would likely happen on the Mac
too
rather than the Last Resort font, wouldn't
From: Doug Ewell [EMAIL PROTECTED]
Of course, if this is your belief, you are not alone. The ISO 3166
Maintenance Agency has now spent five months debating and voting on the
question of what new codes for Serbia and Montenegro should replace
YU and YUG used for Yugoslavia, while some people
Let me add that this was the case recently for Hebrew (to mention on
example). So it is certainly not impossible.
But we have enough real work to do that we should do our best to veer from
the theoretical. :-)
MichKa
- Original Message -
From: Michael (michka) Kaplan [EMAIL PROTECTED
Thank you for [indirectly] making my point for me. I am saying that if
someone has an issue that *does* make a difference then they should bring it
up.
Otherwise, I say that a difference that makes no difference, make no
difference. And we can move on to actual problems. :-)
MichKa
-
(reminded of a South Park Episode... the spelling bee in Hooked on Monkey
Phonics)
excerpt:
-
MAYOR: Here we go - kroxldyphivc.
KYLE: What?!?
MAYOR: kroxldyphivc.
KYLE: Definition?
MAYOR: Something which has a kroxldyph-like quality.
KYLE: Uh, could you use it in a
- Original Message -
From: Philippe Verdy [EMAIL PROTECTED]
snip Philippe's message
This is an equal opportunity forum intended for discussion of issues
relative to Unicode, an industrial consortium that includes (among many
others) the companies you are talking about. Excessive
From: William Overington [EMAIL PROTECTED]
It certainly is exciting!
Whoosh!
MichKa
Well, at least I can remember the date with these types of reminders.
:-)
MichKa
- Original Message -
From: Thomas Milo [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Michael Everson
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, April 01, 2003 8:39 AM
Subject: Re:
From: Kenneth Whistler [EMAIL PROTECTED]
and any such sequences as quatrillo con coma or tz which
need to be handled as units simply get contractions defined
for them in the collation element weighting tables.
Or other, analogous methods to obtain the same results (for products
that do not
You can remove a per-file prefix, certainly. This would make sense.
But if you do not, what is the harm of a character that you cannot see
and which does not even have width or cause line breaking behavior?
Realistically, what would the problem be?
MichKa
- Original Message -
From:
with their repro
scenario, if they have one (I don't think they do, as the code on the
NT platforms does not have this functionality, even as an option).
MichKa
- Original Message -
From: Yung-Fong Tang [EMAIL PROTECTED]
To: Michael (michka) Kaplan [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent
From: Yung-Fong Tang [EMAIL PROTECTED]
One of my colleague ask me this question.
In the interests of completeness
The function that does the type of sorting your colleague noted is
StrCmpLogicalW in shlwapi.dll, version 5.5 and later. See the
following link for more information (all on one
LCMapString does not do the reported behavior either. ComparesString
and LCMapString are based on the same data and return the same
results.
Your colleague is mistaken.
MichKa
- Original Message -
From: Yung-Fong Tang [EMAIL PROTECTED]
To: Michael (michka) Kaplan [EMAIL PROTECTED]
Cc
From: Dominikus Scherkl [EMAIL PROTECTED]
Yeah! One of the best features of XP - finaly I don't need to
insert leading zeroes to filenames to get them in the proper order
(even 9a is sorted before 10).
Anyone know is there a way to make them sort in the same
order?
Why should anybody
From: Doug Ewell [EMAIL PROTECTED]
Note that I'm speaking in terms of programmable sorting. I really
don't
care how filenames in Windows Explorer are sorted.
Sigh I wonder if my mail made it to the list?
Doug,
Frank was wrong (or arther his colleague was wrong). CompareString
does not
From: Yung-Fong Tang [EMAIL PROTECTED]
One of my colleague ask me this question.
Not much to do with Unicode, though. Is it?
We use LCMapStringW on WinXP and LCMapStringA
on Win98 (by using LCMAP_SORTKEY ). And we got
different sorting order for the following
Example of message list
From: Mark Davis [EMAIL PROTECTED]
I agree with Kent that it is somewhat less robust to simply remove
ill-formed sequences, since it removes any indication that the data
was
corrupted.
Nice that the API gives one the option to choose, huh? ;-)
The notion of continuing (even if one is
Well, DBCS means double byte character set and thus it is always two
bytes. But its a theoretical definition since there are no actual DBCS
code pages -- all of the ones that exist are MBCS (multibyte character
set) since they support both one-byte and two-byte characters.
There are standards
]
Sent: Sunday, February 16, 2003 11:20 AM
Subject: Re: BOM's at Beginning of Web Pages?
At 19:10 -0800 2003-02-15, Michael \(michka\) Kaplan wrote:±±
Of course if I had a penny for every byte that has been used
discussing these three bytes sometimes found at the beginning of a
UTF-8 document
From: Roozbeh Pournader [EMAIL PROTECTED]
PS: UTF-16 is an exception to that, since the BOM is not part of the
document and should be removed for processing.
And to whatever extent UTF-8 has a BOM, it would fall under the same
category. Certainly that is how processors that understand the
From: Roozbeh Pournader [EMAIL PROTECTED]
I agree, but the Unicode web age is the buggy thing here, not the
specific
browser that was reported earlier to have a problem with it. That's
all my
point. One should fix the Unicode web page instead of that browser.
If the problem was indeed due to
From: [EMAIL PROTECTED]
1) Sorting Test
a) include a list of un-ordered strings.
b) follow that with the same list, ordered properly.
GB18030 does not define a specific standard for sorting (as far as I know, neither
does GB13000). It
is an encoding standard.
Since
Well, that opening byte is either a BOM or its ZWNBSP. Either way its something you
would not really
see if the either the app or the rendering engine understand Unicode
MichKa
- Original Message -
From: Michael Everson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, January
From: Michael Everson [EMAIL PROTECTED]
At 13:53 -0800 2002-12-17, Kenneth Whistler wrote:
The question for Unicoders is whether introduction of significant
normalization problems into Tibetan (for everyone) is a worthwhile
tradeoff
for this claimed legacy ease of transition for one system,
This is an expected behavior. Ii has to do with the Endian-ness of the
processor on which you are running. From the glossary
(http://www.unicode.org/glossary/):
Little-endian. A computer architecture that stores multiple-byte numerical
values with the least significant byte (LSB) values first.
Hello Raymond,
If you have Chinese Office XP and the font in question (Simsun Founder
Extended), then you already have all of the contents of
http://i18nwithvb.com/surrogate_ime/ , in Chinese -- the translation on the
web site is just a handy adjunct for people who do not understand Chinese.
:-)
From: Carl W. Brown [EMAIL PROTECTED]
Other companies
like Microsoft took a very big gamble and implemented the code for
surrogate
support into Windows 2000 based on early drafts of the Unicode standard.
If
they had not done it this way or had guessed wrong they might not even
have
support
This person has installed an application that is attempting to use the
Unicode version of ATL.DLL on Win9x, which will fail (this is expected).
This error would not be related to the freeze (it is code that causes the
load to fail right after clicking OK to the messagebox); the freeze might
be
From: Michael Everson [EMAIL PROTECTED]
At 12:10 -0700 2002-11-11, John Hudson wrote:
Many thanks to the various people who recommended Michael Kaplan's
calculator at http://trigeminal.com/16to32AndBack.asp
This is excellent and solves my problem.
Glad you like it, John -- I am sure James
From: John Hudson [EMAIL PROTECTED]
At 13:50 11/11/2002, Michael Everson wrote:
By the way MichKa if you make the boxes a bit wider the whole string of
numbers would display.
I noticed the same problem in Opera. It's okay in IE.
Ah, if I called *that* by design, someone might accuse me of
From: Joseph Boyle [EMAIL PROTECTED]
Thanks for the dozens of responses discussing consumers' behavior on UTF-8
BOM. This is actually not what I'm concerned with, as I have to take it as
a
given that there is both software that wants UTF-8 BOM and software that
doesn't want it.
Could we
From: Joseph Boyle [EMAIL PROTECTED]
Joesph,
Software currently under development could use the identifiers for
choosing
whether to require or emit BOM, like the file requirements checker I have
to
write, and ICU/uconv.
Lets separate that into the two issuse it represents:
EMITTING: They
From: Joseph Boyle [EMAIL PROTECTED]
No, the notation to say BOM required (report any files without BOM),
BOM
not allowed (report any files with BOM), or BOM optional (only report
files if they are not valid UTF-8 at all), for a given file type.
Well, yes. If you wanted to avoid making it
From: [EMAIL PROTECTED]
In particular, I'm thinking of a situation about a year and a half ago
(IIRC) in which Michael (and I and others) were strongly opposed to a
suggestion that the Unicode Consortium should document a certain variation
(perversion, some would say) of one of the Unicode
From: Mark Davis [EMAIL PROTECTED]
Ironic that for the purpose of dealing with THREE bytes that so many bytes
are being wasted. :-)
Little probability that right double quote would appear at the start of a
document either. Doesn't mean that you are free to delete it (*and* say
that
you are
From: Mark Davis [EMAIL PROTECTED]
That is not sufficient. The first three bytes could represent a real
content
character, ZWNBSP or they could be a BOM. The label doesn't tell you.
There are several problems with this supposition -- most notably the fact
that there are cases that specifically
From: Joseph Boyle [EMAIL PROTECTED]
Type Encoding Comment
.txt UTF-8BOM We want plain text files to have BOM to distinguish
from legacy codepage files
Not really required, but optional -- the perfomance hit of making sure its
valid UTF-8 is pretty minor. But people do open some *huge* text
From: Joseph Boyle [EMAIL PROTECTED]
These are listed as examples to demonstrate the idea of a configuration
file
listing encoding constraints. The fact that each constraint is arguable is
a
good reason to make the constraints configurable, and therefore to have
names to distinguish BOM and
is an unrealistic one.
MichKa
- Original Message -
From: Tex Texin [EMAIL PROTECTED]
To: Michael (michka) Kaplan [EMAIL PROTECTED]
Cc: Mark Davis [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Saturday, November 02, 2002 11:08 AM
Subject: Re: Names for UTF-8 with and without BOM
Michael (michka
No links to give, just a note to warn you
that VB itself converts text that it puts into the RichEdit control from Unicode
when it assigns the text.
Technically the control supports Unicode
since its interfaces are Unicode. but this conversion does limit the text that
can be supported.
All this talk about the letter A reminded me of something from Hofstadter:
The problem of intelligence, as I see it is to understand the fluid nature
of mental categories, to understand the invariant cores of percepts such as
your mother’s face, to understand the strangely flexible yet strong
From: nandu patil
I wanted to do all encodings in C++ so i can write a library (DLL) which
will handle all this stuff
Do you need to communicate with other applications that do not support
Unicode? If not, then you have no need to support encodings at all (since
you are using Unicode and you
From: Doug Ewell [EMAIL PROTECTED]
It's too bad you can't see that combination on the
Javascript keyboards at Globaldev.
The use of either CTRL or CTRLSHIFT shift states in Microsoft-supplied
keyboards is very rare. The reason it is rare is that it interferes with
programs that use those
From: Gopal Krishan
In one of my VB project, I'm sending PostMessage API function
to send character of my desired value to control. e.g. If I
need to send character J to the keyboard, I'm using
dim s as Long
s = PostMessage(Text1.hwnd, WM_CHAR, 99, 0)
where 99 is the ASCII value of
Allow us to help you once more:
http://unicode.org/unicode/consortium/distlist.html#3
It contains the info on how to unsubscribe, and if you scroll down a bit it
gives information on what to do if you have problems unsubscribing.
MichKa
- Original Message -
From: Amruthavakkula,
The AscW() function in VB gives the code point of the first character in the
string it is passed (it is basically the inverse of ChrW).
MichKa
- Original Message -
From: Magda Danish (Unicode) [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 03, 2002 10:06 AM
Subject:
Allow us to help you once
more:
http://unicode.org/unicode/consortium/distlist.html#3
(contains the info on how to
unsubscribe)
MichKa
- Original Message -
From:
Jason
To: [EMAIL PROTECTED]
Sent: Thursday, October 03, 2002 8:55
PM
Subject: please unsubsribe me
What scares me was that I puzzled that out almost instantly -- I felt like I
was watching Wheel of Fortune or something. ;-)
MichKa
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Friday, August 30, 2002 9:03 AM
Subject: RE: Romanized Cyrillic
From: Michael Everson [EMAIL PROTECTED]
Only because so few people think that fonts are worth paying for that
people who really OUGHT to be earning their living by making fonts
have to do other things. There's something really wrong with that
model. Isn't there?
Of course, one could also
From: Janusz S. Bie [EMAIL PROTECTED]
The summary is very short: I got *no* answer to my query.
Well, it *is* a question that really has nothing to do with Unicode, a
character encoding standard.
Perhaps some of you may suggest a more responsive forum?
Well, something on topic would likely
From: William Overington [EMAIL PROTECTED]
Could this be discussed at the Unicode Technical Committee
meeting next week please?
whoosh
William,
Please read Ken's message again. He was *talking* about HTML, and pointing
out how all of these things are supported in browsers already.
You will
AFAIK reverse diacritic are unique to French -- of course French is spoken
in a lot of different locales. ;-)
MichKa
- Original Message -
From: Ake Persson [EMAIL PROTECTED]
To: Unicode List [EMAIL PROTECTED]
Sent: Friday, August 09, 2002 3:58 AM
Subject: Backward accent order
The
From: Tex Texin [EMAIL PROTECTED]
Simply throwing out terms and definitions, without
establishing a need and ignoring existing industry terms,
seems to be a self-inflating and glory-seeking action,
rather than a desire to make a helpful contribution.
Just so.
I mention this not as an
1 - 100 of 575 matches
Mail list logo
