Memoji are not merely animated emoji; they are personalized avatars.
As for animated emoji, I expect that the UTC would consider them out-of-scope
for plain text. Note that web pages can already contain animated or moving
elements which cannot be represented in plain text.
> On Jul 9, 2018, a
Maybe we should just throw in the towel and put "DON'T PANIC" on the cover in
big, friendly letters. 😜
macOS (and iOS, for that matter) fully support Extension F provided fonts are
availble. I'm not aware of any work that Apple has done to its fonts for
Extension F support. Indeed, I'm not aware of any publically available fonts
for Extension F but would gladly install one myself if it's availabl
Well, you can go with Venus = white planet, Mercury = grey planet, Uranus =
greenish planet, Neptune = bluish planet, Jupiter = striped planet.
As you say, though, without a context, none of them convey much and Venus, at
least, would just be a circle.
Plus there's the question of the context
𠆩 𠌥 𠍁 𠓼 𠕄 𠝭 𠝹 𠮨 𠮩 𠯋 𠯦 𠯽 𠰋 𠰲 𠱁 𠱂 𠱃 𠱓 𠱘 𠱥 𠱷 𠱸 𠲜 𠳏 𠳕 𠳖 𠴕 𠴰 𠵇 𠵈 𠵉 𠵩 𠵯 𠵼 𠵾 𠵿 𠶜 𠶧 𠶲 𠸉
That is an example of forty Cantonese-specific characters which are not obscene
(that I'm aware of) from Extension B. For the curious, I've appended at the
bottom the full list of 280 for all of Plane 2 which I was
> On Mar 29, 2017, at 4:12 AM, Martin J. Dürst wrote:
>
> Let me start with a short summary of where I think we are at, and how we got
> there.
>
> - The discussion started out with two letters,
> with two letter forms each. There is explicit talk of the
> 40-letter alphabet and glyphs in th
> On Mar 27, 2017, at 9:56 AM, John H. Jenkins wrote:
>
>
>> On Mar 27, 2017, at 2:04 AM, James Kass > <mailto:jameskass...@gmail.com>> wrote:
>>
>>>
>>> If we have any historic metal types, are there
>>> examples where a fon
> On Mar 27, 2017, at 2:04 AM, James Kass wrote:
>
>>
>> If we have any historic metal types, are there
>> examples where a font contains both ligature
>> variants?
>
> Apparently not.
>
> John H. Jenkins mentioned early in this thread that these lig
My own take on this is "absolutely not." This is a font issue, pure and simple.
There is no dispute as to the identity of the characters in question, just
their appearance.
In any event, these two letters were never part of the "standard" Deseret
Alphabet used in printed materials. To the exte
On 2013年4月19日, at 下午1:52, Stephan Stiller wrote:
> But I'd argue that the distance of the information content of such
> low-quality translations to the information content conveyed by correct and
> polished language is often tolerable. Grammar isn't that important for
> getting one's point ac
On 2013年2月1日, at 上午6:07, "Costello, Roger L." wrote:
> So why would one ever generate text in decomposed form (NFD)?
>
The Unihan database is stored in NFD because it makes the regular expressions
used to qualify its contents much, *much* simpler. I imagine that things like
fuzzy text match
wood [2013-01-30 20:17]:
>> A very accessible book on all this is "The Chinese Language: Fact and
>> Fantasy" by John De Francis, published in 1984 by University of Hawaii
>> Press. There is a brief synopsis on Wikipedia
>> http://en.wikipedia.org/wiki/The_Chinese_L
On 2013年1月30日, at 上午4:50, Andreas Stötzner wrote:
> Most ideographs in use are pictographs, for obvious reasons. But it would be
> nice indeed to have ideograms for “thanks”,
謝
> “please”,
請
> “yes”,
對
> “no”,
不
> “perhaps”
許
> – all those common notions which cannot be de-*picted* in
http://xkcd.com/998/
On 2012年12月21日, at 下午4:22, Doug Ewell wrote:
> And as you've no doubt heard to death by now, real Maya don't believe in that
> apocalyptic mumbo-jumbo anyway. Today was a celebration.
>
> --
> Doug Ewell | Thornton, Colorado, USA
> http://www.ewellic.org | @DougEwell
> Fro
I double-checked *very* carefully, and I did't see anything wrong at all. :-)
You got sharp eyes there, Doug.
On 2012年11月28日, at 下午10:58, Doug Ewell wrote:
> John H. Jenkins wrote:
>
>> Or, if one prefers:
>>
>> http://www.井作恆.net/XKCD/1137.html
>
> In al
y browser cannot display it
> and its displays the Punycoded name instead without decoding it.
>
> This is strange because I do have Deseret fonts installed and I can view
> "Unicoded" HTML pages containing Deseret letters.
>
>
> 2012/11/26 John H. Jenkins
>
Or, if one prefers:
http://www.井作恆.net/XKCD/1137.html
On 2012年11月21日, at 上午10:22, Deborah Goldsmith wrote:
>
> http://xkcd.com/1137/
>
> Finally, an xkcd for Unicoders. :-)
>
> Debbie
>
BBEdit and TextWrangler on OS X both do a good job at handling different
encodings.
On 2012年10月3日, at 下午10:58, Stephan Stiller wrote:
> Dear all,
>
> In your experience, what are the best (plaintext) texteditors or word
> processors for Linux / Mac OS X / Windows that have the ability to save
r parts of the documentation.
=
Hoani H. Tinikini
John H. Jenkins
jenk...@apple.com
er semantics—that is, they behave differently. It has nothing to do
with Unicode failing to specify shapes.
=====
Siôn ap-Rhisiart
John H. Jenkins
jenk...@apple.com
ave
currency symbols with decidated code points, other countries will make *new*
currency symbols and demand that *they* get dedicated code points, too. We all
know how unrealistic a scenario *that* is.
=
John H. Jenkins
jenk...@apple.com
entific literature should be considered urgent use,
> in my opinion, and encoded sooner rather than later.
>
=
Hoani H. Tinikini
John H. Jenkins
jenk...@apple.com
.9.1.1.3
>> https://www.google.com/search?q=Danio+ 魚丹
>>
>>
>> Chinese wikipedia: http://zh.wikipedia.org/
>> My blog: http://shizhao.org
>> twitter: https://twitter.com/shizhao
>>
>> [[zh:User:Shizhao]]
>>
>>
=
Hoani H. Tinikini
John H. Jenkins
jenk...@apple.com
l likelihood, "probably just another goddamn fertility
> symbol."
>
> Make that: "currency symbol" and ship it.
>
>
Maybe a "turtle ideograph"?
=
井作恆
John H. Jenkins
jenk...@apple.com
Studies Bibliographer
> East Asian Library and the Gest Collection
> Frist Campus Center, Room 314
> Princeton University
> Princeton, NJ 08544
> United States
=
John H. Jenkins
井作恆
𐐖𐐱𐑌 𐐐. 𐐖𐐩𐑍𐐿𐐮𐑌𐑆
jenk...@apple.com
se to put them into UTR #45. My job is to make
the recommendation.
In either case, somebody other than me (that is, somebody who wants them added
to Unicode) needs to write a document/proposal to the UTC justifying that and
giving the options for encoding.
=
John H. Jenkins
井作恆
𐐖𐐱𐑌 𐐐. 𐐖𐐩𐑍𐐿𐐮𐑌𐑆
jenk...@apple.com
UTC approves a status of "N" (to be encoded), the character would
be included in the UTC's submission to the IRG for Extension F. Work on
Extension F will likely start in 2013.
Andre Schappo 於 2012年1月13日 上午8:36 寫道：
>
> On 12 Jan 2012, at 16:54, John H. Jenkins wrote:
&
/www.unicode.org/pending/proposals.html. For hanzi, the characters need
to be added to UTR #45 first, but I'm going to propose that for both the
upside-down fuk1—er, fu, and the upside-down chun, since they have been
discussed. UTR #45 lets us track such discussions.
=
井作恆
John H. Jenkins
jenk...@apple.com
There are really three choices:
1) Don't encode it at all and rely on higher-level protocols to display it.
(After all, it's only used in specialized contexts and does not have a distinct
meaning or pronunciation from the regular 福.)
2) Use a registered ideographic variation sequence to suppor
tility that efforts to get it implemented as part of a
plain-text standard seem pretty quixotic to me.
(And before anybody accuses me of being overly cynical, I should point out that
I'm probably the person putting in the greatest effort to get the Deseret
Alphabet to be actually *used*. How quixotic is *that*?)
=
井作恆
John H. Jenkins
jenk...@apple.com
Andrew West 於 2011年10月20日 上午3:25 寫道：
> On 19 October 2011 18:41, John H. Jenkins wrote:
>>
>> U+613F kDefinition (variant/simplification of U+9858 願) desire, want, wish;
>> (archaic) prudent, cautious
>> U+613F kSemanticVariant U+9858> U+613F kSpecialized
t who can make the change. When you do so, *please* include a
source for your information. We get all kinds of offered corrections to the
Unihan data which we can't use because there's no authoritative source.
=
井作恆
John H. Jenkins
jenk...@apple.com
This is a known (and, alas, long-standing) problem. We really do intend to get
it fixed, but it's impossible to say when.
=
John H. Jenkins
jenk...@apple.com
standard yet, and it's subject to change,
but it is a well-defined set of interest to people who are tracking IRG work.
=
Siôn ap-Rhisiart
John H. Jenkins
jenk...@apple.com
what for? Most of
> them i never use.
> There must be a simpler system, not so many aprior data for it work.
>
> 2011/9/13, John H. Jenkins :
>>
>> QSJN 4 UKR 於 2011年9月12日 下午9:06 寫道：
>>
>>> I know it is sacred cow, but let me just ask, how do you people think.
absolutely must be done using a higher-level
protocol to handle all the details.
There are occasionally suggestions that positioning controls be added to plain
text in Unicode, but so far the UTC has felt that the benefits are too marginal
to overcome its reasons for having left them out in the first place.
=
Hoani H. Tinikini
John H. Jenkins
jenk...@apple.com
and often very embarrassing—but so long as Unicode does its
intended job and makes it possible for people to represent texts written in the
various languages it covers, it's something we just have to live with.
See also <http://www.unicode.org/faq/basic_q.html#4>.
=====
Siôn ap-Rhi
bleedin' choir invisible. This is an
ex-possibility.
And even if that *weren't* true, there are nowhere *near* enough kanji to have
a serious impact on Ken's analysis.
Richard Wordingham 於 2011年8月24日 下午4:51 寫道：
> Has Japanese
> disunification been completely killed, or me
when the sun reaches its red giant stage
and threatens to engulf the Earth. ☺
=
Siôn ap-Rhisiart
John H. Jenkins
jenk...@apple.com
practice, and, in practice, all OT engines run the bidi
algorithm in character space and not in glyph space. At this point, trying to
arrange things so that it can be done in glyph space instead is a practical
impossibility.
=
Hoani H. Tinikini
John H. Jenkins
jenk...@apple.com
e
> benefits if fully worked out, is a radical departure from how OpenType works.
>
I'll toss in my obligatory, "That's how AAT does it" reference. It has
advantages and disadvantages—but, as you say, OT would have to be heavily
redesigned to do it.
=
John H. Jenkins
井作恆
𐐖𐐱𐑌 𐐐. 𐐖𐐩𐑍𐐿𐐮𐑌𐑆
jenk...@apple.com
William_J_G Overington 於 2011年8月22日 下午12:36 寫道：
> On Monday 22 August 2011, John H. Jenkins wrote:
>
>> Forgive my asking, but this reference to the "description section of the
>> Macintosh Roman section of a TrueType font" has me puzzled, because I don't
41,$E549,$E57C,$EA00-$EA0F,$EC07";
>
Forgive my asking, but this reference to the "description section of the
Macintosh Roman section of a TrueType font" has me puzzled, because I don't
know what you're talking about. What table contains this string?
=
井作恆
John H. Jenkins
jenk...@apple.com
of storing
character-specific information useful on multiple platforms. This is one
reason why embedding the existing directionality controls within the text
itself is currently the most reliable way of getting the behavior one might
want in a platform-agnostic way.
=
Siôn ap-Rhisiart
John H. Jenkins
jenk...@apple.com
nencoded ideographs, but there is a lot of work to be done
before that would be practical.
=
John H. Jenkins
jenk...@apple.com
gt; would be little to unify outside of U+002E FULL STOP.
Oh, I imagine they'll have one or two turtle ideographs. :-)
Seriously, though, if and when we run into ETs with all their myriad writing
systems, I really don't think that we'll be Unicode to represent them.
===
feel over the current
situation, but, again, before you could convince the UTC to do this, you'd have
to present pretty solid evidence that the current solution doesn't work and
that this would.
=
John H. Jenkins
jenk...@apple.com
ce suggests that we're in no danger of running out of code points.
=
Siôn ap-Rhisiart
John H. Jenkins
jenk...@apple.com
orthwhile project:
>
> http://www.kickstarter.com/projects/1496420787/the-endangered-alphabets-project/
>
> Michael Everson * http://www.evertype.com/
>
>
>
>
>
=
井作恆
John H. Jenkins
jenk...@apple.com
ent of the IRG using a copy of Adobe-Japan1-6 to work out issues on Han
unification without waiting for Adobe to say anything about the set.
=
井作恆
John H. Jenkins
jenk...@apple.com
, I would personally prefer that the whole discussion be dropped
until Apple has had a chance to at least look over the document and respond.
To do otherwise strikes me as at the least discourteous and at best premature.
=
井作恆
John H. Jenkins
quot;letters," and so on.
> * Since those two letters must be encoded in 2 or 3 characters, with a
> monospace font, they are twice or 3 times larger than the other letters.
>
> To solve this last problem, would it be possible to make a font in which c
> ZWJ h would be dis
be better ?
>
Yes, that would be better. That way it will be tracked and it's less likely to
slip through the cracks in my schedule. For general questions, you can email
me directly.
=
Hoani H. Tinikini
John H. Jenkins
jenk...@apple.com
n't exist.
> Does the Unicode Consortium and/or ISO or indeed anyone else make any claims
> upon it?
>
Yes, the claim is that if you use it, you're generating invalid Unicode.
Don't do it, don't contemplate it, don't think about it.
=
John H. Jenkins
jenk...@apple.com
a step towards a
> multiscript web.
>
> Bob Richmond
>
>
>
>
=
Siôn ap-Rhisiart
John H. Jenkins
jenk...@apple.com
he
> Unicode site, but I'd be sure to ask permission before trying that out).
>
> Uriah
>
> On Mon, Sep 13, 2010 at 12:03 AM, John H. Jenkins wrote:
> I'll raise the possibility with the appropriate individuals, but I think it
> likely that the Consortium wou
ach radical, or
> which blocks include IICore characters.
> I'm also considering adding the contents of the Unicode Character Database as
> well at a later phase.
> Regards,
> Uriah Eisenstein
=
Siôn ap-Rhisiart
John H. Jenkins
jenk...@apple.com
l (and not national) sources used by Unicode during the
development of the original URO.
=
John H. Jenkins
jenk...@apple.com
gt; line-ending characters formatted with the Stylistic Set 7
>> OpenType Feature. No PUA; no variation selectors. Just
>> flourishing, OpenType glyphs.
>>
>>
>> Peter
>>
>
>
>
=
John H. Jenkins
jenk...@apple.com
ngly
suggests the existence of some sort of Platonic "plain text" which is the
essence of what was written.
=
Siôn ap-Rhisiart
John H. Jenkins
jenk...@apple.com
on.
Variation selectors are intended to cover cases where more information is
needed for rendering than is required for other processes such as searching
(Mongolian), or cases where different user communities disagree on whether two
forms must be unified or must be deunified.
=
Hoani H. Tinikini
John H. Jenkins
jenk...@apple.com
ng, and if they do this in their emails or tweets, or if they're
complaining that this is something that they want to do but can't, then Unicode
and plain text provide a proper way to help them.
=
Hoani H. Tinikini
John H. Jenkins
jenk...@apple.com
On Aug 3, 2010, at 12:00 PM, Robert Abel wrote:
> On 2010/08/03 18:17, John H. Jenkins wrote:
>>
>> Thanks for the report; it's been fixed.
>>
>> BTW, problems with the Unihan database should be reported via
>> http://www.unicode.org/reporting.html
work…
>
> Martin Heijdra
> Martin J. Heijdra
> Chinese Studies/East Asian Studies Bibliographer
> East Asian Library and the Gest Collection
> Frist Campus Center, Room 314
> Princeton University
> Princeton, NJ 08544
> United States
=
Hoani H. Tinikini
John H. Jenkins
jenk...@apple.com
re complete. Are there any
> tools around that could show this - perhaps something that could tell how
> many glyphs are defined in a given interval?
>
>
=
井作恆
John H. Jenkins
jenk...@apple.com
While it's exciting to have the new symbol, and while one
does want to strike while the iron is hot, ten years from now it won't have
made much difference whether it was encoded in 2010 or 2011--unless the job got
botched through over-haste.
Festina lente.
=
井作恆
John H. Jenkins
jenk...@apple.com
the way we should do
it wherever possible, but no, a formal policy is probably not best" camp.)
=
井作恆
John H. Jenkins
jenk...@apple.com
We hope to have it back in the next few days.
On Jul 12, 2010, at 8:34 AM, Martin Heijdra wrote:
> When will Unihan be back? It has been down for quite a while now, and there
> are librarians for whom checking this is part of their workflow…
>
> Martin
=
Siôn ap-Rhisiart
Joh
t;> Hello!
>>
>> 001B, 001D, 001C are present in some keyboard layouts. What are these
>> characters used for?
>>
>>
>
>
>
=
Siôn ap-Rhisiart
John H. Jenkins
jenk...@apple.com
ants I've looked at seem to have very different
> abstract shapes, in some cases looking more like simplified/traditional
> pairs. As I said I don't know clearly how they are determined. Are they
> supposed to be exactly those pairs which would be unified if it were not for
> the Source Separation Rule?
>
> TIA,
> Uriah
=
John H. Jenkins
jenk...@apple.com
o
how Unicode does things.
In re the tonal system specifically, I note that it uses a glyph for
hexadecimal-10 which looks (to me, at least) identical with a glyph for
decimal-9. This IMHO represents a serious impediment to the system ever being
adopted. I will, however, gladly be prove
o
how Unicode does things.
In re the tonal system specifically, I note that it uses a glyph for
hexadecimal-10 which looks (to me, at least) identical with a glyph for
decimal-9. This IMHO represents a serious impediment to the system ever being
adopted. I will, however, gladly be prove
ode.org [mailto:unicode-bou...@unicode.org] On
> Behalf Of Peter Constable
> Sent: Saturday, June 05, 2010 6:45 PM
> To: Unicode Discussion
> Subject: base-9 digits
>
> Can we please encode new characters for base-9 digits “0”, “1”, “2”, “3”,
> “4”, “5”, “6”, “7”, “8”?
t support for it, get it adopted
outside of a narrow group of supporters. If there is a *demonstrated* problem
that this is a *demonstrated* solution for, then *maybe* the UTC would look at
it. Until then, discussing the proposal here is simply tilting at windmills.
=
John H. Jenkins
jenk...@apple.com
On Jun 4, 2010, at 2:48 PM, Luke-Jr wrote:
> The computer industry already has units of 'kilobyte' and such referring to
> powers of 1024.
>
You mean, of course, kibibyte. A kilobyte is 1000 bytes.
Unicode has Roman numerals for compatibility reasons, not for serious use as
Roman numerals. If you *really* want to work with roman numerals, even in the
year MMDCCLXIII AUC, use the letters, just like the Romans did.
And in any event, you're undermining your own case, because a *lot* of
socie
You can peruse
the IRGs documents on the subject at their Web site,
<http://appsrv.cse.cuhk.edu.hk/~irg/>.
=
John H. Jenkins
jenk...@apple.com
ime, yours not excepted. If you seriously want to get
such a radical redefinition of "plain text" included in Unicode, you'll need to
start elsewhere.
And I don't have time myself to really comment further than I already have.
=
John H. Jenkins
jenk...@apple.com
and then for
> the program to run in a virtual machine within the app, displaying a
> graphical result on the screen of the iPad. Could such an app be written
> based on the information in the paper_draft_005.pdf document?
>
OK, one very last note. The answer to this question is,
First of all, as Michael says, this isn't character encoding. You're not
interchanging plain text. This is essentially machine language you're writing
here, and there are entirely different venues for developing this kind of
thing.
Secondly, I have virtually no idea what problem this is att
As you say, the main problem is that there are so many different
possible sets. Some will be proprietary, which would limit their
usefulness although there would, I believe, otherwise be no objection
to its inclusion. If you can come up with a reasonably standard set and
reasonably consistent d
On Dec 10, 2004, at 1:25 PM, Tim Greenwood wrote:
Is that like the 'Please RSVP' that I see all too often? Or should
that not be excused?
Or -- my own personal favorite -- "in the year AD 2004."
On Dec 8, 2004, at 3:57 PM, Patrick Andries wrote:
Azzedine Ait Khelifa a écrit :
Hello All,
The subject of this conference is really interesting and veryusefull.
But once again Africa is forgotten.
I want to know, if we can have the same conference "AfricaOriented"
scheduled ?
If Not, What shou
On Dec 6, 2004, at 10:23 AM, Johannes Bergerhausen wrote:
From some discussions here i learned that Arial Unicode MS contains
about 50.000 glyphs,
which is about the size of characters encoded in Unicode 2.0 and was
shipped the last
time bundled with Office for Windows 2003.
A Pan-Unicode-Font
) NFD.
"Slightly altered"?
Yes, the specification for the Mac file system was frozen before NFD
had been developed by the UTC, so it isn't exactly the same. But it's
close.
John H. Jenkins
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://homepage.mac.com/jhjenkins/
he non-BMP characters to the PUA using ftxdumperfuser (or
remove their Unicode mappings altogether), and re-add (or re-shift) the
Unicode mappings after using FontLab with the same tool.
========
John H. Jenkins
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://homepage.mac.com/jhjenkins/
x," e.g., "u2" I'm told that the
latest version of FontLab will generate an appropriate cmap entry for
it, but I don't know for sure.)
John H. Jenkins
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://homepage.mac.com/jhjenkins/
. Is it true
that, to represent Chinese simplified programmatically, two bytes will
do.
Unicode in the UTF-16 encoding will cover almost all the simplified
Chinese characters people use today in two bytes. There are the
occasional exceptions which will require four bytes.
John H
) for KahnawÃ:ke (Mohawk).
Or Peking for BeÇjÄng. :-)
John H. Jenkins
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://homepage.mac.com/jhjenkins/
27;re using
UTF-8, UTF-16, or UTF-32.
John H. Jenkins
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://homepage.mac.com/jhjenkins/
later
the question of the other symbols.
It's a logo. We normally don't do logos.
To be a little less terse, in the case of symbols like this, it is the
strong preference not to encode as a means to encourage use.
====
John H. Jenkins
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://h
e Mac converts Unicode to old Mac scripts which it
then renders. That's why all the question marks when the page is
looked at with MS Explorer.
======
John H. Jenkins
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://homepage.mac.com/jhjenkins/
p;item_id=GraphiteFonts.
We could probably help you get it to work on Mac OS X. Meanwhile,
Xenotype claims to have a Burmese language kit for Mac OS X
(<http://www.xenotypetech.com/osxBurmese.html>), although nobody at
Apple has seen it, so we can't confirm that it works as advertised
don't think PUA characters are used, actually, but I could
be wrong.
No, it uses the acutal Unicode characters, and just has a huge cmap
that maps everything in Unicode to the glyph for its block.
======
John H. Jenkins
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://homepage.mac.com/jhjenkins/
it would be useful for its Mac users.
Er, no. Apple thought it would be useful for its Mac users and
commissioned Michael to make glyphs. (And I personally think he's done
an excellent job.)
==
John H. Jenkins
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://homepage.mac.com/jhjenkins/
On Thursday, July 17, 2003, at 12:00 AM, Richard Cook wrote:
I'm guessing this just hasn't been implemented yet.
You are guessing correctly. Once some of the dust settles from my day
job, I expect I can get to this.
======
John H. Jenkins
[EMAIL PROTECTED]
[EMAIL PROTE
On Monday, July 7, 2003, at 4:38 PM, Michael Everson wrote:
At 16:22 -0600 2003-07-07, John H. Jenkins wrote:
IIRC the English prefer to say "Mr Roberts."
The, ahem, Irish too. ;-)
Well, to be frank, I'm sure that the Welsh, Scots, and Manx probably
do, too. (Did I leave an
my name.
IIRC the English prefer to say "Mr Roberts."
==
John H. Jenkins
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://homepage.mac.com/jhjenkins/
tml>). I'm not sure
of the status of Unicode support, but it seems to be fine if you're not
worrying about collating or similar services. It's what's used at the
moment to host the Unihan database, for example.
==
John H. Jenkins
[EMAIL PROTECTED]
[EMAIL PROTECTE
troy pounds].
Apparently a weighty publication, that forthcoming Unicode standard...
Cheers,
Otto Stolz
==
John H. Jenkins
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.tejat.net/
1 - 100 of 317 matches
Mail list logo
