| 1 |
From: Guylhem AZNAR <[email protected]>, GPL |
| 2 |
|
| 3 |
Basically, lat is psf, latu is psfu (currency is replaced by EURO), latv |
| 4 |
is pure unicode (currency will not be replaced by EURO symbol, only |
| 5 |
unicode EURO are replaced) and latw replaces unicode EURO and currency |
| 6 |
by EURO. |
| 7 |
|
| 8 |
Here's a chart, please tell me if it isn't clear enough (I wanted font |
| 9 |
support to become exhaustive since many people asked for special |
| 10 |
replacement of currency or instead non replacement since they already |
| 11 |
use UNICODE, etcetera......) |
| 12 |
|
| 13 |
| Iso encoding | Unicode map | Single | Cross |
| 14 |
| within font | included | compatibility | compatibility |
| 15 |
------------------------------------------------------------------- |
| 16 |
lat9 | y | n | n | lat1 + lat9 |
| 17 |
------------------------------------------------------------------- |
| 18 |
lat9u | n | y | n | lat1 + lat9 |
| 19 |
------------------------------------------------------------------- |
| 20 |
lat9v | y | y | unicode | n |
| 21 |
------------------------------------------------------------------- |
| 22 |
lat9w | y | y | n | lat1 + lat9 |
| 23 |
| | | | + unicode |
| 24 |
------------------------------------------------------------------- |
| 25 |
|
| 26 |
* lat9 fonts do not include any unicode translation map, |
| 27 |
therefore each currency sign will look like euro, what could cause |
| 28 |
compatibility problems for files coming from windows computers (cp1252 or |
| 29 |
latin1 are "incompatible" with latin9) but the huge advantage is it works |
| 30 |
right now with linux. |
| 31 |
|
| 32 |
* lat9u fonts are encoded in a non standard sequence (but |
| 33 |
identical to latXu fonts from kbd) compared to the latter, therefore it |
| 34 |
brings the same problems with cp1252 and latin1 but the unicode translation |
| 35 |
map allows nice chars. for semi graphical applications like Yast, mc or |
| 36 |
other ncurses or dialog based programs. |
| 37 |
|
| 38 |
* lat9v encoded in iso official sequence just like lat9 but |
| 39 |
with a full fledged unicode translation map, so no currency sign will be |
| 40 |
replaced by euro |
| 41 |
This avoids export problems if you use pure unicode and a unicode keymap : |
| 42 |
each latin9 char. is replaced by the adequate unicode char. and then |
| 43 |
displayed what is not only technically elegant but also useless with |
| 44 |
"standard" linux console. Very few systems are unicode ready ! |
| 45 |
|
| 46 |
Therefore only use lat9, lat9u or lat9v fonts if you know what you are |
| 47 |
doing, else you can go with lat9w, the best compromise : you can |
| 48 |
be latin9 compatible immediately. |
| 49 |
There is no obligation of unicode or whatever, semi graphical chars. are |
| 50 |
not messed up and if you feel like trying unicode, latin9 chars are |
| 51 |
displayed correctly (only the 0.3% latin9 incompatible chars. from latin1 |
| 52 |
lack) |
| 53 |
|
| 54 |
You do not need to understand anything to use euro in everyday life, and if |
| 55 |
you still hesitate, trust my choice : lat9w. |
| 56 |
|
| 57 |
In order to use lat9-16.psf (or another lat9 .psf), you must supply a |
| 58 |
unicode map : |
| 59 |
|
| 60 |
loadunimap lat9.uni |
| 61 |
setfont lat9-16.psf |
| 62 |
|
| 63 |
To use lat9w-16.psf (or another lat9u, lat9v or lat9w) : |
| 64 |
|
| 65 |
setfont lat9w-16.psf |