Jason White, le Mon 11 Aug 2008 18:59:48 +1000, a écrit :
> If the characters involved are defined in Unicode to be equivalent, as with
> combining characters and the accented letters, then I can't think of a good
> reason to distinguish them at the level of the table.
All the more so since for vi
On Sat, Aug 09, 2008 at 03:55:10PM +0200, Mario Lang wrote:
> > 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.
Perhaps an option in the table could be provided to turn normalization
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Mario Lang, le Sat 09 Aug 2008 10:55:00 +0200, a écrit :
>> Jason White <[EMAIL PROTECTED]> 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
>>
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Hello,
>
> Mario Lang, le Sat 09 Aug 2008 07:03:32 +0200, a écrit :
>> One example that kind of interests me is the international phonetic
>> alphabet, which is used on Wikipedia sometimes. A mapping
>> for that would be useful...
>
> I have an experi
Samuel Thibault <[EMAIL PROTECTED]> writes:
> Mario Lang, le Sat 09 Aug 2008 07:03:32 +0200, a écrit :
>> 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.
>
> Well, there are all the spacing characters for i
Jason White, le Sat 09 Aug 2008 16:15:23 +1000, a écrit :
> 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. Techniques for doing this, and very likely working
> code
Mario Lang, le Sat 09 Aug 2008 10:55:00 +0200, a écrit :
> Jason White <[EMAIL PROTECTED]> 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 n
Mario Lang, le Sat 09 Aug 2008 07:03:32 +0200, a écrit :
> 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.
Well, there are all the spacing characters for instance: breakable,
non-breakable, half, thin, etc.
Hello,
Mario Lang, le Sat 09 Aug 2008 07:03:32 +0200, a écrit :
> One example that kind of interests me is the international phonetic
> alphabet, which is used on Wikipedia sometimes. A mapping
> for that would be useful...
I have an experimental one for that.
Samuel
___
Jason White <[EMAIL PROTECTED]> 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
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" character
[quoted lines by Mario Lang on 2008/08/09 at 07:03 +0200]
>I think it might be useful to define a lot more unicode characters since the
>screen font can be switched pretty easily. Besides, while there is this 512
>limitation on linux console, BrlAPI clients like Orca can feed unicode
>characte
Dave Mielke <[EMAIL PROTECTED]> writes:
>>> On first sight, this looks wrong. Given that we have 2^8 possible
>>> chars and 2^8 possible dot-patterns, we shouldn't reuse the
>>> same dot pattern for two different characters.
>
> We actually now have way more than that since the tables have become
Dave Mielke <[EMAIL PROTECTED]> wrote:
> [quoted lines by Hermann on 2008/08/08 at 11:07 +0200]
>
[...]
>>> On first sight, this looks wrong. Given that we have 2^8 possible
>>> chars and 2^8 possible dot-patterns, we shouldn't reuse the
>>> same dot pattern for two different characters.
>>You are
[quoted lines by Hermann on 2008/08/08 at 11:07 +0200]
>Wasn't this corrected to "§" due to my suggestion?
Yes, it was. I guess, with all this table conversion, I accidentally lost it.
>> char \xB6 (12345678) # ⣿ ¶ [PILCROW SIGN]
>>
>What does that mean?
It's a paragraph sign, as opposed to th
On 08.08.2008 at 12:32:17 Samuel Thibault <[EMAIL PROTECTED]> wrote:
> Hermann, le Fri 08 Aug 2008 11:07:38 +0200, a écrit :
>> On 08.08.2008 at 10:52:30 Mario Lang <[EMAIL PROTECTED]> wrote:
>> > While skimming over the new converted de.ttb file in
>> > the dev repo, I noticed the following:
>> >
Hermann, le Fri 08 Aug 2008 11:07:38 +0200, a écrit :
> On 08.08.2008 at 10:52:30 Mario Lang <[EMAIL PROTECTED]> wrote:
> > While skimming over the new converted de.ttb file in
> > the dev repo, I noticed the following:
> >
> > char \xA7 (12345678) # ⣿ § [SECTION SIGN]
>
> Wasn't this corrected t
On 08.08.2008 at 10:52:30 Mario Lang <[EMAIL PROTECTED]> wrote:
> Hi.
>
> While skimming over the new converted de.ttb file in
> the dev repo, I noticed the following:
>
> char \xA7 (12345678) # ⣿ § [SECTION SIGN]
Wasn't this corrected to "§" due to my suggestion?
> char \xB6 (12345678) # ⣿ ¶
18 matches
Mail list logo
