{6} All Tickets By Milestone (Including closed) (7 matches)
A more complex example to show how to make advanced reports.
| Ticket | Summary | Component | Status | Resolution | Version | Type | Priority | Owner | Modified |
|---|---|---|---|---|---|---|---|---|---|
| #5 | glifLib fails reading the xml of a .glif if a non-ascii character is present in the anchor.name. | component1 | new | None | defect | major | just | 12/15/08 | |
| #7 | Possible glifname clash with glyphNameToShortFileName | component1 | new | None | defect | minor | erik | 06/22/10 | |
| #6 | Default glyph namer in glifLib.py fails to distinguish T_h and T_H | component1 | closed | fixed | defect | critical | erik, just | 03/27/09 | |
| #4 | Importing a UFO with certain blue zone settings can cause a traceback in FontLab | component1 | closed | fixed | defect | minor | erik | 07/14/08 | |
| #3 | Data/GlyphConstructions.txt missing in OSX package installer | component1 | closed | fixed | task | major | erik | 03/11/08 | |
| #2 | UFO import/export bug in a mixed RoboFab environment | component1 | closed | fixed | defect | major | Erik | 02/21/08 | |
| #1 | Traceback in exporting a UFO from FontLab Studio 5, with non-ascii char in a glyph.note. | component1 | closed | fixed | defect | minor | somebody | 02/02/08 |
Note: See TracReports for help on using and
creating reports.
