| 2010-09-16 16:15:25 |
Paul Sladen |
bug |
|
|
added bug |
| 2010-09-16 16:15:41 |
Paul Sladen |
ubuntu-font-family: status |
New |
Confirmed |
|
| 2010-09-16 16:15:45 |
Paul Sladen |
ubuntu-font-family: importance |
Undecided |
High |
|
| 2010-09-16 16:15:53 |
Paul Sladen |
ubuntu-font-family: assignee |
|
Shiraaz Gabru (shiraaz) |
|
| 2010-09-16 16:15:56 |
Paul Sladen |
ubuntu-font-family: milestone |
|
0.70 |
|
| 2010-09-16 16:16:09 |
Paul Sladen |
tags |
|
uff-pua uff-regression |
|
| 2010-09-21 17:46:12 |
Shiraaz Gabru |
ubuntu-font-family: importance |
High |
Low |
|
| 2010-09-22 04:09:31 |
Paul Sladen |
attachment added |
|
reinject-version.py https://bugs.launchpad.net/ubuntu-font-family/+bug/640623/+attachment/1620990/+files/reinject-version.py |
|
| 2010-09-30 10:37:15 |
Paul Sladen |
ubuntu-font-family: milestone |
0.70 |
later |
|
| 2010-09-30 10:37:19 |
Paul Sladen |
ubuntu-font-family: assignee |
Shiraaz Gabru (shiraaz) |
|
|
| 2010-11-19 13:42:51 |
Paul Sladen |
summary |
Restore debug glyphs (Weight and version) in PUA |
Restore version debug glyph in PUA |
|
| 2010-11-19 13:48:26 |
Paul Sladen |
description |
The debug glyphs in the PUA have been removed. This prevents accurate point-of-user detection from user bug reports. |
Currently the 0.69 can be identified in rendering screenshots as it is the only version without a version number glyph.
In order to tell 0.70 uniquely apart, in screenshots and regardless of metadata, this needs to be present.
It should be possible to build this using the superscript/subscript glyphs to build a composite so that it is very obvious what it is and can't be mistaken for normal prose: Eg, within a normal EM square it should be possible to have something like:
v 0
.70
it doesn't matter if these glyphs overlap each other---indeed this makes it easy to distinguish it has the version symbol and not something that a user can create (or fake) easily with text.
This should be (re-)generated by a script in a similar manner to the glyphs used for the CASE implementation (bug #676538) and once the codepoint entry and bounding-box are reinserted updating is trival. |
|
| 2010-11-19 13:48:32 |
Paul Sladen |
ubuntu-font-family: importance |
Low |
High |
|
| 2010-11-19 13:48:41 |
Paul Sladen |
ubuntu-font-family: assignee |
|
Malcolm Wooden (malcolm-daltonmaag) |
|
| 2010-11-19 13:48:46 |
Paul Sladen |
ubuntu-font-family: milestone |
later |
0.70 |
|
| 2010-11-19 13:48:57 |
Paul Sladen |
summary |
Restore version debug glyph in PUA |
Technical: Restore version debug glyph in PUA |
|
| 2010-11-19 13:49:33 |
Paul Sladen |
description |
Currently the 0.69 can be identified in rendering screenshots as it is the only version without a version number glyph.
In order to tell 0.70 uniquely apart, in screenshots and regardless of metadata, this needs to be present.
It should be possible to build this using the superscript/subscript glyphs to build a composite so that it is very obvious what it is and can't be mistaken for normal prose: Eg, within a normal EM square it should be possible to have something like:
v 0
.70
it doesn't matter if these glyphs overlap each other---indeed this makes it easy to distinguish it has the version symbol and not something that a user can create (or fake) easily with text.
This should be (re-)generated by a script in a similar manner to the glyphs used for the CASE implementation (bug #676538) and once the codepoint entry and bounding-box are reinserted updating is trival. |
Currently the 0.69 can be identified in rendering screenshots as it is the only version without a version number glyph.
In order to tell 0.70 uniquely apart, in screenshots and regardless of metadata, this needs to be present.
It should be possible to build this using the superscript/subscript glyphs to build a composite so that it is very obvious what it is and can't be mistaken for normal prose: Eg, within a normal EM square it should be possible to have something like:
v 0
.70
it doesn't matter if these glyphs overlap each other---indeed this makes it easy to distinguish it as the version symbol and not something that a user can create (or fake) easily with text.
This should be (re-)generated by a script in a similar manner to the glyphs used for the CASE implementation (bug #676538) and once the codepoint entry and bounding-box are reinserted updating is trival.
|
|
| 2010-11-19 14:30:41 |
Shiraaz Gabru |
ubuntu-font-family: status |
Confirmed |
Fix Committed |
|
| 2010-12-14 04:33:59 |
Paul Sladen |
ubuntu-font-family: status |
Fix Committed |
Fix Released |
|
| 2010-12-14 06:15:47 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/ubuntu-font-family-sources |
|
