On 10/4/2015 5:30 AM, Sean Leonard
wrote:
On 10/3/2015 12:28 PM, Asmus Freytag (t) wrote: The following doesn't really answer my question; the first draft of 10646 seems pretty irrelevant in that context. However, I do have a small comment on your current project, so I'll append it here:
Totally agree that mapping these to random glyphs from 8-bit sets that happen to have those positions mapped to printable shapes is not useful. But this problem is already solved. Implementers already have solutions, and they do not depend on encoding anything or making any other changes. They simply show shapes that somehow contain the abbreviation for the control code, as in this example showing the line endings from a random text file: You can see that the shapes do not actually resemble the existing control pictures' glyph design although the principle is clearly related. Also notice that the implementation chooses to use different techniques for showing whitespace. Since over the 25 years of the standard none of these implementers ever approached the consortium with a request for a standard set of character codes, my conclusion would be that this is a solution in search of a problem. The case for most of the original control pictures was very marginal and grounded, if I recall, in specific legacy implementations of dumb terminals. Unlike the old host-terminal interfaces, modern debuggers don't send character streams to a dumb device. There is a whole rendering architecture that offers plenty choices for substituting different shapes for certain code points. All that is taking place on a level where the actual 'codes' used for that are not shared or visible, reducing the benefit of standardization. As you can see from my example, the other benefit of standardization, which is a consensus around a specific set of shapes, as you would have, for example for standard math symbols, is also absent, because implementers like to use different techniques - in my example colored dots, arrows and the like for whitespace and fat heavy black rounded rectangles with abbreviations for other control codes. And who knows, the formatting could change -- many debuggers now let you view text data in different modes, for example. A./ |
- Acquiring DIS 10646 Sean Leonard
- RE: Acquiring DIS 10646 Michel Suignard
- Re: Acquiring DIS 10646 Sean Leonard
- Re: Acquiring DIS 10646 Asmus Freytag (t)
- Re: Acquiring DIS 10646 Sean Leonard
- Re: Acquiring DIS 10646 Asmus Freytag (t)
- Re: Acquiring DIS 10646 Doug Ewell
- Re: Acquiring DIS 10646 Janusz S. Bien
- Re: Acquiring DIS 10646 Sean Leonard
- Re: Acquiring DIS 10646 Doug Ewell
- Why Nothing Ever Goes Away (was: Re: Acquiring... Ken Whistler
- Re: Why Nothing Ever Goes Away (was: Re: A... Philippe Verdy
- Re: Why Nothing Ever Goes Away (was: R... Philippe Verdy
- Re: Why Nothing Ever Goes Away Sean Leonard
- Re: Why Nothing Ever Goes Awa... Philippe Verdy
- Re: Why Nothing Ever Goes... Richard Wordingham