You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Enter [""C:\Documents and Settings\image"".png] in a t2t file
2. Export file to latex
What is the expected output?
\includegraphics{"C:/Documents and Settings/image".png}
What do you see instead?
\includegraphics{"C:$\backslash$Documents and Settings$\backslash$image".png}
What version of the product are you using? On what operating system?
t2t 2.5, Ubuntu Linux Karmic Koala
Original issue reported on code.google.com by jendriks...@gmail.com on 10 Feb 2010 at 3:51
The text was updated successfully, but these errors were encountered:
txt2tags doesn't know about Windows files, or how specific targets expect them
to be formatted. But you can easily workaround this by adding a postproc filter:
%!postproc(tex): MYIMAGE '"C:/Documents and Settings/image"'
%!postproc(html): MYIMAGE C:\Documents and Settings\image
[MYIMAGE.png]
But I'll leave that bug opened as a reference, to maybe in the future include
that on the sources.
Thanks for the detailed report!
Original comment by aureliojargas@gmail.com on 18 Jun 2010 at 2:57
I think I made an error above. The expected output should be
\includegraphics{C:\Documents and Settings\image.png}
Why are the backslashes escaped although they're surrounded by ""s ?
Original comment by jendriks...@gmail.com on 20 Nov 2010 at 4:17
This bugreport is actually a duplicate of bug 11. It wasn't clear to me that
raw blocks make escapes and only tagged blocks don't make escapes.
You should probably change the tip
http://txt2tags.sourceforge.net/tips.html#html-remote-image, because the tagged
mark works for all targets there, while the raw mark doesn't work e.g. for
latex when the image path has backslashes.
Original comment by jendriks...@gmail.com on 16 May 2012 at 1:36
Original issue reported on code.google.com by
jendriks...@gmail.com
on 10 Feb 2010 at 3:51The text was updated successfully, but these errors were encountered: