![](https://secure.gravatar.com/avatar/7797bae6c97f293294c13b1df94ac794.jpg?s=120&d=mm&r=g)
Dear all,
I found a small bug in the PDF+LaTeX export module. In the generated tex-file that contains the object placement information for latex a few comment character at line ends are missing.
This causes some funny misalignment effects if the final pdf with superimposed text is wrapped into other latex-command. Sometimes LaTeX requires to know where a line ends, otherwise undesired spacing is created.
We have identified the lines with missing comment characters '%' here:
http://tex.stackexchange.com/questions/82080/pictures-from-inkscapes-pdflate...
and I would not mind to fix this myself, but I can not find where the PDF+LaTeX module is located in the inkscape branch. If someone could please point me in the right direction, I'd appreciate it.
Regards, Martin
![](https://secure.gravatar.com/avatar/84524eb6e916f5d548e7c7c0e41fd127.jpg?s=120&d=mm&r=g)
On Mon, 2012-11-12 at 10:18 +0000, M H wrote:
Dear all,
I found a small bug in the PDF+LaTeX export module. In the generated tex-file that contains the object placement information for latex a few comment character at line ends are missing.
This causes some funny misalignment effects if the final pdf with superimposed text is wrapped into other latex-command. Sometimes LaTeX requires to know where a line ends, otherwise undesired spacing is created.
We have identified the lines with missing comment characters '%' here:
http://tex.stackexchange.com/questions/82080/pictures-from-inkscapes-pdflate...
and I would not mind to fix this myself, but I can not find where the PDF+LaTeX module is located in the inkscape branch. If someone could please point me in the right direction, I'd appreciate it.
Look at:
src/extension/internal/latex-text-renderer.cpp
![](https://secure.gravatar.com/avatar/15f5e6abf26f57e1838c29a8356ce7f8.jpg?s=120&d=mm&r=g)
---- M H <martin.hehn@...400...> wrote:
Dear all,
I found a small bug in the PDF+LaTeX export module. In the generated tex-file that contains the object placement information for latex a few comment character at line ends are missing.
This causes some funny misalignment effects if the final pdf with superimposed text is wrapped into other latex-command. Sometimes LaTeX requires to know where a line ends, otherwise undesired spacing is created.
We have identified the lines with missing comment characters '%' here:
http://tex.stackexchange.com/questions/82080/pictures-from-inkscapes-pdflate...
and I would not mind to fix this myself, but I can not find where the PDF+LaTeX module is located in the inkscape branch. If someone could please point me in the right direction, I'd appreciate it.
I thought I had fixed this in r10154. Can you try with 0.48.3 ?
Cheers, Johan
![](https://secure.gravatar.com/avatar/7797bae6c97f293294c13b1df94ac794.jpg?s=120&d=mm&r=g)
Hi Johan,
I noticed that when I looked through the source code just now. Most probably did not get the latest version of inkscape as I am on an older Ubuntu lucid system.
Will try to update and message again in case there are any problems but I guess it can be considered as fixed.
Very useful extension for my daily work, thanks for your efforts.
regards, Martin
On 12 November 2012 12:26, <jbc.engelen@...2592...> wrote:
---- M H <martin.hehn@...400...> wrote:
Dear all,
I found a small bug in the PDF+LaTeX export module. In the generated tex-file that contains the object placement information for latex a few comment character at line ends are missing.
This causes some funny misalignment effects if the final pdf with superimposed text is wrapped into other latex-command. Sometimes LaTeX requires to know where a line ends, otherwise undesired spacing is
created.
We have identified the lines with missing comment characters '%' here:
http://tex.stackexchange.com/questions/82080/pictures-from-inkscapes-pdflate...
and I would not mind to fix this myself, but I can not find where the PDF+LaTeX module is located in the inkscape branch. If someone could
please
point me in the right direction, I'd appreciate it.
I thought I had fixed this in r10154. Can you try with 0.48.3 ?
Cheers, Johan
participants (3)
-
unknown@example.com
-
M H
-
Tavmjong Bah