Re: Plain text (from Re: Avoidance variants)

2015-03-26 Thread Shervin Afshar
On Thu, Mar 26, 2015 at 8:10 PM, Mark E. Shoulson wrote: > Statelessness looks more like an ideal; the current reality already > violates it. The question is whether that ideal is "violated" because of choice or out of necessity; bidi-related stateful format codes specifically seem like a case

Re: Plain text (from Re: Avoidance variants)

2015-03-26 Thread Mark E. Shoulson
On 03/26/2015 08:01 PM, Leo Broukhis wrote: Exact semantics of formatting characters aside, it is best to define plain text as a stateless stream. Well, not strictly true. Or at least, Unicode text is not quite stateless. We have these directional overrides and embeddings and isolates... The

Re: Plain text (from Re: Avoidance variants)

2015-03-26 Thread Leo Broukhis
Exact semantics of formatting characters aside, it is best to define plain text as a stateless stream. The characters you're proposing require a decoder to keep state, therefore they won't do. At most you may ask for *U+E1001 COMBINING ITALICIZER *U+E1003 COMBINING BOLDIFIER after all, we already h

Re: Plain text (from Re: Avoidance variants)

2015-03-26 Thread Mark E. Shoulson
On 03/26/2015 11:18 AM, William_J_G Overington wrote: > Blocks of boring plain text, no italics or effects any more complex than justification, simple notes written all in one font with no formatting to speak of etc. I am wondering if it is considered a good idea to define into Plane 14 some

Re: Avoidance variants

2015-03-26 Thread Mark E. Shoulson
On 03/26/2015 01:14 AM, Jonathan Rosenne wrote: “It's still a HEH, it just looks like another letter, right?” Wrong. It’s a QOF. Just like the p in receipt is a p. Unicode should not concern itself with the reasons words are spelt the way they are spelt. Good enough point. And I suppose w

Re: Plain text (from Re: Avoidance variants)

2015-03-26 Thread Tim Greenwood
Many years ago, in the initial days of Unicode development, I discussed it with a colleague at DEC. His response was that Unicode would become weighed down with all sorts of junk getting added to it. Over twenty years later Unicode's huge success comes from not having done that. It is not going to

IUC 39 call for participation - abstract submission reminder

2015-03-26 Thread Rick McGowan
Hi everyone, Just a quick reminder that the Call for participation in IUC #39 is now open, and the deadline for submitting an abstract is coming up quickly: April 3. All the information is here, on the conference website: http://www.unicodeconference.org/ The conference itself is Octobe

RE: Plain text (from Re: Avoidance variants)

2015-03-26 Thread Tex Texin
Or to put it another way, you are inventing what is essentially another markup language. If you are going to tag text with styling, why not just use one of the many existing markup schemes used in html, bulletin boards, wiki, etc.? tex From: Unicode [mailto:unicode-boun...@unicode.org

RE: Plain text (from Re: Avoidance variants)

2015-03-26 Thread Shawn Steele
> I am wondering if it is considered a good idea to define into Plane 14 some > formatting characters, so that plain text could in the future contain italics > and so on. No, it would not then be “plain text” ___ Unicode mailing list Unicode@unicode.

Re: Plain text (from Re: Avoidance variants)

2015-03-26 Thread Asmus Freytag
On 3/26/2015 8:18 AM, William_J_G Overington wrote: > Blocks of boring plain text, no italics or effects any more complex than justification, simple notes written all in one font with no formatting to speak of etc. I am wondering if it is co

Plain text (from Re: Avoidance variants)

2015-03-26 Thread William_J_G Overington
> Blocks of boring plain text, no italics or effects any more complex than justification, simple notes written all in one font with no formatting to speak of etc. I am wondering if it is considered a good idea to define into Plane 14 some formatting characters, so that plain text could

Re: Avoidance variants

2015-03-26 Thread Asmus Freytag (t)
On 3/25/2015 10:14 PM, Jonathan Rosenne wrote: “It's still a HEH, it just looks like another letter, right?” Wrong. It’s a QOF. Just like the p in receipt is a p. Unicode should not concern itself with the reasons words are spelt the way they are spelt. Identifying deliberate misspellings

Re: Are you CONFUSED about WHAT CHARACTER(S) you type?!?!

2015-03-26 Thread Doug Ewell
Peter Constable wrote: >> It's a known font bug. It's been around since at least 2010. It's >> probably not the end of the world. > > It's the first time it was retorted to us, AFAIK. (I assume "reported" unless the report was made in a caustic manner. :) Here's a post to Microsoft Community fr

Re: Are you CONFUSED about WHAT CHARACTER(S) you type?!?!

2015-03-26 Thread Mark Davis ☕️
It only provides a "stand-in" glyph if you don't otherwise have a font for that character on your system. That "stand-in" just indicates the type of character (eg script). No single font with current technology can handle all of Unicode. The most complete open font set I know of is the Noto family

Re: Are you CONFUSED about WHAT CHARACTER(S) you type?!?!

2015-03-26 Thread Michael McGlothlin
Similar but with a couple differences. Most important would be getting vendors to actually use the font. Also it should be appropriate to actually display the characters rather than being debugging information. Does this last resort font represent every character in some meaningful way? e.g. I'