| 1 |
=========================================================== |
| 2 |
= |
| 3 |
= THIS PACKAGE IS IN NEED OF A MAINTAINER = |
| 4 |
= SEE https://github.com/Pomax/ucharclasses/issues/23 = |
| 5 |
= |
| 6 |
=========================================================== |
| 7 |
|
| 8 |
|
| 9 |
ucharclasses package for XeLaTex |
| 10 |
-------------------------------------- |
| 11 |
Michiel Kamermans, v2.6, October 2022 |
| 12 |
|
| 13 |
The brief |
| 14 |
--------- |
| 15 |
|
| 16 |
Sometimes you don't want to have to bother with font |
| 17 |
switching just because you're using languages that are |
| 18 |
distinct enough to use different unicode blocks, but |
| 19 |
aren't covered by the polyglossia package. Where normal |
| 20 |
word processing packages such as Microsoft Word or |
| 21 |
OpenOffice Writer handle this for you, LATEX (because it |
| 22 |
needs you to tell it what to do) has no default behaviour |
| 23 |
for this, and so we arrive at a need for a package that |
| 24 |
does this for us. You probably already discovered that |
| 25 |
regular LATEX has no understanding of unicode, and ended |
| 26 |
up going for Xe(La)TeX as your TeX compiler of choice, |
| 27 |
which means you now have two excellent resources available: |
| 28 |
fontspec, and ucharclasses. |
| 29 |
|
| 30 |
The first of these lets you pick fonts based on what your |
| 31 |
system calls them, without needing to do anything special |
| 32 |
such as turning them into metafonts. This is convenient, |
| 33 |
user friendly, and the way of the future (at least, it |
| 34 |
should be). |
| 35 |
|
| 36 |
The second lets you define what should happen when your |
| 37 |
text changes from a character in one unicode block, to a |
| 38 |
character in another. This is also convenient, and paired |
| 39 |
with fontspec it offers automatic font switching in the |
| 40 |
same way that normal Office applications perform, with |
| 41 |
one big difference: you stay in control. If at some point |
| 42 |
you need the switch rule to do something different, |
| 43 |
you will be out of luck using an Office application. |
| 44 |
In Xe(La)TeX, you stay on top of things and still get to |
| 45 |
say exactly what happens, and when. |
| 46 |
|
| 47 |
So what is it? |
| 48 |
-------------- |
| 49 |
|
| 50 |
This package sets up XeTeX character classes based on |
| 51 |
which unicode block a character is found in. It then |
| 52 |
allows transition rules to be defined when entering or |
| 53 |
leaving particular unicode blocks, the code of which |
| 54 |
gets inserted automatically when a transition from a |
| 55 |
character from one unicode block to a character from |
| 56 |
another unicode block is encountered by XeTeX |
| 57 |
|
| 58 |
Unicode Compatibility |
| 59 |
--------------------- |
| 60 |
|
| 61 |
Current compatibility is Unicode 15.0 |
| 62 |
|
| 63 |
Changelog |
| 64 |
--------- |
| 65 |
|
| 66 |
v2.6: Unicode 15 support |
| 67 |
v2.5: Unicode 14 support |
| 68 |
v2.4: Unicode 11, 12, and 13 support |
| 69 |
v2.3: Unicode 10 support |
| 70 |
v2.2: Unicode 8.0 and LaTeX2e support |
| 71 |
v2.1: Uplift for the updates introduced in XeTeX 0.99994 |
| 72 |
v2.0: Rewritten to Vastly improve performance + Unicode 6.0 |
| 73 |
v1.0: Unicode block switching using XeTeX intercharclasses. |
| 74 |
|
| 75 |
Contributors |
| 76 |
------------ |
| 77 |
|
| 78 |
v2.5-2.6: Werner Lemberg |
| 79 |
v2.4: Werner Lemberg, Shreeshrii |
| 80 |
v2.1-2.3: Qing Lee, Werner Lemberg |
| 81 |
v2.0: Enrico Gregorio |
| 82 |
v1.0: Mike "Pomax" Kamermans |
| 83 |
|
| 84 |
License? |
| 85 |
-------- |
| 86 |
|
| 87 |
Public Domain |
| 88 |
https://www.ctan.org/license/pd |
| 89 |
|
| 90 |
Repository? |
| 91 |
----------- |
| 92 |
|
| 93 |
https://github.com/Pomax/ucharclasses |