To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=105238
------- Additional comments from alfay...@openoffice.org Fri Sep 25 08:42:17 +0000 2009 ------- Hello mru. Thanks a lot for your response. I send an attachment, an odt document with several font examples, including Bitstream Vera Mono and DejaVu Sans Mono. The point is that you mustn't have Bitstream Vera family installed in your system, so I guess you'll need two different systems with different Oo versions. I'm sorry I didn't explain myself clear enough. I'll try to be more exhaustive: I tried with several other fonts (monospaced and non-monospaced, including Courier New) and the only ones that are problematic are DejaVu Sans Mono and Bitstream Vera Sans Mono. But I don't think the problem it's in the fonts, the results of the tests make me think that it's a mix of font sustitution and the "Print Layout" vs. "Web Layout" issue. DejaVu and Bitstream Vera are free font families common in Linux, but not in Windows. As far as I know, Oo 2.x installed Bitstream Vera on the system, but now Oo 3.x installs DejaVu. I noticed that when the specific font is installed in the system, there´s no problem with it, so in this case, no matter what Oo version you're using, the text is displayed OK in Linux. The same goes for Bitstream on Oo 2 and DejaVu on Oo 3 in Windows. But when you use DejaVu Sans Mono in Oo 3 and then you open the document in Oo 2, the problem arises. And also when you use Bitstream Vera Mono in Oo 2 and you open the document in Oo 3. So I guess that when Oo tries to substitute a font, and this font is monoespaced, something happens and it's displayed with the wrong kerning, overlapping the characters. The weird thing is that this only happens in Print Layout mode. Also, when you open the document the first time, it's displayed OK, the next time you open the document is when it's bad displayed; that makes me think that it's some kind of obscure program failure in the Print Layout mode... I don't think the problem relays in a certain font, but in the way Oo treats it and displays it: a) The first time you open the doc, it's displayed OK. If there was a problem within the font, it should be bad displayed always. b) In fact, there's no font!. As I explained before, the font is not installed in the system where the error happens. To be more precise, the problem is not with the font, but with the sustitution of the font. That is: for example, the system does not have the Bitstream Vera font family, the text written in Bitstream Vera Sans is displayed OK (so, the font is supposed to has been well replaced), but the text written in Bitstream Vera Sans Mono is "crunched". Anyway, I think the relevance of this problem lies in this point: it undermines one of the strongs of Oo, the possibility of working with a standard format, no matter the system and (up to some point, at least) the version of the application. To get this accomplished, you need some system-independent fonts, that technically and legally could be distributed and installed with Oo; Bitstream (and now DejaVu) are the font families chosen and so, they should be fully reliable and functional. Of course, you can't blame Oo for an error of the font itself but I think this is not the case here. Thanks for your attention. Hope it helps Carlos --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
