| 2014-06-25 17:10:20 |
Jay |
bug |
|
|
added bug |
| 2014-06-25 17:10:20 |
Jay |
attachment added |
|
Image of the bug https://bugs.launchpad.net/bugs/1334363/+attachment/4139161/+files/Screenshot%202014-06-25%2013.09.52.png |
|
| 2014-06-25 18:56:20 |
Paul Sladen |
ubuntu-font-family: status |
New |
Incomplete |
|
| 2014-06-25 19:13:05 |
Jay |
attachment added |
|
Screenshot 2014-06-25 15.12.50.png https://bugs.launchpad.net/ubuntu-font-family/+bug/1334363/+attachment/4139235/+files/Screenshot%202014-06-25%2015.12.50.png |
|
| 2014-06-25 20:01:52 |
Jay |
attachment added |
|
Screenshot 2014-06-25 16.01.42.png https://bugs.launchpad.net/ubuntu-font-family/+bug/1334363/+attachment/4139244/+files/Screenshot%202014-06-25%2016.01.42.png |
|
| 2014-06-25 21:38:16 |
Paul Sladen |
summary |
Apostrophe and quotes displaying as &u2079 (superior 9) |
Apple Keynote 6 Smart Quotes: Apostrophe and quotes displaying as &u2079 (superior 9) |
|
| 2014-06-25 21:43:15 |
Paul Sladen |
ubuntu-font-family: status |
Incomplete |
Invalid |
|
| 2014-06-26 11:28:10 |
Masoud Abkenar |
bug |
|
|
added subscriber Masoud Pourmoosa |
| 2014-06-30 15:25:27 |
Paul Sladen |
ubuntu-font-family: status |
Invalid |
Incomplete |
|
| 2014-07-29 16:48:54 |
Ashley Sheinwald |
bug |
|
|
added subscriber Ashley Sheinwald |
| 2014-07-30 03:22:28 |
Paul Sladen |
summary |
Apple Keynote 6 Smart Quotes: Apostrophe and quotes displaying as &u2079 (superior 9) |
Mavericks OS X 10.9.4: Smart Quotes: Apostrophe and quotes displaying as U+2079 (superior 9) |
|
| 2014-09-28 04:19:57 |
Launchpad Janitor |
ubuntu-font-family: status |
Incomplete |
Expired |
|
| 2014-12-09 00:27:06 |
Adolfo Jayme Barrientos |
description |
When using Ubuntu Font (all weights) in OSX, apostrophes and quotes are displaying as a superior 9. |
When using Ubuntu Font (all weights) in OSX, apostrophes and quotes are displaying as a superior 9.
------------------------ Info from dupe bug 1400534 ------------------------
The Ubuntu-R.ttf file appears to have a broken Unicode cmap subtable, where character U+2019 (single quote) is mapped to glyph 373, which is the superscript 9 glyph. The Apple Roman cmap subtable is correct, and maps it to glyph 111. This leads to inconsistent behaviour in different applications, depending on whether they access the Unicode or Apple Roman cmap subtable.
Further details in this thread: http://www.princexml.com/forum/topic/2867/ubuntu-font-not-rendered-properly
---------------------------------------------------------------------------- |
|
| 2014-12-09 00:27:10 |
Adolfo Jayme Barrientos |
ubuntu-font-family: status |
Expired |
Confirmed |
|
| 2014-12-10 16:37:12 |
Paul Sladen |
ubuntu-font-family: status |
Confirmed |
Incomplete |
|
| 2015-01-28 10:20:15 |
Matthew Paul Thomas |
description |
When using Ubuntu Font (all weights) in OSX, apostrophes and quotes are displaying as a superior 9.
------------------------ Info from dupe bug 1400534 ------------------------
The Ubuntu-R.ttf file appears to have a broken Unicode cmap subtable, where character U+2019 (single quote) is mapped to glyph 373, which is the superscript 9 glyph. The Apple Roman cmap subtable is correct, and maps it to glyph 111. This leads to inconsistent behaviour in different applications, depending on whether they access the Unicode or Apple Roman cmap subtable.
Further details in this thread: http://www.princexml.com/forum/topic/2867/ubuntu-font-not-rendered-properly
---------------------------------------------------------------------------- |
When using Ubuntu Font (all weights) in OSX, apostrophes and quotes are displaying as a superior 9.
Chrome, OS X 10.9.5
1. In Google Docs, set the font to Ubuntu, and type “hello”. (Option+[ for the open quote, Option+] for the close quote.)
What you should get: “hello”
What you actually get: ⁸hello⁹
(From dupe bug 1400534)
The Ubuntu-R.ttf file appears to have a broken Unicode cmap subtable, where character U+2019 (single quote) is mapped to glyph 373, which is the superscript 9 glyph. The Apple Roman cmap subtable is correct, and maps it to glyph 111. This leads to inconsistent behaviour in different applications, depending on whether they access the Unicode or Apple Roman cmap subtable.
Further details in this thread: http://www.princexml.com/forum/topic/2867/ubuntu-font-not-rendered-properly |
|
| 2015-01-28 10:20:46 |
Matthew Paul Thomas |
ubuntu-font-family: status |
Incomplete |
Confirmed |
|
| 2015-01-28 10:20:48 |
Matthew Paul Thomas |
ubuntu-font-family: importance |
Undecided |
High |
|
| 2015-03-02 16:53:46 |
Matthew Paul Thomas |
tags |
|
uff-dmi |
|
| 2015-03-03 08:25:00 |
Matthew Paul Thomas |
summary |
Mavericks OS X 10.9.4: Smart Quotes: Apostrophe and quotes displaying as U+2079 (superior 9) |
Wrong characters appear in some Mac apps ([‘] → [⁸], [’] → [⁹], [–] → [ẃ], [—] → [Ẅ]) |
|
| 2015-03-03 08:26:31 |
Matthew Paul Thomas |
description |
When using Ubuntu Font (all weights) in OSX, apostrophes and quotes are displaying as a superior 9.
Chrome, OS X 10.9.5
1. In Google Docs, set the font to Ubuntu, and type “hello”. (Option+[ for the open quote, Option+] for the close quote.)
What you should get: “hello”
What you actually get: ⁸hello⁹
(From dupe bug 1400534)
The Ubuntu-R.ttf file appears to have a broken Unicode cmap subtable, where character U+2019 (single quote) is mapped to glyph 373, which is the superscript 9 glyph. The Apple Roman cmap subtable is correct, and maps it to glyph 111. This leads to inconsistent behaviour in different applications, depending on whether they access the Unicode or Apple Roman cmap subtable.
Further details in this thread: http://www.princexml.com/forum/topic/2867/ubuntu-font-not-rendered-properly |
When using Ubuntu Font (all weights) in OSX, apostrophes and quotes are displaying as a superior 9.
Chrome, OS X 10.9.5
1. In Google Docs, set the font to Ubuntu, and type “hello”. (Option+[ for the open quote, Option+] for the close quote.)
What you should get: “hello”
What you actually get: ⁸hello⁹
(From dupe bug 1400534)
The Ubuntu-R.ttf file appears to have a broken Unicode cmap subtable, where character U+2019 (single quote) is mapped to glyph 373, which is the superscript 9 glyph. The Apple Roman cmap subtable is correct, and maps it to glyph 111. This leads to inconsistent behaviour in different applications, depending on whether they access the Unicode or Apple Roman cmap subtable.
Further details in this thread: http://www.princexml.com/forum/topic/2867/ubuntu-font-not-rendered-properly
Workaround involving the TransType utility: https://discussions.apple.com/thread/6510381 |
|
| 2015-03-03 08:32:09 |
Matthew Paul Thomas |
description |
When using Ubuntu Font (all weights) in OSX, apostrophes and quotes are displaying as a superior 9.
Chrome, OS X 10.9.5
1. In Google Docs, set the font to Ubuntu, and type “hello”. (Option+[ for the open quote, Option+] for the close quote.)
What you should get: “hello”
What you actually get: ⁸hello⁹
(From dupe bug 1400534)
The Ubuntu-R.ttf file appears to have a broken Unicode cmap subtable, where character U+2019 (single quote) is mapped to glyph 373, which is the superscript 9 glyph. The Apple Roman cmap subtable is correct, and maps it to glyph 111. This leads to inconsistent behaviour in different applications, depending on whether they access the Unicode or Apple Roman cmap subtable.
Further details in this thread: http://www.princexml.com/forum/topic/2867/ubuntu-font-not-rendered-properly
Workaround involving the TransType utility: https://discussions.apple.com/thread/6510381 |
Problem occurs with: Chrome, Pages, Byword, Ulysses; OS X 10.9.4, 10.9.5
When using Ubuntu Font (all weights) in OSX, apostrophes and quotes are displaying as a superior 9.
1. Set the font to Ubuntu (in Chrome, do this in Google Docs)
2. Copy this text, including the quotes:
‘About 8–9 o’clock — but no earlier’
3. Paste it into the app.
What you see: ⁸About 8ẃ9 o⁹clock Ẅ but no earlier⁹
(From dupe bug 1400534)
The Ubuntu-R.ttf file appears to have a broken Unicode cmap subtable, where character U+2019 (single quote) is mapped to glyph 373, which is the superscript 9 glyph. The Apple Roman cmap subtable is correct, and maps it to glyph 111. This leads to inconsistent behaviour in different applications, depending on whether they access the Unicode or Apple Roman cmap subtable.
Further details in this thread: http://www.princexml.com/forum/topic/2867/ubuntu-font-not-rendered-properly
Workaround involving the TransType utility: https://discussions.apple.com/thread/6510381 |
|
| 2015-03-03 08:32:11 |
Matthew Paul Thomas |
ubuntu-font-family: status |
Confirmed |
Triaged |
|
| 2015-03-03 08:34:53 |
Matthew Paul Thomas |
description |
Problem occurs with: Chrome, Pages, Byword, Ulysses; OS X 10.9.4, 10.9.5
When using Ubuntu Font (all weights) in OSX, apostrophes and quotes are displaying as a superior 9.
1. Set the font to Ubuntu (in Chrome, do this in Google Docs)
2. Copy this text, including the quotes:
‘About 8–9 o’clock — but no earlier’
3. Paste it into the app.
What you see: ⁸About 8ẃ9 o⁹clock Ẅ but no earlier⁹
(From dupe bug 1400534)
The Ubuntu-R.ttf file appears to have a broken Unicode cmap subtable, where character U+2019 (single quote) is mapped to glyph 373, which is the superscript 9 glyph. The Apple Roman cmap subtable is correct, and maps it to glyph 111. This leads to inconsistent behaviour in different applications, depending on whether they access the Unicode or Apple Roman cmap subtable.
Further details in this thread: http://www.princexml.com/forum/topic/2867/ubuntu-font-not-rendered-properly
Workaround involving the TransType utility: https://discussions.apple.com/thread/6510381 |
Problem occurs with: Chrome, Keynote, Pages, Byword, Ulysses; OS X 10.9.3, 10.9.4, 10.9.5
Does not occur with: Illustrator, Photoshop, Textmate
When using Ubuntu Font (all weights) in OSX, apostrophes and quotes are displaying as a superior 9.
1. Set the font to Ubuntu (in Chrome, do this in Google Docs)
2. Copy this text, including the quotes:
‘About 8–9 o’clock — but no earlier’
3. Paste it into the app.
What you see: ⁸About 8ẃ9 o⁹clock Ẅ but no earlier⁹
(From dupe bug 1400534)
The Ubuntu-R.ttf file appears to have a broken Unicode cmap subtable, where character U+2019 (single quote) is mapped to glyph 373, which is the superscript 9 glyph. The Apple Roman cmap subtable is correct, and maps it to glyph 111. This leads to inconsistent behaviour in different applications, depending on whether they access the Unicode or Apple Roman cmap subtable.
Further details in this thread: http://www.princexml.com/forum/topic/2867/ubuntu-font-not-rendered-properly
Workaround involving the TransType utility: https://discussions.apple.com/thread/6510381 |
|
| 2015-03-03 09:48:47 |
Matthew Paul Thomas |
description |
Problem occurs with: Chrome, Keynote, Pages, Byword, Ulysses; OS X 10.9.3, 10.9.4, 10.9.5
Does not occur with: Illustrator, Photoshop, Textmate
When using Ubuntu Font (all weights) in OSX, apostrophes and quotes are displaying as a superior 9.
1. Set the font to Ubuntu (in Chrome, do this in Google Docs)
2. Copy this text, including the quotes:
‘About 8–9 o’clock — but no earlier’
3. Paste it into the app.
What you see: ⁸About 8ẃ9 o⁹clock Ẅ but no earlier⁹
(From dupe bug 1400534)
The Ubuntu-R.ttf file appears to have a broken Unicode cmap subtable, where character U+2019 (single quote) is mapped to glyph 373, which is the superscript 9 glyph. The Apple Roman cmap subtable is correct, and maps it to glyph 111. This leads to inconsistent behaviour in different applications, depending on whether they access the Unicode or Apple Roman cmap subtable.
Further details in this thread: http://www.princexml.com/forum/topic/2867/ubuntu-font-not-rendered-properly
Workaround involving the TransType utility: https://discussions.apple.com/thread/6510381 |
Problem occurs with:
Chrome, Keynote, Pages, Byword, Ulysses; OS X 10.9.3–10.9.5
Prince; OS X, Windows 8
Does not occur with:
Illustrator, Photoshop, Textmate
1. Set the font to Ubuntu (in Chrome, do this in Google Docs)
2. Copy this text, including the quotes:
“About 8–9 o’clock — but no earlier”
3. Paste it into the app.
What you see: ⁸About 8ẃ9 o⁹clock Ẅ but no earlier⁹
From dupe bug 1400534:
The Ubuntu-R.ttf file appears to have a broken Unicode cmap subtable, where character U+2019 (single quote) is mapped to glyph 373, which is the superscript 9 glyph. The Apple Roman cmap subtable is correct, and maps it to glyph 111. This leads to inconsistent behaviour in different applications, depending on whether they access the Unicode or Apple Roman cmap subtable.
From <http://www.princexml.com/forum/topic/2867/ubuntu-font-not-rendered-properly#13544>:
macroman 183 maps to glyph 413, but U+2211 maps to glyph 1168
macroman 189 maps to glyph 414, but U+03a9 maps to glyph 949
macroman 206 maps to glyph 109, but U+0152 maps to glyph 360
macroman 207 maps to glyph 121, but U+0153 maps to glyph 372
macroman 208 maps to glyph 115, but U+2013 maps to glyph 361
macroman 209 maps to glyph 116, but U+2014 maps to glyph 362
macroman 210 maps to glyph 112, but U+201c maps to glyph 372
macroman 211 maps to glyph 113, but U+201d maps to glyph 373
macroman 212 maps to glyph 110, but U+2018 maps to glyph 372
macroman 213 maps to glyph 111, but U+2019 maps to glyph 373
macroman 219 maps to glyph 98, but U+00a4 maps to glyph 127
macroman 220 maps to glyph 108, but U+2039 maps to glyph 360
macroman 221 maps to glyph 120, but U+203a maps to glyph 372
macroman 222 maps to glyph 428, but U+fb01 maps to glyph 1170
macroman 223 maps to glyph 430, but U+fb02 maps to glyph 1172
macroman 226 maps to glyph 99, but U+201a maps to glyph 361
macroman 227 maps to glyph 101, but U+201e maps to glyph 361
macroman 246 maps to glyph 105, but U+005e maps to glyph 65
macroman 247 maps to glyph 117, but U+02dc maps to glyph 936
macroman 249 maps to glyph 353, but U+02d8 maps to glyph 1172
macroman 250 maps to glyph 354, but U+02d9 maps to glyph 1173
macroman 251 maps to glyph 355, but U+02da maps to glyph 1174
macroman 253 maps to glyph 357, but U+02dd maps to glyph 1176
macroman 254 maps to glyph 356, but U+02db maps to glyph 1175
macroman 255 maps to glyph 351, but U+02c7 maps to glyph 360
Workaround involving the TransType utility: https://discussions.apple.com/thread/6510381 |
|
| 2015-03-03 14:45:08 |
Matthew Paul Thomas |
summary |
Wrong characters appear in some Mac apps ([‘] → [⁸], [’] → [⁹], [–] → [ẃ], [—] → [Ẅ]) |
[25 mod] Wrong characters appear in some Mac apps ([‘] → [⁸], [’] → [⁹], [–] → [ẃ], [—] → [Ẅ]) |
|
| 2015-03-14 10:46:33 |
mach |
description |
Problem occurs with:
Chrome, Keynote, Pages, Byword, Ulysses; OS X 10.9.3–10.9.5
Prince; OS X, Windows 8
Does not occur with:
Illustrator, Photoshop, Textmate
1. Set the font to Ubuntu (in Chrome, do this in Google Docs)
2. Copy this text, including the quotes:
“About 8–9 o’clock — but no earlier”
3. Paste it into the app.
What you see: ⁸About 8ẃ9 o⁹clock Ẅ but no earlier⁹
From dupe bug 1400534:
The Ubuntu-R.ttf file appears to have a broken Unicode cmap subtable, where character U+2019 (single quote) is mapped to glyph 373, which is the superscript 9 glyph. The Apple Roman cmap subtable is correct, and maps it to glyph 111. This leads to inconsistent behaviour in different applications, depending on whether they access the Unicode or Apple Roman cmap subtable.
From <http://www.princexml.com/forum/topic/2867/ubuntu-font-not-rendered-properly#13544>:
macroman 183 maps to glyph 413, but U+2211 maps to glyph 1168
macroman 189 maps to glyph 414, but U+03a9 maps to glyph 949
macroman 206 maps to glyph 109, but U+0152 maps to glyph 360
macroman 207 maps to glyph 121, but U+0153 maps to glyph 372
macroman 208 maps to glyph 115, but U+2013 maps to glyph 361
macroman 209 maps to glyph 116, but U+2014 maps to glyph 362
macroman 210 maps to glyph 112, but U+201c maps to glyph 372
macroman 211 maps to glyph 113, but U+201d maps to glyph 373
macroman 212 maps to glyph 110, but U+2018 maps to glyph 372
macroman 213 maps to glyph 111, but U+2019 maps to glyph 373
macroman 219 maps to glyph 98, but U+00a4 maps to glyph 127
macroman 220 maps to glyph 108, but U+2039 maps to glyph 360
macroman 221 maps to glyph 120, but U+203a maps to glyph 372
macroman 222 maps to glyph 428, but U+fb01 maps to glyph 1170
macroman 223 maps to glyph 430, but U+fb02 maps to glyph 1172
macroman 226 maps to glyph 99, but U+201a maps to glyph 361
macroman 227 maps to glyph 101, but U+201e maps to glyph 361
macroman 246 maps to glyph 105, but U+005e maps to glyph 65
macroman 247 maps to glyph 117, but U+02dc maps to glyph 936
macroman 249 maps to glyph 353, but U+02d8 maps to glyph 1172
macroman 250 maps to glyph 354, but U+02d9 maps to glyph 1173
macroman 251 maps to glyph 355, but U+02da maps to glyph 1174
macroman 253 maps to glyph 357, but U+02dd maps to glyph 1176
macroman 254 maps to glyph 356, but U+02db maps to glyph 1175
macroman 255 maps to glyph 351, but U+02c7 maps to glyph 360
Workaround involving the TransType utility: https://discussions.apple.com/thread/6510381 |
Problem occurs with:
Chrome, Keynote, Pages, Byword, Ulysses; OS X 10.9.3–10.10.2
Prince; OS X, Windows 8
Does not occur with:
Illustrator, Photoshop, Textmate, Firefox, Safari
1. Set the font to Ubuntu (in Chrome, do this in Google Docs)
2. Copy this text, including the quotes:
“About 8–9 o’clock — but no earlier”
3. Paste it into the app.
What you see: ⁸About 8ẃ9 o⁹clock Ẅ but no earlier⁹
From dupe bug 1400534:
The Ubuntu-R.ttf file appears to have a broken Unicode cmap subtable, where character U+2019 (single quote) is mapped to glyph 373, which is the superscript 9 glyph. The Apple Roman cmap subtable is correct, and maps it to glyph 111. This leads to inconsistent behaviour in different applications, depending on whether they access the Unicode or Apple Roman cmap subtable.
From <http://www.princexml.com/forum/topic/2867/ubuntu-font-not-rendered-properly#13544>:
macroman 183 maps to glyph 413, but U+2211 maps to glyph 1168
macroman 189 maps to glyph 414, but U+03a9 maps to glyph 949
macroman 206 maps to glyph 109, but U+0152 maps to glyph 360
macroman 207 maps to glyph 121, but U+0153 maps to glyph 372
macroman 208 maps to glyph 115, but U+2013 maps to glyph 361
macroman 209 maps to glyph 116, but U+2014 maps to glyph 362
macroman 210 maps to glyph 112, but U+201c maps to glyph 372
macroman 211 maps to glyph 113, but U+201d maps to glyph 373
macroman 212 maps to glyph 110, but U+2018 maps to glyph 372
macroman 213 maps to glyph 111, but U+2019 maps to glyph 373
macroman 219 maps to glyph 98, but U+00a4 maps to glyph 127
macroman 220 maps to glyph 108, but U+2039 maps to glyph 360
macroman 221 maps to glyph 120, but U+203a maps to glyph 372
macroman 222 maps to glyph 428, but U+fb01 maps to glyph 1170
macroman 223 maps to glyph 430, but U+fb02 maps to glyph 1172
macroman 226 maps to glyph 99, but U+201a maps to glyph 361
macroman 227 maps to glyph 101, but U+201e maps to glyph 361
macroman 246 maps to glyph 105, but U+005e maps to glyph 65
macroman 247 maps to glyph 117, but U+02dc maps to glyph 936
macroman 249 maps to glyph 353, but U+02d8 maps to glyph 1172
macroman 250 maps to glyph 354, but U+02d9 maps to glyph 1173
macroman 251 maps to glyph 355, but U+02da maps to glyph 1174
macroman 253 maps to glyph 357, but U+02dd maps to glyph 1176
macroman 254 maps to glyph 356, but U+02db maps to glyph 1175
macroman 255 maps to glyph 351, but U+02c7 maps to glyph 360
Workaround involving the TransType utility: https://discussions.apple.com/thread/6510381 |
|
| 2015-04-27 12:23:44 |
Dominik Röttsches |
bug |
|
|
added subscriber Dominik Röttsches |
| 2015-05-08 15:08:37 |
Michael Rawling |
bug |
|
|
added subscriber Michael Rawling |
| 2015-05-08 18:32:25 |
Paul Sladen |
bug |
|
|
added subscriber Magdalena Mirowicz |
| 2015-06-07 16:43:03 |
Matthew Paul Thomas |
bug watch added |
|
http://code.google.com/p/chromium/issues/detail?id=426056 |
|
| 2015-06-07 16:43:03 |
Matthew Paul Thomas |
bug task added |
|
chromium-browser |
|
| 2015-06-08 22:37:22 |
Stephen Stewart |
bug |
|
|
added subscriber Stephen Stewart |
| 2015-06-30 16:00:31 |
Matthew Paul Thomas |
attachment added |
|
screenshots of the current version (top) and pre-release version (bottom) https://bugs.launchpad.net/ubuntu-font-family/+bug/1334363/+attachment/4422500/+files/1334363-Ubuntu-font-mapping.png |
|
| 2015-06-30 16:00:39 |
Matthew Paul Thomas |
ubuntu-font-family: status |
Triaged |
In Progress |
|
| 2015-07-19 20:29:36 |
thebitguru |
bug |
|
|
added subscriber thebitguru |
| 2015-07-27 10:21:34 |
Iain Lane |
bug |
|
|
added subscriber Iain Lane |
| 2015-07-27 12:04:10 |
Magdalena Mirowicz |
attachment added |
|
2015-07-10_Ubuntu-0.83.zip https://bugs.launchpad.net/ubuntu-font-family/+bug/1334363/+attachment/4434614/+files/2015-07-10_Ubuntu-0.83.zip |
|
| 2015-07-27 12:24:52 |
Paul Sladen |
attachment removed |
2015-07-10_Ubuntu-0.83.zip https://bugs.launchpad.net/ubuntu-font-family/+bug/1334363/+attachment/4434614/+files/2015-07-10_Ubuntu-0.83.zip |
|
|
| 2015-07-27 12:30:41 |
Paul Sladen |
ubuntu-font-family: status |
In Progress |
Fix Committed |
|
| 2015-07-30 15:00:19 |
Jay |
removed subscriber Jay |
|
|
|
| 2015-07-30 15:00:22 |
Jay |
bug |
|
|
added subscriber Jay |
| 2015-07-30 15:00:29 |
Jay |
removed subscriber Jay |
|
|
|
| 2015-08-18 16:34:25 |
Magdalena Mirowicz |
ubuntu-font-family: milestone |
|
0.92-beta-test |
|
| 2015-08-19 08:55:35 |
Magdalena Mirowicz |
ubuntu-font-family: milestone |
0.92-beta-test |
latin-c |
|
| 2015-08-19 08:55:39 |
Magdalena Mirowicz |
ubuntu-font-family: milestone |
latin-c |
0.83-mac-bug-fix |
|
| 2015-08-21 17:09:32 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-branches/ubuntu/wily/ubuntu-font-family-sources/wily-proposed |
|
| 2015-09-21 14:49:35 |
Magdalena Mirowicz |
ubuntu-font-family: status |
Fix Committed |
Fix Released |
|
| 2016-01-08 07:00:10 |
Daniel Friesen |
bug |
|
|
added subscriber Daniel Friesen |
