Created attachment 54405 [details]
Source SVG, with most troublesome elements removed
SVG test file is "saved as" PDF from Inkscape. PDF looks as expected in PDF viewers (Acrobat, PDF XChange Viewer). When the PDF is opened in LODraw the following errors occur:
1. Text rotated to 90 degrees is offset vertically by an amount which seems to be proportional to the font size.
2. Text rotated to 45 degrees is completely mangled.
3. Line junctions convert from mitered to rounded.
(Bug 3 affects other LODraw input methods as well.)
Additionally the following properties are problematic:
4. dashed lines - dashes are lost, minor problem.
5. opacity - each object with an opacity of <100% in Inkscape results in a separate full page size black rectangle when the resulting PDF is imported into LODraw.
6. gradients - gradient rectangle extends to page limits.
7. pattern fill - patterns extend to page limits.
Problems 5,6, and 7 are probably all related, the PDF import just makes a mess of this sort of object.
Created attachment 54406 [details]
Example SVG file, including most troublesome elements.
Created attachment 54407 [details]
Example "save as" to PDF, version without most problematic elements
Created attachment 54408 [details]
Example "save as" PDF, version with most problematic elements
Created attachment 54409 [details]
Example without most troublesome elements, opened in LODraw, screenshot
Created attachment 54410 [details]
Exampe SVG without most troublesome elements, in Inkscape, screenshot
Created attachment 54411 [details]
Exampe SVG with most troublesome elements, in Inkscape, screenshot
Created attachment 54412 [details]
Example with most troublesome elements, opened in LODraw, screenshot
Pretty much everything is buried in a sea of black rectangles.
Impossible to handle this report with lots of different problems and unclear relation between problems and sample document. We sill have to create separate reports.
I started with "Bug 44710 - FILEOPEN PDF: Rotated texts at wrong position and scrambled"
<http://wiki.documentfoundation.org/BugReport#General_information> item 4
Fair enough, breaking it up. Dot/dash issue is bug 44727
The opacity issue was opened as Bug 44729
The gradient/pattern issue was opened as bug 44731
Additional PDF import problems in bug 45001
Joins and caps are not imported properly: bug 45003
reproduced in 3.5.2 on Fedora 64 bit and Windows 7 32 bit
used Firefox as reference viewer. Tested only first attachment.
If we open picture from office starting screen, picture opens as Draw document, and opens very corrupted. Half elements are broken.
If we open picture from existing document using Insert->Picture->From file, then picture contains only one error: one extra black rectangle in middle.
I can confirm this with LO 4.1.1 on Windows 7.
oh. thanks regina (again). you're right. I imported it incorrectly... :-(
ups. wrong tab. stricke last comment :-/
Most bugs are reported like
58173 Rotated text
(some may have been fixed meanwhile)
Keep this one for the lines issue, and rename the topic.
Line junctions are fixed in Bug 45003.
Dashed lines fixed within Bug 78241.
Anything else left here?
Tested by creating a Writer document with different line styles, export as pdf, and open in Draw. In general, it looks the same as in Writer. But:
1. Line width: 0.5, 1, 6pt -> works perfectly
2. Line style: ultrafine, fine, dashed, dash/dot, and user defined -> looks the same but none of the styles is listed with its name (not sure if it's possible, but would be good if)
3. Color: red, blue, tango sky blue, greenish user defined, white an blue background -> works like a charm including the color names in the sidebar's color picker
4. Arrow style: square right, big arrow left and small right: simulated per square plus line or triangular shapes
5. Shadow: red with default settings, white on blue background with small distance and 50% transparency: shadow line is simulated by an extra line, transparency is ignored, distance is okay
Taken all together it looks good to me. The minor inconsistencies are acceptable.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present on a currently supported version of LibreOffice
(5.4.1 or 5.3.6 https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the version of LibreOffice and
your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave
a short comment that includes your version of LibreOffice and Operating System
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword
Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Created attachment 135955 [details]
LOO 18.104.22.168 improved against LOO test 2011
Example with no opacity: i see no difference between Inkscape and screenshot in LOO 22.214.171.124.
0.125 pt line is wrong in 126.96.36.199
> 0.125 pt line is wrong in 188.8.131.52
It have the same thickness as 0.25 pt and 0.5 pt - 1 pixel.
Different look is just because of antialiasing.
Created attachment 137860 [details]
bounding_line4 without false long vertical stripes LOO-184.108.40.206
bounding_line4 without false long vertical stripes
LOO-220.127.116.11 64bit win 10
export to pdf
wrong patterns in more detail after deleting false long vertical stripes
I tried open PDF and SVG with most problematic elements from attach in LibreOffice Draw 6.1 beta 2
PDF opens as black rectangle!
SVG opens fine!
I tried save SVG to PDF from LibreOffice 6.1 beta 2 and then reopened result (see attach). PDF opens, but with problem in shapes
Created attachment 142848 [details]
bounding_line4.pdf in LO Draw 6.1 beta 2
Created attachment 142849 [details]
bounding_line4.svg in LO Draw 6.1 beta 2
Created attachment 142850 [details]
bounding_line4 from LO Draw 6.1 beta 2.pdf reopens in LO Draw 6.1 beta 2
Problem with PDF import still present in 6.1 beta 2
svg import now good with some errors in LO 18.104.22.168
complete circles of samples are incomplete.
so new svgio is a great improvement but not perfect.
no improvement in pdf-import to version 6.0.x .
svg import now very good with no errors found here in LO 22.214.171.124
complete circles of samples are now ok.
so new svgio is a great improvement and here perfect.
So 50% of problem is solved with the svg part.
pdf is here unsolved.
no improvement in pdf-import to version 6.0.x .
pdf import of simple pdf in 126.96.36.199-64 in Win10-x64 is ok
with line 0.0 is not seen.
in Acrobat reader and firefox 61 this zero line is red.
second complex pdf no improvement in visible elements perhaps under the black layer.
same problems in complex pdf in 188.8.131.52 to previous in 6.2 and 6.1