It's certainly possible to limit the number of default transitions, but
with the ever increasing expanse that is Unicode, while it might seem
unrealistic, really it's more a matter of time until someone actually
needs more classes than are currently available
There is an obvious optimization as per Jonathan's suggestion to
collapse multiple blocks to scripts instead, to bring down the number of
required classes used in the package, but also remember that
ucharclasses is just one package; if someone uses additional packages
that rely on allocating classes to achieve some goal, then having only
255 (sans xetex-reserved classes) may become not enough much faster than
if it's only used for the transition triggers that ucharclasses offers.
- Pomax
On 12/14/2015 11:02 AM, Werner LEMBERG wrote:
<<Don't you only need to allocate a class to a block for which a
transition is specified, so 256 should only be a problem if you need
to specify that many transitions?>>
I guess this would need a complete rewrite of the ucharclasses package
(so Michiel should answer :-), but yes, such an approach could solve
the issue.
Regardless of that, I think that \XeTeXcharclass should allow more
than 256 registers.
Werner
--------------------------------------------------
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
