On 13/12/2015 07:04, Werner LEMBERG wrote:
>
> [XeTeX 3.14159265-2.6-0.2 (TeX Live 2015)]
>
>
> Folks,
>
>
> I'm updating the `ucharclasses.sty' to completely cover Unicode. This
> style file maps Unicode character blocks to character classes, and
> I've hit the 256 entry limit of \XeTeXc
Getting those up to 16 bits would be fantastic. There is some PR
activity on https://github.com/Pomax/ucharclasses right now to get
things fitting Unicode 8, if that's hitting the limitations of XeTeX,
then that feels like something worth having a look at.
-- Pomax
On 12/12/2015 11:04 PM, Wer
On 13/12/15 02:04, Werner LEMBERG wrote:
[XeTeX 3.14159265-2.6-0.2 (TeX Live 2015)]
Folks,
I'm updating the `ucharclasses.sty' to completely cover Unicode. This
style file maps Unicode character blocks to character classes, and
I've hit the 256 entry limit of \XeTeXcharclass...
Any cha
But my first reaction to the question is to ask whether Unicode
character blocks are the most useful thing to map. They're rather
arbitrary, with things like Latin script split up across numerous
blocks largely due to historical accident.
Mapping the Script property to char classes would see
On 14/12/2015 04:31, Jonathan Kew wrote:
> Probably, at least in principle; I don't remember the code offhand to
> know how easy/difficult this might be.
Here's the relevant code:
p:=cur_chr; scan_usv_num;
p:=p+cur_val;
n:=sf_code(cur_val) mod @"1;
scan_optional_equals
On 13 December 2015 at 07:04, Werner LEMBERG wrote:
>
> [XeTeX 3.14159265-2.6-0.2 (TeX Live 2015)]
>
>
> Folks,
>
>
> I'm updating the `ucharclasses.sty' to completely cover Unicode. This
> style file maps Unicode character blocks to character classes, and
> I've hit the 256 entry limit of \X
