Re: NNBSP

2019-01-18 Thread Marcel Schneider via Unicode
On 19/01/2019 01:55, Asmus Freytag via Unicode wrote: On 1/18/2019 2:05 PM, Marcel Schneider via Unicode wrote: On 18/01/2019 20:09, Asmus Freytag via Unicode wrote: Marcel, about your many detailed *technical* questions about the history of character properties, I am afraid I have no

Re: NNBSP

2019-01-18 Thread Richard Wordingham via Unicode
On Fri, 18 Jan 2019 10:20:22 -0800 Asmus Freytag via Unicode wrote: > However, if there's a consensus interpretation of a given character > the you can't just go in and change it, even if it would make that > character work "better" for a given circumstance: you simply don't > know (unless you

Re: NNBSP

2019-01-18 Thread Asmus Freytag via Unicode
On 1/18/2019 2:46 PM, Shawn Steele via Unicode wrote: >> That should not impact all other users out there interested in a civilized layout. I’m not sure that the choice of the word “civilized” adds value to the conversation. 

Re: NNBSP

2019-01-18 Thread Asmus Freytag via Unicode
On 1/18/2019 2:05 PM, Marcel Schneider via Unicode wrote: On 18/01/2019 20:09, Asmus Freytag via Unicode wrote: Marcel, about your many detailed *technical* questions about the history of character

Re: Loose character-name matching

2019-01-18 Thread Richard Wordingham via Unicode
On Thu, 17 Jan 2019 18:44:50 -0500 "J. S. Choi" via Unicode wrote: > I’m implementing a Unicode names library. I’m confused about loose > character-name matching, even after rereading The Unicode Standard § > 4.8, UAX #34 § 4, #44 § 5.9.2 – as well as >

RE: NNBSP

2019-01-18 Thread Shawn Steele via Unicode
>> If they are obsolete apps, they don’t use CLDR / ICU, as these are designed >> for up-to-date and fully localized apps. So one hassle is off the table. Windows uses CLDR/ICU. Obsolete apps run on Windows. That statement is a little narrowminded. >> I didn’t look into these date

Re: NNBSP

2019-01-18 Thread Marcel Schneider via Unicode
On 18/01/2019 23:46, Shawn Steele wrote: *>> *Keeping these applications outdated has no other benefit than providing a handy lobbying tool against support of NNBSP. I believe you’ll find that there are some French banks and other institutions that depend on such obsolete applications

RE: NNBSP

2019-01-18 Thread Shawn Steele via Unicode
>> Keeping these applications outdated has no other benefit than providing a >> handy lobbying tool against support of NNBSP. I believe you’ll find that there are some French banks and other institutions that depend on such obsolete applications (unfortunately). Additionally, I believe you’ll

Re: NNBSP

2019-01-18 Thread Marcel Schneider via Unicode
On 18/01/2019 22:03, Shawn Steele via Unicode wrote: I've been lurking on this thread a little. This discussion has gone “all over the place”, however I’d like to point out that part of the reason NBSP has been used for thousands separators is because that it exists in all of those legacy

RE: NNBSP

2019-01-18 Thread Shawn Steele via Unicode
I've been lurking on this thread a little. This discussion has gone “all over the place”, however I’d like to point out that part of the reason NBSP has been used for thousands separators is because that it exists in all of those legacy codepages that were mentioned predating Unicode. Whether

Re: NNBSP

2019-01-18 Thread Marcel Schneider via Unicode
On 18/01/2019 19:20, Asmus Freytag via Unicode wrote: On 1/18/2019 7:27 AM, Marcel Schneider via Unicode wrote: Covering existing character sets (National, International and Industry) was _an_ (not "the") important goal at the time: such coverage was understood as a necessary (although not

Re: NNBSP

2019-01-18 Thread Marcel Schneider via Unicode
On 18/01/2019 19:02, Asmus Freytag via Unicode wrote: On 1/18/2019 7:27 AM, Marcel Schneider via Unicode wrote: I understand only better why a significant majority of UTC is hating French. Francophobia is also palpable in Canada, beyond any technical reasons, especially in the IT

Re: Encoding italic (was: A last missing link)

2019-01-18 Thread Asmus Freytag via Unicode
I would full agree and I think Mark puts it really well in the message below why some of the proposals brandished here are no longer plain text but "not-so-plain" text. I think we are better served with a solution that provides some form of "light" rich text, for

Re: NNBSP

2019-01-18 Thread Asmus Freytag via Unicode
Marcel, about your many detailed *technical* questions about the history of character properties, I am afraid I have no specific recollection. French is not the only language that uses a space to group figures. In fact, I grew up with thousands separators being

Re: NNBSP

2019-01-18 Thread Asmus Freytag via Unicode
On 1/18/2019 7:27 AM, Marcel Schneider via Unicode wrote: Covering existing character sets (National, International and Industry) was an (not "the") important goal at the time: such

Re: NNBSP

2019-01-18 Thread Asmus Freytag via Unicode
On 1/18/2019 7:27 AM, Marcel Schneider via Unicode wrote: I understand only better why a significant majority of UTC is hating French. Francophobia is also palpable in Canada, beyond any technical reasons, especially in the IT

Re: Encoding italic (was: A last missing link)

2019-01-18 Thread wjgo_10...@btinternet.com via Unicode
Mark E. Shoulson wrote: …, since italic fonts generally are narrower than roman). I remember reading years ago that that was why italic type was invented in the first place in the fifteenth century, so that more text could be got into small format books that could conveniently be carried

Re: Encoding italic

2019-01-18 Thread Mark E. Shoulson via Unicode
On 1/17/19 1:27 AM, Martin J. Dürst via Unicode wrote: This lead to the layering we have now: Case distinctions at the character level, but style distinctions at the rich text level. Any good technology has layers, and it makes a lot of sense to keep established layers unless some serious

Re: Encoding italic (was: A last missing link)

2019-01-18 Thread Mark E. Shoulson via Unicode
On 1/16/19 7:16 AM, Andrew Cunningham via Unicode wrote: HI Victor, an off list reply. The contents are just random thoughts sparked by an interesting conversation. On Wed, 16 Jan 2019 at 22:44, Victor Gaultney via Unicode mailto:unicode@unicode.org>> wrote: - It finally, and

Re: Encoding italic (was: A last missing link)

2019-01-18 Thread Mark E. Shoulson via Unicode
On 1/16/19 6:23 AM, Victor Gaultney via Unicode wrote: Encoding 'begin italic' and 'end italic' would introduce difficulties when partial strings are moved, etc. But that's no different than with current punctuation. If you select the second half of a string that includes an end quote

Re: NNBSP

2019-01-18 Thread Marcel Schneider via Unicode
On 17/01/2019 20:11, 梁海 Liang Hai via Unicode wrote: [Just a quick note to everyone that, I’ve just subscribed to this public list, and will look into this ongoing Mongolian-related discussion once I’ve mentally recovered from this week’s UTC stress. :)] Welcome to Unicode Public. Hopefully

Re: wws dot org

2019-01-18 Thread Mark E. Shoulson via Unicode
On 1/17/19 1:50 PM, Frédéric Grosshans via Unicode wrote: On a side note, you the site considers visible speech as a living-script, which surprised be. This information is indeed in the Wikipedia infobox and implied by its “HMA status” on the Berkeley SEI page, but the text of the wikipedia

Re: wws dot org

2019-01-18 Thread Johannes Bergerhausen via Unicode
Thanks a lot for this input! We’ll check this with Deborah Anderson from SEI Berkeley. The update of the web site to Unicode 12.0 will be an opportunity to make some corrections. All the best, Johannes > Am 17.01.2019 um 19:50 schrieb Frédéric Grosshans > : > > Thanks for this nice website