Re: Unicode, SMS and year 2012

2012-04-30 Thread David Starner
On Sat, Apr 28, 2012 at 6:22 PM, Naena Guru naenag...@gmail.com wrote: How I see Unicode is as a set of character groups, 7-bit, 8-bit (extends and replaces 7-bit), 16-bit, and CJKV that use some sort of 16-bit paring. That's one lens to see Unicode through, but in most cases it's

Re: U+2018 is not RIGHT HIGH 6

2012-04-30 Thread Asmus Freytag
Even if some minutiae of glyph selection are left to a font, the problem is often that there's no specification as to what certain languages need, so that fonts cannot be expected to provide the correct implementation. When Unicode was first created, the fact that one and the same quotation

Re: Unicode, SMS and year 2012

2012-04-30 Thread Asmus Freytag
Darcula and other novels aside, there are applications where text volume definitely matters. One I've come across in my work is transaction-log filtering. Logs, like http logs, can generate rather interesting streams of text data, where the volume easily becomes so large that merely

Re: U+2018 is not RIGHT HIGH 6

2012-04-30 Thread Werner LEMBERG
So, one of the most useful things that could come of the current discussion, would be a thorough documentation of the glyph variations needed to support both English and German for the same quotation mark characters. For German, it's quite simple: The opening quotes must visibly start at the

Re: Encoding of Numbers Composed of Decimal Digits (General Category of Nd)

2012-04-30 Thread Michael Probst
Am Samstag, den 28.04.2012, 13:18 +0100 schrieb Richard Wordingham: Is it anywhere stated as policy that numbers written by a string of decimal digits will be encoded with the most significant digit first in storage order? I couldn't find it stated anywhere. Isn't this about encoding

Re: Writing Babylonian Numbers in Unicode

2012-04-30 Thread Michael Probst
Am Samstag, den 28.04.2012, 15:56 +0100 schrieb Richard Wordingham: However, there does not appear to be anything for *CUNEIFORM NUMERIC SIGN TWO U, for which one might expect *CUNEIFORM SIGN MAN (Borger 2003 no. 708). So, how does one distinguish '20' from '610' (= 10×60 + 10)? I resorted

Re: U+2018 is not RIGHT HIGH 6

2012-04-30 Thread Michael Probst
Am Montag, den 30.04.2012, 09:29 +0200 schrieb Werner LEMBERG: So, one of the most useful things that could come of the current discussion, would be a thorough documentation of the glyph variations needed to support both English and German for the same quotation mark characters. English

Re: U+2018 is not RIGHT HIGH 6

2012-04-30 Thread Andreas Prilop
On Sun, 29 Apr 2012, Asmus Freytag wrote: So, one of the most useful things that could come of the current discussion, would be a thorough documentation of the glyph variations needed to support both English and German for the same quotation mark characters. Actually, the case is quite

Re: U+2018 is not RIGHT HIGH 6

2012-04-30 Thread Mark Davis ☕
FYI, we have gathered in CLDR on usage of characters in different languages, including quotation marks (and those to use for embeddings). It is at http://unicode.org/repos/cldr-tmp/trunk/beta-charts/by_type/misc.characters.html . (The page takes a while to load because of the exemplar information

Re: U+2018 is not RIGHT HIGH 6

2012-04-30 Thread David Starner
On Mon, Apr 30, 2012 at 5:30 AM, Michael Probst michael.probs...@web.de wrote: It just makes more sense than giving a code point to a mere glyph variant (U+201F); or the other way round: If even that has been encoded already, the RIGHT HIGH 6 should have been before, and if it hasn't, it

RE: U+2018 is not RIGHT HIGH 6

2012-04-30 Thread Doug Ewell
Michael Probst michael dot probst03 at web dot de wrote: It just makes more sense than giving a code point to a mere glyph variant (U+201F); or the other way round: If even that has been encoded already, the RIGHT HIGH 6 should have been before, and if it hasn't, it should be now. I'm kind

Re: U+2018 is not RIGHT HIGH 6

2012-04-30 Thread Markus Scherer
On Mon, Apr 30, 2012 at 9:47 AM, Doug Ewell d...@ewellic.org wrote: Michael Probst michael dot probst03 at web dot de wrote: It just makes more sense than giving a code point to a mere glyph variant (U+201F); or the other way round: If even that has been encoded already, the RIGHT HIGH 6

A new character to encode from the Onion? :)

2012-04-30 Thread Bill Poser
Digital typography has reached *The Onion*: http://www.theonion.com/articles/errant-keystroke-produces-character-never-before-s,28030/ .

Re: Encoding of Numbers Composed of Decimal Digits (General Category of Nd)

2012-04-30 Thread Richard Wordingham
On Mon, 30 Apr 2012 13:46:20 +0200 Michael Probst michael.probs...@web.de wrote: Am Samstag, den 28.04.2012, 13:18 +0100 schrieb Richard Wordingham: Is it anywhere stated as policy that numbers written by a string of decimal digits will be encoded with the most significant digit first in

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

2012-04-30 Thread Asmus Freytag
On 4/30/2012 12:27 PM, Bill Poser wrote: Digital typography has reached The Onion: http://www.theonion.com/articles/errant-keystroke-produces-character-never-before-s,28030/. Quote: , it is, in all likelihood, "probably just another goddamn fertility

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

2012-04-30 Thread John H. Jenkins
Asmus Freytag asm...@ix.netcom.com 於 2012年4月30日 下午1:59 寫道: On 4/30/2012 12:27 PM, Bill Poser wrote: Digital typography has reached The Onion: http://www.theonion.com/articles/errant-keystroke-produces-character-never-before-s,28030/. Quote: , it is, in all likelihood, probably just

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

2012-04-30 Thread Asmus Freytag
On 4/30/2012 1:25 PM, John H. Jenkins wrote: Asmus Freytag asm...@ix.netcom.com mailto:asm...@ix.netcom.com 於 2012年4月30日 下午1:59 寫道: On 4/30/2012 12:27 PM, Bill Poser wrote: Digital typography has reached /The Onion/:

Re: Writing Babylonian Numbers in Unicode

2012-04-30 Thread Richard Wordingham
On Mon, 30 Apr 2012 13:51:27 +0200 Michael Probst michael.probs...@web.de wrote: Am Samstag, den 28.04.2012, 15:56 +0100 schrieb Richard Wordingham: However, there does not appear to be anything for *CUNEIFORM NUMERIC SIGN TWO U, for which one might expect *CUNEIFORM SIGN MAN (Borger 2003

Re: Writing Babylonian Numbers in Unicode

2012-04-30 Thread Ken Whistler
On 4/30/2012 3:33 PM, Richard Wordingham wrote: One is not compelled to construct U+3039 (〹) ,twenty' from two U+3038 (〸) ,ten', so a CUNEIFORM TWO U may well be missing. It looks as though it is. No, it isn't. It was present in Proposal N2664

Re: [unicode] Re: vertical writing mode of modern Yi?

2012-04-30 Thread suzuki toshiya
I wouldn't expect to see vertical modern standard Yi text in modern publications, other than perhaps newspapers. I got a scanned image of Liangshan Ribao (涼山日報), dated 2002/Mar/9, the vertical text is laid out without glyph rotation. Regards, mpsuzuki inline: LiangshanRibao-20020309.png