View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000568 | luatex | luatex bug | public | 2011-02-04 20:32 | 2015-11-03 16:34 |
| Reporter | phi | Assigned To | Hans Hagen | ||
| Priority | low | Severity | tweak | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.65.0 | ||||
| Fixed in Version | 0.85.0 | ||||
| Summary | 0000568: Inconsistent error handling behavior with virtual fonts | ||||
| Description | When using an invalid command in the fontdata.characters[...].commands table, sometimes an error is issued, sometimes not. For example, when compiling the following document: \directlua{% local virtual = { name = "test", type = "virtual", fonts = { { name = "cmr10", size = 0xA0000 } }, characters = { [0x0061] = { commands = { { "font", 1 }, { "unknown" } } } } } local id = font.define(virtual) font.current(id) } \bye the message "unknown packet command unknown!" is printed and afterward the error "bad argument #-1 to 'define' (number expected, got nil" is raised. If we uncomment the line `{"font", 1},` and/or add a parameter to the "unknown" command (e.g., `{"unknown", 0}`), the error message disappears and LuaTeX exits with return code 0. If would be nice if the error message were printed in all cases, and even better if it were a bit more user-friendly (e.g., using file-line-error style). | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2011-02-04 20:32 | phi | New Issue | |
| 2011-02-10 10:36 | Taco | Status | new => assigned |
| 2011-02-10 10:36 | Taco | Assigned To | => Taco |
| 2014-03-30 11:49 | Hans Hagen | Assigned To | Taco => Hans Hagen |
| 2015-11-03 16:34 | Hans Hagen | Note Added: 0001502 | |
| 2015-11-03 16:34 | Hans Hagen | Status | assigned => closed |
| 2015-11-03 16:34 | Hans Hagen | Resolution | open => fixed |
| 2015-11-03 16:34 | Hans Hagen | Fixed in Version | => 0.85.0 |
