Re: Encoding italic

2019-01-19 Thread Richard Wordingham via Unicode
On Sun, 20 Jan 2019 03:14:21 + James Kass via Unicode wrote: > (In the event that a persuasive proposal presentation prompts the > possibility of italics encoding...) The use of italic script isn't just restricted to the Latin script, which includes base characters not supported by the

Re: Encoding italic

2019-01-19 Thread Richard Wordingham via Unicode
On Fri, 18 Jan 2019 10:51:18 -0500 "Mark E. Shoulson via Unicode" wrote: > 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

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

2019-01-19 Thread James Kass via Unicode
(In the event that a persuasive proposal presentation prompts the possibility of italics encoding...) Possible approaches include: 1 - Liberating the italics from the Members Only Math Club ...which has been an ongoing practice since they were encoded.  It already works, but the set is

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

2019-01-19 Thread Kent Karlsson via Unicode
(I have skipped some messages in this thread, so maybe the following has been pointed out already. Apologies for this message if so.) You will not like this... But... There is already a standardised, "character level" (well, it is from a character standard, though a more modern view would be

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

2019-01-19 Thread James Kass via Unicode
Victor Gaultney wrote, > If however, we say that this "does not adequately consider the harm done > to the text-processing model that underlies Unicode", then that exposes a > weakness in that model. That may be a weakness that we have to accept for > a variety of reasons (technical

Re: NNBSP

2019-01-19 Thread Asmus Freytag via Unicode
On 1/19/2019 3:53 AM, James Kass via Unicode wrote: Marcel Schneider wrote, > When you ask for knowing the foundations and that knowledge is persistently refused, > you end up believing that those foundations just can’t

Re: Encoding italic

2019-01-19 Thread Asmus Freytag via Unicode
On 1/19/2019 12:34 PM, James Kass via Unicode wrote: On 2019-01-19 6:19 PM, wjgo_10...@btinternet.com wrote: > It seems to me that it would be useful to have some codes that are > ordinary characters in some contexts

Re: Encoding italic

2019-01-19 Thread James Kass via Unicode
On 2019-01-19 6:19 PM, wjgo_10...@btinternet.com wrote: > It seems to me that it would be useful to have some codes that are > ordinary characters in some contexts yet are control codes in others, ... Italics aren't a novel concept.  The approach for encoding new characters is that 

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

2019-01-19 Thread wjgo_10...@btinternet.com via Unicode
Asmus Freytag wote: This is an effort that's out of scope for Unicode to implement, or, I should say, if the Consortium were to take it on, it would be a separate technical standard from The Unicode Standard. I note what you say, but what concerns me is that there seem to be an increasing

Re: NNBSP

2019-01-19 Thread James Kass via Unicode
Marcel Schneider wrote, > When you ask for knowing the foundations and that knowledge is persistently refused, > you end up believing that those foundations just can’t be told. > > Note, too, that I readily ceased blaming UTC, and shifted the blame elsewhere, where it > actually belongs

Re: NNBSP

2019-01-19 Thread Marcel Schneider via Unicode
On 19/01/2019 09:42, Asmus Freytag via Unicode wrote: […] For one, many worthwhile additions / changes to Unicode depend on getting written up in proposal form and then championed by dedicated people willing to see through the process. Usually, Unicode has so many proposals to pick from that

Re: NNBSP

2019-01-19 Thread Marcel Schneider via Unicode
On 19/01/2019 01:21, Shawn Steele wrote: *>> *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.

Re: NNBSP

2019-01-19 Thread Asmus Freytag via Unicode
On 1/18/2019 11:34 PM, Marcel Schneider via Unicode wrote: Current practice in electronic publishing was to use a non-breakable thin space, Philippe Verdy reports. Did that information come in somehow? ==>