Timeline for How to adjust font features in LuaTeX?
Current License: CC BY-SA 4.0
21 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 28, 2020 at 15:25 | comment | added | Ulrike Fischer | @Someone I approved the edit, but I would really prefer if you don't do such cosmetics edits which don't add anything useful to an four years old answer and cost only time to review. | |
| S Aug 28, 2020 at 15:19 | history | edited | Ulrike Fischer | CC BY-SA 4.0 |
I don't have a summary
|
| S Aug 28, 2020 at 15:19 | history | suggested | Someone | CC BY-SA 4.0 |
I don't have a summary
|
| Aug 28, 2020 at 15:15 | review | Suggested edits | |||
| S Aug 28, 2020 at 15:19 | |||||
| Feb 28, 2017 at 8:41 | comment | added | Yan Zhou | I agree, the syntax is a bit confusing, regarding to glyph names. As to unit of "-200", I believe it is standard PS unit, that is 1 thousandth of em, and -200 is -20% type size | |
| Feb 9, 2017 at 9:39 | history | edited | Ulrike Fischer | CC BY-SA 3.0 |
added 683 characters in body
|
| Oct 7, 2016 at 7:40 | comment | added | Paolo Polesana | @HenriMenke I also found that in some position of the string some names are consistent, while in other not: in defining a ligature ['Iacute'] = { "afii10026", "acutecmb"} does not apply. The glyph names are taken from the Adobe standard. After some trials I found that ['Iacute'] = { "И", 0x0301} works perfectly. Here I had to mix 'direct typing' (cyrillic И type) and this '0x0301' unicode standard... How to understand it? I didn't even know there was so many ways to call a type!!! | |
| Oct 7, 2016 at 7:35 | comment | added | Henri Menke | @PaoloPolesana The problem is that the fonts are a mess here. Naming is highly inconsistent. | |
| Oct 7, 2016 at 6:50 | comment | added | Paolo Polesana | @HenriMenke Thank you: anyway I'm still confused... I see a lot of way to call the characters it these examples: "A", [0x0041], 'f_i' for ligatures, also 'iacute' from Adobe glyph names, "Q.alt01", "uni1E9E.smcp"... This is for me a complete mess! I need some reference to order my knowledge... | |
| Oct 7, 2016 at 6:41 | comment | added | Paolo Polesana | @UlrikeFischer Defining a ligature, I found that the string ['Iacute'] = { "afii10026", "acutecmb"} does not apply. The glyph names are taken from the Adobe standard. After some trials I found that ['Iacute'] = { "И", 0x0301} works perfectly. So: some glyph names are accepted, while other not. Which is the standard? | |
| Oct 6, 2016 at 19:27 | comment | added | Ulrike Fischer | @PaoloPolesana: My example use glyph names ("A"), so I don't understand the question. | |
| Oct 6, 2016 at 19:19 | comment | added | Henri Menke | @PaoloPolesana Yes, you can. For a simple example see this answer of mine (it is a ConTeXt answer but the Lua part will stay the same for LaTeX). | |
| Oct 6, 2016 at 14:45 | comment | added | Paolo Polesana | @HenriMenke Simple question from an ignorant: is there any way to use glyph names instead of unicode like [0x0041] as argument of data = {...} ? | |
| Jun 25, 2016 at 20:12 | comment | added | Ulrike Fischer |
@Thérèse: You should add the W-setting to the existing table for A. ["A"] = { ["V"] = -200 , ["W"] = -200 }, (but curiously the 200 leads to a much larger kerning now.)
|
|
| Jun 25, 2016 at 20:05 | comment | added | Thérèse |
Just noticed something very strange: if I try to adjust the kerning of a second pair of letters by adding the line ["A"] = { ["W"] = -200 }, after ["A"] = { ["V"] = -200 }, the adjustment to the pair “AV” vanishes.
|
|
| May 31, 2016 at 9:13 | comment | added | Henri Menke | I have checked again and the units of kerning are (as in the feature files) 1/1000em. | |
| May 31, 2016 at 9:07 | comment | added | Henri Menke |
I experimented a bit: The description string "extra kerns" seems to be optional (nothing happens when I leave it out). When I use name = "kern", the feature is automatically applied together with all other entries in the kern feature. This seems more convenient than having to declare an extra feature. So far, I haven't found out how to make vertical kerning work (a.k.a. positioning in the feature files), how to adjust kerning around a single character, and how to adjust kerning when the partner is a space (I can't choose 0x0020, because space in TeX is handled differently).
|
|
| May 30, 2016 at 8:37 | comment | added | Ulrike Fischer | @HenriMenke: As you saw in the context list answer you can get quite fast working code from Hans to specific questions. What you seldom get it good documentation. It is even unclear if the interface is stable. So it is up to us to improve the situation. Imho we should try to extend this question and its answers to a definite "how to manipulate kernings" reference. And create more questions for other handlers. | |
| May 30, 2016 at 8:21 | comment | added | Henri Menke | BTW: In the feature file syntax -200 would correspond to -200/1000em. | |
| May 30, 2016 at 8:17 | comment | added | Henri Menke |
Thank you very much for solving the specific example from my question! The actual question however is, whether we can have a review of what is possible and how it can be done with fonts.handlers. The issue of the syntax not being final is minor, as an answer can always be updated later.
|
|
| May 30, 2016 at 8:08 | history | answered | Ulrike Fischer | CC BY-SA 3.0 |