linux-traipu team mailing list archive

[Steven <steven@xxxxxxxx>]

Hi everyone,

I'm actually having the same issue with sketch.

@Paul : Do you have an idea of when the new font would be released ?
It's very hard to work on this way ! :)

Thanks for your research anyway, i thought i was an isolated case.

Steven

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1334363

Title:
  [25 mod] Wrong characters appear in some Mac apps ([‘] → [⁸], [’] →
  [⁹], [–] → [ẃ], [—] → [Ẅ])

Status in Chromium Browser:
  Unknown
Status in Ubuntu Font Family:
  In Progress

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1334363/+subscriptions