Bug 98422 - Wrong hyphenation with punctuation
Summary: Wrong hyphenation with punctuation
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Linguistic (show other bugs)
Version:
(earliest affected)
5.2.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-04 18:27 UTC by Urmas
Modified: 2018-09-03 14:56 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot of correct result (106.84 KB, image/jpeg)
2017-04-09 18:20 UTC, Buovjaga
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Urmas 2016-03-04 18:27:40 UTC
Libreoffice hyphenates the following word as "limin/e»", despite hyphenation properties set to 2 chars at the end. Here is one.
Comment 1 Buovjaga 2016-03-21 20:12:14 UTC
What language do I have to be using to get this bad behavior? With Finnish, it does limi-ne.

(I did Format paragraph - Text flow - Hyphenation automatically)

64-bit, KDE Plasma 5
Build ID: 5.1.1.3 Arch Linux build-2
CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8)
Comment 2 raal 2016-03-22 10:22:14 UTC
(In reply to Buovjaga from comment #1)
Hi Buovjaga, version is 5.2. I have few weeks old master build and hyphenation doesn't work for me (works in 5.1.1.3, do nothing in 5.2). Could you test with 5.2?
Comment 3 Buovjaga 2016-03-22 10:37:48 UTC
(In reply to raal from comment #2)
> (In reply to Buovjaga from comment #1)
> Hi Buovjaga, version is 5.2. I have few weeks old master build and
> hyphenation doesn't work for me (works in 5.1.1.3, do nothing in 5.2). Could
> you test with 5.2?

Yeah, I don't know how to get hyphenation to work in 5.2, so I tested with 5.1. I could not find anything immediately relevant in autogen help. There is only
--with-system-altlinuxhyph Use ALTLinuxhyph already on system.
--with-external-hyph-dir Specify external hyphenation pattern dir.

How do I need to build to get hyphenation working?
Comment 4 Kruno 2017-04-09 11:37:32 UTC
It's a closing question mark which LibreOffice seams to treat as letter character, since hyphenation properties set to to characters (two: e») - related to #106989?
Comment 5 Buovjaga 2017-04-09 18:20:30 UTC
Created attachment 132424 [details]
Screenshot of correct result

Still working ok for me.

Arch Linux 64-bit, KDE Plasma 5
Version: 5.3.1.2
Build ID: 5.3.1-1
CPU Threads: 8; OS Version: Linux 4.10; UI Render: default; VCL: kde4; Layout Engine: new; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Comment 6 Xisco Faulí 2017-10-31 17:45:51 UTC
(In reply to raal from comment #2)
> (In reply to Buovjaga from comment #1)
> Hi Buovjaga, version is 5.2. I have few weeks old master build and
> hyphenation doesn't work for me (works in 5.1.1.3, do nothing in 5.2). Could
> you test with 5.2?

Hi raal,
Does it work in master now ?
Comment 7 Xisco Faulí 2018-01-15 11:27:57 UTC
Hi Urmas,
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 8 QA Administrators 2018-07-31 09:38:50 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2018-09-03 14:56:59 UTC
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-20180903