> >What do you think of this syntax which reduces redundant syntactical
> >sugar:
> >
> > classes
> > ClassName A B C D E;
> > EquivalentClass A - E;
> > UppercaseAlphabet @EquivalentClass
> > F - Z;
> > MostEfficient A - Z;
> > Identifier - A - Z a - z;
> >
> >I think we need a trailing comma or something like that to easily
> >support multiline entries (which greatly enhance readability).
>
> Okay. I'll work on it this weekend. My concern was that a trailing
> punctuation mark might be interpreted as a character, although I suppose
> I can work around that.
Ah, my mistake. It should be rather
EquivIdentifier A - Z - a - z ;
(note the space before the final `;') -- can you suggest a better
solution for multi-line entries?
> I'll also substitute the std::map usage for a ptable.
Thanks.
> >Additionally, we need support for handling Unicode ranges:
> >
> > CJKpunct u3000 - u303F;
>
> My intention was that any valid glyph name was to be valid as a
> class character, but name_to_glyph apparently doesn't handle Unicode
> characters. Should I be using a different function, or should I
> extend name_to_glyph?
Please let me first have a look at it (to be done in the next days).
Werner
