Bug 125937 - Lib5-text do not open the same way in Lib6
Summary: Lib5-text do not open the same way in Lib6
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.1.1 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-15 12:27 UTC by Jesper Friborg
Modified: 2020-03-26 02:39 UTC (History)
4 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 Jesper Friborg 2019-06-15 12:27:28 UTC
Description:
In Lib5 version and in danish I split the words, so they fit a margin-setting to 14-centimeter. I do it without carriage-return-activation, but letting the program do the change to the new line itself. Having written and saved several thousands pages in that way there have been no problems with reopening them in exactly the same way in Lib5 again. 

But in Lib6 the same texts does not respect the word-splitting, but insist on displacing the whole word to the beginning of the next line, leaving empty space in the end of the line before, where part of the word were before. And that means of course that the whole text is displaced accordingly, so originally page-layout is ruined,by creating extra lines.

Steps to Reproduce:
1.write a lib5 text with word-splittings at the end of the line
2. try to open it in Lib6
3. see that whole, then un-split, words first appear in the next line  

Actual Results:
Lay-out is ruined

Expected Results:
To see the saved layout


Reproducible: Always


User Profile Reset: No



Additional Info:
Like said in LinuxQuestionings.org, where there is a thread under "newbie" with the title "How to secure that Lib5-texts open the same way in Lib6" the program must either open exactly the same way or at least offer "import of older settings". Here it is also told that you earlier have had bug-reports about this, but lacked "documentation". Maybe this is helpful.
Comment 1 V Stuart Foote 2019-06-15 13:36:48 UTC
Sorry, but as submitted there is nothing actionable here.

We need a sample of several pages of a document prepared in LibreOffice 5.x that is being mis-formatted in LibreOffice 6.x

Also, it helps a lot to know what versions/builds of LibreOffice you are working with (although we can usually extract that information from any sample you submit). There have been 51 release builds of LibreOffice 6.x and 99 release builds of LibreOffice 5.x -- multipled by the support Operating systems -- with each build affected by the operating system and desktop environment being worked in.  You've got to help narrow the scope of your reported issue or this will never be confirmed let alone patched if found valid.

Thanks!
Comment 2 Jesper Friborg 2019-06-16 18:14:07 UTC Comment hidden (obsolete)
Comment 3 V Stuart Foote 2019-06-16 20:18:33 UTC
Sorry, but that text is no help, we would need some sample of documents to determine if paragraph, character or even page formatting is different. It may not be changes to he hyphenation rules at all.
Aids

To bypass any profile migration issues--moving from 5.x to 6.x--you can also open LibreOffice in SafeMode (from the Help menu). That will allow it to use the defaults for your locale. And, in Safe mode with default user profile, does the 6.x build hyphenation match the 5.x builds?

Otherwise could you compare 5.x/6.x user configuration/profile. Review checkbox entries in Tools -> Options -> Languages -> Writing 

One other thing to look for. I believe your default da-DK hyphenation will be performed by "Libhyphen Hypenator", and you should have its localized hyphenation library installed with your 5.x or a new 6.x build. You'd look in the LibreOffice installation directory, for a directory LibreOffice/share/extensions/dict-da/ and a file named either hyphen_da.dic, or hypehn_da-DK.dic

The rules are cryptic not meant to be directly edited, but you should be able to compare the size of the hyphenation rule files between 5.x and 6.x builds. Should not see a great change in size if everything was built/installed correctly.
Comment 4 V Stuart Foote 2019-06-16 20:23:32 UTC
@scootergeisen, you'd done the last Pootle changes to the Danish da-DK dictionary. Any tweaks to the Hyphenation rules? And are you seeing correct hyphenation with 6.2.4, 6.3.0 or master/6.4.0 builds?  Thanks!
Comment 5 Jesper Friborg 2019-06-17 16:33:27 UTC
Thank you for your efforts, but you forget that you have to deal with an amateur here, in over his head, but trying to use the possibility to widen understanding range.

So from the first of the two: 

1. Which of the nine marking possibilities do I use in safe mode
2. How to find user configuration profile. In "tools" I can only find "language", but not "options" and "writing"
3. Where to find LibreOffice installation directory

 In the second post I has been impossible for me to look up what "pootle changes" mean. Some of the hyphenation is "self-made" in the sense, that it didn't appear by itselves. But I have only done "grammatical correct splitting", "to fill the rest of the line". I haven't been able to check hyphenation in 6.2.4 as my MX-18-distribution only is updated until 6.0.1.1 

As you maybe can see the whole thing is quite "swimming" for me, so I really need step-by-step-directions. I hope you have patience for that. Apart from having a personal problem, I also filed the report because I felt obliged to, encouraged by others in Linux-Questionings.com. If you havn't let me know and I might have to downgrade.
Comment 6 Telesto 2019-06-17 20:12:28 UTC
@Jesper Friborg
(In reply to Jesper Friborg from comment #5)
>  In the second post I has been impossible for me to look up what "pootle
> changes" mean. Some of the hyphenation is "self-made" in the sense, that it
> didn't appear by itselves. But I have only done "grammatical correct
> splitting", "to fill the rest of the line". I haven't been able to check
> hyphenation in 6.2.4 as my MX-18-distribution only is updated until 6.0.1.1 

This is directed to ScooterGeisen, so no wonder you didn't understand :-)
Comment 7 Dieter 2019-08-27 09:29:11 UTC
Jesper, since there is no answer from ScooterGeisen to comment 4, I'd like to ask for a sample document as attachment.

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it)
Comment 8 scootergrisen 2019-08-27 11:13:22 UTC
(In reply to V Stuart Foote from comment #4)
> @scootergeisen, you'd done the last Pootle changes to the Danish da-DK
> dictionary. Any tweaks to the Hyphenation rules? And are you seeing correct
> hyphenation with 6.2.4, 6.3.0 or master/6.4.0 builds?  Thanks!

I have no idea.
And i dont know what lib5/lib6 is.
Comment 9 Dieter 2019-08-27 13:16:11 UTC
(In reply to scootergrisen from comment #8)
> And i dont know what lib5/lib6 is.
LO5 and LO6?
Comment 10 scootergrisen 2019-08-27 15:47:43 UTC
(In reply to Dieter Praas from comment #9)
> (In reply to scootergrisen from comment #8)
> > And i dont know what lib5/lib6 is.
> LO5 and LO6?

ok but maybe better to let someone else test it that knows it better. i dont really use it much.
Comment 11 QA Administrators 2020-02-24 02:32:29 UTC Comment hidden (obsolete)
Comment 12 QA Administrators 2020-03-26 02:39:12 UTC
Dear Jesper Friborg,

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