May 20, 2010
7:33 a.m.
http://code.google.com/p/pharo/issues/detail?id=2448
As you've noted, we've already done it. It's broken then display of WideStrings with StrikeFonts, since that relied on Wide Characters being stops, which did happen when leadingChar was 255, but not when it's 0. That is manifested in that the rest of the string after a WideChar is rendered as ?'s. There's also an error causing the width of the chars to be wrong, and the first char on the line to be displayed on the previous line instead, but iirc that's not directly related to the stops issue.
Cheers, Henry