With all fonts, at 11pt., autohyphenation leaves no space between the last character in the line and the hyphen, which often touches or overlaps it.
What operating system do you use? This may as well be just a rendering artifact, rather than an actual spacing error — does exporting to PDF render fine, for example?
Created attachment 105037 [details] Hyphenation when printed
Created attachment 105038 [details] Hyphenation with PDF export
Created attachment 105039 [details] Correct hyphenation (as it should be)
I have the same problem. Arch Linux, with Libreoffice 4.3.0.4. The font is Calibri, 11 pt. German text language. When printing directly from LibreOffice on a Kyocera Mita FS 1920, the hyphenation _always_ runs into the last letter. This makes direct printing from LibreOffice absolutely useless. On the other hand, when exporting a PDF, the spacing is not too narrow, but on the other hand slightly too large. This is still somewhat usable, but looks slightly weird. I have attached three images which show the problem. Only the last one hyphenation-3-correct.png is correct. I have manually written the words in LO Writer like this: Wirt- Zusätz- inter- It would be extremely good if this is fixed. Currently this makes LO close to unusable for serious usage at the moment.
Is there any reaction to this bug report? I have the slight suspicion that this issue arises because the font "OpenSymbol" is used, which does not go well with Calibri. I don't know why LibreOffice uses OpenSymbol, even if I use Calibri for the main font.
Hi all, I copied and Paste without issue: Wirt- Zusätz- inter- with Calibri font 11 pts in LO 4.4.0.0.alpha0+ Build ID: 5aeb852efcabdd51545d5d41c92f4bf3cef1d663 TinderBox: Win-x86@39, Branch:master, Time: 2014-09-08_07:01:57 & Windows 7 Home Premium Odt, Printing and Export to pdf show no difference. regards, Jacques
May be this is related to bug #76014. Then you should be able to workaround this problem by changing the the system default printer BEFORE LO START to another one.
Status NEW because of confirmation in comment 5 version set to 4.3.0.4 and O/S to Linux I'd like to know from affected user if they still experience this in LibO 4.3.5.2
I can reproduce this bug in LibreOffice 4.3.3.2, 4.3.5.2 and in the forthcoming version 4.4.0.2 under Kubuntu 14.10 (64 bit). This bug is also reproducible under Knoppix 7.4.2 (Live-USB) and CentOS 7.0-1406 (Live-USB) with a Canon MG5350. Today I have reinstalled my whole system and I have now a fresh formatted, clean Kubuntu 14.10 system. The bug is still reproducible. Fortunately a workaround exists: When I change the printer language (in the printer dialogue) from the default setting "PDF" to "PostScript (driver level)", the text is been printed properly. When I print text with 600 dpi, the hyphens overlapp with the text on the left. When I print with 2400 dpi resolution, the space between the hyphen and the text is IMHO too wide. The problem appears at manual hyphenation as well as at automatic hyphenation. I have attached two PNG files.
Created attachment 112575 [details] hyphens printed with 600 dpi
Created attachment 112576 [details] hyphens printed with 2400 dpi
Created attachment 112598 [details] original ODT test file
I can confirm this behavior in LibreOffice Writer 4.3.3.2 on 64 bit Ubuntu 14.04. I have experienced it with fonts other than those mentioned, specifically with FreeSerif and its companions. Because of other quirks with LibreOffice dual-sided printing, I always export to pdf and print from Acrobat Reader, so this isn't such a big deal for me, but I agree that it is annoying.
This bug is still reproducible in Kubuntu 15.04 and LibreOffice 4.4.2.2. Therefore hyphenation is simply not usable with PDF as default printer language. When I change the printer language (in the printer dialogue) from the default setting "PDF" to "PostScript (driver level)", the text is been printed properly.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
The bug is still present: LibreOffice: 5.1.4.2 KDE neon User Edition 5.7 (based on Ubuntu 16.04)
Using Version: 5.2.1.2 on Ubuntu 16.04.1. This bug is still present and, when printing directly from LibreOffice, appears on the printed page as well as the screen. This isn't really an issue for me, however, since I seldom ever print directly from LibreOffice (way too many problems with that), and export to pdf for printing (which seems to work fine). Has anyone experienced this issue on Windows? LO seems to rely on Linux to read font information and, whether due to ill-formed fonts or bugs in fontinfo, Linux provides unreliable information about the font. The only comment posted with this bug report that DOESN'T experience this is from a Windows user. (albeit from the statistically significant sample of six!!!)
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170929
I happened to have just installed Linux Mint 18.2 on a new Intel machine that has LibreOffice 5.1.6.2 as part of its default apps. Since I hadn't yet removed LO, I retested for this bug and can confirm that it is still present. On another Ubuntu 16.04 AMD machine, I still had a LibreOfficeDev 5.3.4.0.0+ (later versions were all removed since LO has too many "issues" for my particular uses), so I fired that up and tested. I can confirm that this bug is still present on that combination as well (not surprising; Mint is an Ubuntu derivative). As I mentioned in Comment 18, I really suspect this has to do with LO's use of Linux font information system calls (the same reason Writer does bizarre and inappropriate font substitutions without reporting them to the user). Before (mostly) abandoning LO, I learned quite some time ago to never print from within Writer anyway - I mostly "printed" to pdf and then let Adobe Reader do the actual printing (indicating that the generated pdf is done properly, and that Adobe Reader has a way of getting font metrics on its own). The steps for reproducing this bug are well documented - even in earlier postings on this bug tracker - so I'm rather fascinated by the notion that - because no one has complained about this for more than a year - it might have magically fixed itself and gone away. While I obviously can't speak for everyone, it is fairly clear that bugs only get worked on (much less actually fixed) when they're simple to fix; fair enough - it's free. It's also clear that not considering certain classes of bugs (like text rendering) "in toto" (rather than as individual quirks) insures that they'll probably never be fixed.
Bug cannot be reproduced in LibreOffice Version 6.0.6.2. Bug can be closed.