On Wed, 30 Dec 2009 22:57:06 +0100 Johnny Rosenberg <[email protected]> dijo:
>I have a calc document created with earlier versions of >OpenOffice.org, for example OpenOffice.org 3.1. When I opened the file >with OpenOffice.org 3.2 RC1 I noticed that some characters was >”invisible”. I couldn't see them in the cells and I couldn't see them >in the input line. > >Font: FreeSans >Characters: ₍₎⁽⁾₊⁺₋⁻ > >If you can't see them, they are: >Left parenthesis subscript (U+208D) >Right parenthesis subscript (U+208E) >Left parenthesis superior (U+207D) >Right parenthesis superior (U+207E) >Plus subscript (U+208A) >Plus superior (U+207A) >Minus subscript (U+208B) >Minus superior (U+207B) > >I changed the font to DejaVuSans and the characters appeared again. I >also tried a few different font, but they all work except my favourite >font FreeSans. > >All the caracters look fine with FreeSans in older versions of >OpenOffice.org and I also tried with gedit. Worked fine there too. > >Can anyone confirm (or deny) that this is a bug in OpenOffice.org 3.2 >RC1? First, I understand that 3.2 will finally include support for OpenType fonts on Linux. If I am correct, then I must assume that there has been some significant code rewriting for font handling. In other words, it would not surprise me to see a bug. When I read your post my initial reaction was that OOo 3.2 was no longer faking missing glyphs. I have not tried 3.2 yet, but I know in 3.1 and earlier versions OOo would sometimes substitute a glyph from another font. How and why it does this has always been a mystery to me, but it drives me bats when I copy text from a Writer document into a Scribus document. Scribus rigorously will never fake a glyph. Therefore, if Free Sans lacked the glyph, your 3.1 would have faked it, but 3.2 would not. At least, that was my initial suspicion. But I have Free Sans also and I just checked it with Fontmatrix. It does, indeed, have all those glyphs. So my theory crashes and burns. The only other thing I can suggest is to get a different version of Free Sans. My copy is dated March 24, 2009. If you have the same version of Free Sans and the problem remains, then it certainly seems likely that it is a bug in 3.2 RC1. Oh, and my 3.1 is on Fedora 11 x86_64, installed from the repositories. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
