Created attachment 154108 [details]
MS word file with Lines and different styles
if you open an file from MSO that has different line styles, the import is correct, BUT when you'd like to edit the LineStyle the MSO line style name wasn't shown.
I think the MSO linestyle is missing in LibO standard.sod file but I don't know how the linestyle should be labeld that it will be show correct.
So what's the label of the different MSO line styles and when I add them to the standard.sod file will it be shown in the line style property dialog
Created attachment 154110 [details]
Line config dialog
label is missing cause not defined in LibO standard.sod file
We should definitely change at least the empty menu selection. Either we should something like "Other" or even better we provide an option to extend the line styles with names and call this "User defined".
(In reply to Heiko Tietze from comment #2)
> We should definitely change at least the empty menu selection. Either we
> should something like "Other" or even better we provide an option to extend
> the line styles with names and call this "User defined".
There are three kind of dash-definitions: Those from the "standard.sod". They have special treating in the source. Those from an user-defined palette. You need to load the palette to get the items into the list. And third, those which are included in the document. The latter are currently not shown at all, if they are not included in the current loaded palette. So we need something like an options "show document line styles".
Would it not be possible to add the mso styles to libo predefined list?
In the file the label is dash (var) 1, dash (var) 2, ...
I think I can fix the bug.
andreas kainz committed a patch related to this issue.
It has been pushed to "master":
tdf#127499 added 9 new line styles all are (var) and in line with MSO
It will be available in 6.4.0.
The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
A polite ping to Andreas Kainz:
Is this bug fixed? if so, could you please close it as RESOLVED FIXED ?
Otherwise, Could you please explain what's missing?