Forum Discussion
Norbert86
Jan 23, 2019Copper Contributor
Line thickness of SVG changes by exporting docx as PDF
Dear Community, I observed that the line thicknesses of SVG pictures in a docx document get thicker when exported to PDF. I got the impression that Office 365 (Version 1812) changes the line thic...
Jason Morse
Oct 08, 2019Copper Contributor
Thank you for the comment. This SVG was already converted to paths to deal with specialized embedded fonts from ESRI ArcGIS Pro. You will notice that all lines in my previous example above exhibits increased line thicknesses - not just the path'd fonts.
Chuanxin LIU
Oct 28, 2019Copper Contributor
I've found a workaround to solve the problem. First convert all object to path (you've done that). After you place the svg in word, right click and try convert to shape. It works perfectly at my end.
- Jason MorseNov 21, 2019Copper Contributor
Thanks for your reply Chuanxin LIU. Similar to Zyme86 your workaround has not been successful for me.
Converting my SVG to a shape often destroys it or changes many of the shapes to "fat" mode within Word that I cannot change to the expected pen width.
The only workaround I have found so far is generating a PDF, converting it to SVG using https://github.com/dawbarton/pdf2svg and then importing to Word. It looks as expected in Word and the resulting exported PDF.
Ridiculously complicated for a feature that I would expect to work out of the box.
- Zyme86Nov 21, 2019Copper Contributor
Chuanxin LIUfor me your workaround only works to 50%. It indeed solves the problem with the broadened lines, but when making the "conversion to form" in word365 several things happen, like for example the arrows of my inkscape vector graphic also lose their heads.
Edit: So for arrows it is also needed to additionally apply "stroke to path" in inkscape on all arrows. Then that also works fine. But still a lot of other problems occur and parts of the vector graphic are missing in the final pdf, although they are visible in the word file after conversion to form.
- Chuanxin LIUOct 29, 2019Copper Contributor
I exported the same docx to pdf on windows 10 and MacOS. Only windows 10 (for me it's 1903) caused the problem.