Bug 157030 - hyphenation properties get lost when doc gets closed and reopened
Summary: hyphenation properties get lost when doc gets closed and reopened
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.4.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-31 01:58 UTC by Martin
Modified: 2024-04-15 03:15 UTC (History)
2 users (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 Martin 2023-08-31 01:58:53 UTC
Description:
When I change the values for hyphenation (characters at line end/begin) from default "2" to "3", klick ok, check the document, everything is as expected.
When I close the document and reopen it, both values (and some others) are default again, also the text isnt processed as expected.


Steps to Reproduce:
1. open a document with some pages (in my case 400 pages)
2. place cursor in a paragraph with "default paragraph style"
3. open menu styles -> edit style -> text flow
4. check "automatically" and change values for "characters at line end/begin" to 3 (default is 2)
5. broken words are now as expected at least 3 characters long.
6. close and reopen the document and look for words broken after 2 characters. If there are any, thats not good.
7. open the dialog-box and look for the values mentioned above. In my case they're always "2"

Actual Results:
values didnt get saved
after reopen I have a different document, with differen line-breaks and different document-length and pages.

Expected Results:
values should be saved.


Reproducible: Always


User Profile Reset: No

Additional Info:
Working with Debian/Rasbian, Raspberry pi, regulary updated.
German installation, english language-settings but german hypenation-file.
Comment 1 Julien Nabet 2023-08-31 06:36:34 UTC
7.0 is quite an old branch, please give a try to a recent LO version like 7.5.5
Comment 2 Martin 2023-08-31 10:09:40 UTC
cant check this.
working under debian/rasbian, have to deal with the version provided.
Comment 3 QA Administrators 2023-09-01 03:14:52 UTC Comment hidden (obsolete)
Comment 4 Stéphane Guillou (stragu) 2023-09-16 09:38:52 UTC
(In reply to Martin from comment #2)
> cant check this.
> working under debian/rasbian, have to deal with the version provided.

Unfortunately, without an example document, more precise version information (Help > About) and testing in supported version (7.5 or 7.6), we'd have to close as "insufficient data".

You can install different versions of LO side-by-side with the debs: https://www.libreoffice.org/download/download

In any case, I could not reproduce with the "DT" dummy text autotext, ODT file, English hyphenation and:

Version: 7.0.6.2
Build ID: 144abb84a525d8e30c9dbbefa69cbbf2d8d4ae3b
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

The values set in the dialog remained.

Setting as "need info" for now.

Potentially related: bug 40266.
Comment 5 QA Administrators 2024-03-15 03:15:22 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2024-04-15 03:15:36 UTC
Dear Martin,

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