https://bugs.freedesktop.org/show_bug.cgi?id=42856
Roman Eisele <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | --- Comment #12 from Roman Eisele <[email protected]> 2012-08-21 10:04:43 UTC --- Sorry, I have to reopen this bug report. 1) The reporter of bug 53110, [email protected], has reported that he can still reproduce this issue with LibreOffice 3.6.0. This implies that the issue is not fixed in LibO 3.6.x, as I had assumed, but is still present. 2) The fact that I can not reproduce the issue anymore with LibO 3.6.x on MacOS X 10.6.8 (Intel), but dcdevoto can still reproduce it with the same LibO version on MacOS X 10.4.11 (PPC), suggests to me two possible explanations: a) This is NOTOURBUG, rather a problem either with the .dfont versions of Monaco and Courier (both 5.1d1e1) which Apple supplied with MacOS X 10.4.x, or with the text rendering engine (ATSUI?) of MacOS X 10.4 (and 10.5?) itself. So we could close this bug report as RESOLVED/NOTOURBUG b) But I have learned to be careful with setting NOTOURBUG. It seems also possible (even if improbable), from the point of view of a simple-minded bug-wrangler like me, that the reason of this bug is a complicated interaction between LibreOffice and MacOS X 10.4/10.5. Therefore I just REOPEN this bug report for now and wait for additional evidence if this is really NOTOURBUG. 3) In his comments to bug 53110, dcdevoto has also given good reasoning for the importance of this bug; i.e. why the automatic use of ligatures should be always disabled for monospaced fonts including Courier and Monaco. a) Here is another one: If you ever get some carefully space-aligned pseudo-tables like | MacroSoft Office | OpenOffice.org | LibreOffice Supports | Mac, Win | Mac, Win, Linux | Mac, Win, Linux Test result | ** | *** | ***** ... | | | (there are still people who produce manuscripts containing such crap!), the complete alignment will be messed up by the automatic addition of any ligatures, and this makes it difficult to read and convert such pseudo-tables to real tables. b) And yet another one: If you have to embed source code listings in your document, which are normally formatted with monospaced fonts and often aligned with spaces, the automatic addition of ligatures will also mess up the formatting. Because of this and similar reasons I am now convinced that this bug has some importance and that it is reasonable to expect that LibreOffice should not any ligatures to monospaced fonts (by default). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
