Re: Preparing a proposal for encoding a portable interpretable object code into Unicode (from Re: IUC 34 - call for participation open until May 26)

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

Re: Preparing a proposal for encoding a portable interpretable object code into Unicode (from Re: IUC 34 - call for participation open until May 26)

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, No. = John H. Jenkins jenk

Re: Preparing a proposal for encoding a portable interpretable object code into Unicode (from Re: IUC 34 - call for participation open until May 26)

elsewhere. And I don't have time myself to really comment further than I already have. = John H. Jenkins jenk...@apple.com

Re: A question about user areas

documents on the subject at their Web site, http://appsrv.cse.cuhk.edu.hk/~irg/. = John H. Jenkins jenk...@apple.com

Re: Hexadecimal digits

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

Re: Hexadecimal digits

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.

Re: Overloading Unicode

. 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

Re: Octal

...@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”? Peter = John H. Jenkins jenk...@apple.com

Re: Hexadecimal digits

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 proven wrong. = 井作恆 John H. Jenkins jenk

Re: Are Unihan variant relations expected to be symmetrical?

. 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

Re: 001B, 001D, 001C

used for? = Siôn ap-Rhisiart John H. Jenkins jenk...@apple.com

Re: Status of Unihan

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 John H. Jenkins jenk

Re: ? Reasonable to propose stability policy on numeric type = decimal

is probably not best camp.) = 井作恆 John H. Jenkins jenk...@apple.com

Re: Indian new rupee sign

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

Re: Most complete (free) Chinese font?

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

Re: Unihan is back, but...

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. They're less likely to slip through the cracks

Re: Accessing alternate glyphs from plain text (from Re: Draft Proposal to add Variation Sequences for Latin and Cyrillic letters)

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

Re: Accessing alternate glyphs from plain text (from Re: Draft Proposal to add Variation Sequences for Latin and Cyrillic letters)

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

Re: Accessing alternate glyphs from plain text

is the essence of what was written. = Siôn ap-Rhisiart John H. Jenkins jenk...@apple.com

Re: Accessing alternate glyphs from plain text

...@microsoft.com wrote: See the attached PDF showing Unicode 5.2 text set in Word 2010 using the Gabriola font with line-ending characters formatted with the Stylistic Set 7 OpenType Feature. No PUA; no variation selectors. Just flourishing, OpenType glyphs. Peter = John H

Re: U-Source ideographs mapped to themselves

of the original URO. = John H. Jenkins jenk...@apple.com

Re: Unihan SQL access

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

Re: Creative people on Twitter

. 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

Re: Errors in Unihan data : simplified/traditional variants

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

Re: ch ligature in a monospace font

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 displayed as a new glyph? Yes, it's fairly trivial to do. = 井作恆 John H. Jenkins jenk...@apple.com

Re: Quick survey of Apple symbol fonts (in context of the Wingding/Webding proposal)

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

Re: Endangered Alphabets

/ = 井作恆 John H. Jenkins jenk...@apple.com

Re: Code pages and Unicode (wasn't really: RE: Endangered Alphabets)

-Rhisiart John H. Jenkins jenk...@apple.com

Re: RTL PUA?

H. Jenkins jenk...@apple.com

Re: Code pages and Unicode

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. = 井作恆 John H. Jenkins jenk...@apple.com

Re: Code pages and Unicode

that would be practical. = John H. Jenkins jenk...@apple.com

Re: RTL PUA?

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

Re: RTL PUA?

,$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

Re: RTL PUA?

William_J_G Overington 於 2011年8月22日 下午12:36 寫道： On Monday 22 August 2011, John H. Jenkins jenk...@apple.com 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 know what you're talking

Re: RTL PUA?

and disadvantages—but, as you say, OT would have to be heavily redesigned to do it. = John H. Jenkins 井作恆 Жбь А. ЖЩэпЮьц jenk...@apple.com

Re: RTL PUA?

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

Re: Code pages and Unicode

its red giant stage and threatens to engulf the Earth. ☺ = Siôn ap-Rhisiart John H. Jenkins jenk...@apple.com

Re: Code pages and Unicode

. 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 merely scotched? = 井作恆 John H. Jenkins jenk

Re: Controls, gliphs, flies, lemonade

, some else in another (a_a / aa_ - double comb. char., sure you seen that), so we have no standard at all. Off course, i can learn this complex standard, but 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

Re: New version of UTR #45 published

of interest to people who are tracking IRG work. = Siôn ap-Rhisiart John H. Jenkins jenk...@apple.com

Re: Unihan data for U+2B5B8 error

. 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

Re: Unihan data for U+2B5B8 error

you can't count on there being anybody reading this mailing list 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

Re: Unihan data for U+2B5B8 error

Andrew West 於 2011年10月20日 上午3:25 寫道： On 19 October 2011 18:41, John H. Jenkins jenk...@apple.com wrote: U+613F kDefinition (variant/simplification of U+9858 願) desire, want, wish; (archaic) prudent, cautious U+613F kSemanticVariant U+9858kFenn:T U+613F kSpecializedSemanticVariant U

Re: missing characters: combining marks above runs of more than 2 base letters

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

Re: Upside Down Fu character

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

Re: Upside Down Fu character

/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

Re: Upside Down Fu character

), 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: Kang-Hao (Kenny) Lu 於 2012年1月12日 上午12:13 寫道： * Three folks think this is rather

Re: Upside Down Fu character

. 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

Re: Unihan database

Frist Campus Center, Room 314 Princeton University Princeton, NJ 08544 United States = John H. Jenkins 井作恆 Жбь А. ЖЩэпЮьц jenk...@apple.com

Re: A new character to encode from the Onion? :)

another goddamn fertility symbol.terminator.gif Make that: currency symbol and ship it. Maybe a turtle ideograph? = 井作恆 John H. Jenkins jenk...@apple.com

Re: Plese add a Chinese Hanzi

blog: http://shizhao.org twitter: https://twitter.com/shizhao [[zh:User:Shizhao]] = Hoani H. Tinikini John H. Jenkins jenk...@apple.com

Re: Plese add a Chinese Hanzi

literature should be considered urgent use, in my opinion, and encoded sooner rather than later. = Hoani H. Tinikini John H. Jenkins jenk...@apple.com

Re: Flag tags

countries have 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. /tongue-in-cheek = John H. Jenkins jenk...@apple.com

Re: Offlist: complex rendering

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

Re: Unicode Core

of the documentation. = Hoani H. Tinikini John H. Jenkins jenk...@apple.com

Re: texteditors that can process and save in different encodings

BBEdit and TextWrangler on OS X both do a good job at handling different encodings. On 2012年10月3日, at 下午10:58, Stephan Stiller stephan.stil...@gmail.com wrote: Dear all, In your experience, what are the best (plaintext) texteditors or word processors for Linux / Mac OS X / Windows that

Re: xkcd: ‮LTR

Or, if one prefers: http://www.井作恆.net/XKCD/1137.html On 2012年11月21日, at 上午10:22, Deborah Goldsmith golds...@apple.com wrote: http://xkcd.com/1137/ Finally, an xkcd for Unicoders. :-) Debbie

Re: xkcd: LTR

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 jenk...@apple.com Or, if one prefers: http

Re: ‮LTR

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 d...@ewellic.org wrote: John H. Jenkins wrote: Or, if one prefers: http://www.井作恆.net/XKCD/1137.html In all the ensuing discussion

Re: I missed my self-imposed deadline for the Mayan numeral proposal

http://xkcd.com/998/ On 2012年12月21日, at 下午4:22, Doug Ewell d...@ewellic.org 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 |

Re: Ideograms (was: Spiral symbol)

On 2013年1月30日, at 上午4:50, Andreas Stötzner a...@signographie.de 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

Re: Ideograms

on Wikipedia http://en.wikipedia.org/wiki/The_Chinese_Language:_Fact_and_Fantasy - Tim On Wed, Jan 30, 2013 at 1:46 PM, John H. Jenkins jenk...@apple.com wrote: On 2013年1月30日, at 上午4:50, Andreas Stötzner a...@signographie.de wrote: Most ideographs in use are pictographs, for obvious

Re: Text in composed normalized form is king, right? Does anyone generate text in decomposed normalized form?

On 2013年2月1日, at 上午6:07, Costello, Roger L. coste...@mitre.org 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

Re: Encoding localizable sentences (was: RE: UTC Document Register Now Public)

On 2013年4月19日, at 下午1:52, Stephan Stiller stephan.stil...@gmail.com 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

Re: Standaridized variation sequences for the Desert alphabet?

> On Mar 27, 2017, at 2:04 AM, James Kass <jameskass...@gmail.com> wrote: > >> >> If we have any historic metal types, are there >> examples where a font contains both ligature >> variants? > > Apparently not. > > John H. Jenkins mentioned ear

Re: Standaridized variation sequences for the Desert alphabet?

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

Re: Standaridized variation sequences for the Desert alphabet?

> 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

Re: Standaridized variation sequences for the Desert alphabet?

> On Mar 27, 2017, at 9:56 AM, John H. Jenkins <jenk...@apple.com> wrote: > > >> On Mar 27, 2017, at 2:04 AM, James Kass <jameskass...@gmail.com >> <mailto:jameskass...@gmail.com>> wrote: >> >>> >>> If we have any historic

Re: Plane-2-only string

Ʃ ̥ ́ Ӽ Մ ݭ ݹ ந ன ோ ௦ ௽ ఋ ల ు ూ ృ ౓ ౘ ౥ ౷ ౸ ಜ ೏ ೕ ೖ ക ര േ ൈ ൉ ൩ ൯ ർ ൾ ൿ ග ට ඲ ฉ 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

Re: Emoji for major planets at least?

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

Re: Support for Extension F

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

Re: Memoji

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,

Re: Unicode 11.0 and 12.0 Cover Design Art

Maybe we should just throw in the towel and put "DON'T PANIC" on the cover in big, friendly letters. 

<    1   2   3