Bug 151367 - Line following soft hyphen uses paragraph instead of line spacing. Formatting
Summary: Line following soft hyphen uses paragraph instead of line spacing. Formatting
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.3.6.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-06 00:37 UTC by R Freestone
Modified: 2023-05-21 03:16 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description R Freestone 2022-10-06 00:37:42 UTC
Description:
When a soft hyphen is inserted within a word, and the word is actually hyphenated on the page, paragraph spacing is inserted before the next line (the line with the second part of the hyphenated word).

Steps to Reproduce:
1. Insert soft hyphen (U+00AD) within a word that is at the beginning of a line, where the first part of the word and the hyphen will fit on the previous line. Hyphen appears when word is hyphenated.
2. 

Actual Results:
Paragraph spacing is inserted between the two lines with the hyphenated word.


Expected Results:
Line spacing should be used between the two lines with the hyphenated word.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.3.6.2 (x64) / LibreOffice Community
Build ID: c28ca90fd6e1a19e189fc16c05f8f8924961e12e
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

Device name	DESKTOP-S4TL885
Processor	Intel(R) Celeron(R) CPU N3450 @ 1.10GHz   1.10 GHz
Installed RAM	8.00 GB (7.79 GB usable)
Device ID	6CF70119-2AB7-49D6-B2DB-DC18B526440B
Product ID	00331-20020-00000-AA841
System type	64-bit operating system, x64-based processor
Pen and touch	No pen or touch input is available for this display

Edition	Windows 10 Pro
Version	        21H2
Installed on	‎1/‎14/‎2022
OS build	19044.2006
Experience	Windows Feature Experience Pack 120.2212.4180.0
Comment 1 Dieter 2022-10-21 21:30:36 UTC
I can't confirm with

Version: 7.4.2.3 (x64) / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL

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. Change to RESOLVED WORKSFORME, if the problem went away.
Please also make sure, that the reported issue is not related to corruption in the user profile. Please reset your
 Libreoffice profile (https://wiki.documentfoundation.org/UserProfile) and re-test.
Comment 2 QA Administrators 2023-04-20 03:31:19 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2023-05-21 03:15:59 UTC
Dear R Freestone,

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-FollowUp