[BRLTTY] de.ttb
Mario Lang
mlang at delysid.org
Sat Aug 9 09:55:10 EDT 2008
Samuel Thibault <samuel.thibault at ens-lyon.org> writes:
> Mario Lang, le Sat 09 Aug 2008 10:55:00 +0200, a écrit :
>> Jason White <jason at jasonjgw.net> writes:
>> > On Sat, Aug 09, 2008 at 01:30:12AM -0400, Dave Mielke wrote:
>> >
>> >> >There are other things like certain symbols are kind of duplicated in Unicode.
>> >> >But I cant think of any right now, I'd need to check.
>> >
>> > As I remember, accented letters are among these: there are so-called
>> > "combining" characters that allow the letter and the accent to be specified
>> > separately, as well as characters that represent the accented letters as
>> > single, combined entities.
>>
>> Well, a separate character would mean that one representation uses more
>> cells than another, right? Normalising that sounds wrong.
>
> Yes and no. The combining character doesn't take room on the screen.
> So for instance é (e with acute accent) and é (e + combining acute
> accent), although different strings, normalize to the same, and for a
> good reason: they appear exactly the same on my screen, occupying only
> one column.
Oh, that makes good sense then. Thanks for explaining.
>> > One solution to this is to "normalize" the Unicode string before it reaches
>> > the braille translation functions, so that only one representation is ever
>> > used for those characters.
>>
>> If DESCCHAR still returns the original character value, I agree. If not,
>> I disagree... DESCCHAR should always report the actual character...
>
> I agree with you. The normalization should only happen just before the
> output.
I.e., in a table, which sort of brings us back to Dave's equivalence idea.
--
CYa,
⡍⠁⠗⠊⠕ | Debian Developer <URL:http://debian.org/>
.''`. | Get my public key via finger mlang/key at db.debian.org
: :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
`. `'
`- <URL:http://delysid.org/> <URL:http://www.staff.tugraz.at/mlang/>
More information about the BRLTTY
mailing list