Description: To be specific: The German word construct "Kraftwerks-", i. e. "Kraftwerkspark" does not work for the font "Linux Libertine G" correctly. LibreOffice is used in German, the autosyllabification ("Silbentrennung") is working. If a word with "Kraftwerk-" is separated between "Kraft-" and "-werks-" the letter "w" and "e" are displayed at the same place. This means, that you really can not read the word part "-werks-". As far as I see, the problem does occur with the font "Linux Libertine G", for other there is not similar problem. Therefore I am not sure, if this is really a problem of Libreoffice but rather of the font type. This Problem occured in the release 5.2.1.2 and in the new 5.2.3.3. Steps to Reproduce: 1. Textdocument in Writer with syllabification and language switched to German 2. Use font "Linux Libertine G" size 12 and use justified typesetting 3. Write "Kraftwerkspark" at the end of a line, so the word will be separated "Kraft-" and "-werkspark" 4. See wrong typeset Actual Results: The result will occur everytime. Expected Results: "w" and "e" are displayed at the same spot in companion with "r" creating a wonderful new letter. Reproducible: Always User Profile Reset: Yes, even a new release, as discripted above, will bring no better result. Additional Info: This bug can always be solve, if the autosyllabification has no need to divide "Kraftwerks-" at an end of a line. User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0
Tried with justified, German, Linux Libertine G, Tools - Lang - Hyphenation: not reproduced on Win or Linux. On Linux, the only strange thing I get is an extra hyphen. On Windows, I don't get even that. Arch Linux 64-bit, KDE Plasma 5 Version: 5.2.3.3 Build ID: 5.2.3-1 CPU Threads: 8; OS Version: Linux 4.8; UI Render: default; Locale: fi-FI (fi_FI.UTF-8); Calc: group Version: 5.4.0.0.alpha0+ Build ID: babf6d5e53516e80e8e3f2485796ebfaeb20e9c1 CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-12-02_00:57:58 Locale: fi-FI (fi_FI); Calc: group
For me it is also not reproducible with LO 5.3.6.1 and Win10. Do you still have the problem? I'm not really an expert, but as far as I know some problems can be solved, if you disable OpenGL (Extras -> Option -> LibreOffice -> View). Set to NEEDINFO. Please change it back to UNCONFIRMED, if the bug is still there or WORKSFORME, if everything is O.K.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180404
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20180502