Inkscape 0.91 not working with psfrag and eps figures

Bug #1618594 reported by Simon
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
Undecided
Unassigned

Bug Description

Dear all,

First of all Inkscape is a great software, I like it very much and use it to prepare figures for scientific publications.

Yesterday I decided to try out the new 0.91 version of Inkscape (I use the 32 bit pre-compiled version for Windows, I run windows 7) and noticed that the .eps figures that I generate using Inkscape no longer work with psfrag. The same .svg figure, when saved as .eps with the previous version of Inkscape (0.48.5) work fine. I don't use the save to latex option where it generates a text free figure and latex code to superimpose text. While I'm sure that this Latex export feature is great (I haven't experimented with it yet), I feel that compatibility with psfrag should be maintained.

I'm attaching the .svg figure that I've been using to test this.

Revision history for this message
Simon (wakeboard2) wrote :
jazzynico (jazzynico)
tags: added: eps exporting
Revision history for this message
Bevan Jones (thunder852) wrote :

Is this bug confirmed as a bug or a loss of feature?

Simon, did you eventually get around this problem?

Revision history for this message
Alvin Penner (apenner) wrote :

do you have an example of an eps file generated by Inkscape (earlier version) which does work properly in psfrag?
also the original svg file in this case would also be helpful, for testing purposes.

Revision history for this message
Simon (wakeboard2) wrote :

The workaround that I've found and am currently using is to use Inkscape v0.48 which seems to work well for psfrag.

Here's an example .svg as well as the corresponding .eps (generated by v0.48) that works with psfrag.

The latex code for the figure would look something like this:

\begin{figure}[htb]
  \centering
  \subfloat[][]{\label{fig:sinus_excitation}
  \scriptsize
  \psfrag{-8}[r][r]{$-8$} \psfrag{-4}[r][r]{$-4$}
  \psfrag{0}[r][r]{$0$} \psfrag{4}[r][r]{$4$}
  \psfrag{8}[r][r]{$8$}
  \psfrag{-0.5}[c][c]{$-0.5$} \psfrag{0.5}[c][c]{$0.5$}
  \psfrag{b0}[c][c]{$0$} \psfrag{2}[c][c]{$2$}
  \psfrag{1}[c][c]{$1$} \psfrag{1.5}[c][c]{$1.5$}
  \psfrag{xlabel}[c][c]{\small $t (\si{ns})$}
  \psfrag{ylabel}[c][c]{\small $I (\si{mA})$}
  \psfrag{t1}[c][c]{\small$t_1$}
  \psfrag{t2}[c][c]{\small$t_2$}
  \psfrag{t3}[c][c]{\small$t_3$}
  \includegraphics[width=0.222 \textwidth]{current_sinusoidal}}
\end{figure}

My workflow is basically to work on a figure as .svg and export it to .eps format to use with latex.

Revision history for this message
Simon (wakeboard2) wrote :

Here is the .svg file

Revision history for this message
Alvin Penner (apenner) wrote :

thank you for the attached files. I see that there are some differences between old versus new Inkscape versions. For example the two pieces of text 'ylabel' and 't1' are handled slightly differently. In Inkscape 0.48.5 they are reported separately in the eps file, as:

BT
0 -16 16 0 13.618781 201.621619 Tm
/f-0-0 1 Tf
[(ylabel)]TJ
ET
BT
16 0 0 16 124.566541 265.935358 Tm
/f-0-0 1 Tf
(t1)Tj
ET

while in Inkscape 0.92.2 they are reported as a single element, as in:

BT
0 15 15 0 12.767607 125.979733 Tm
/f-0-0 1 Tf
[(ylabel)]TJ
15 0 0 -15 116.781132 65.685602 Tm
(t1)Tj
ET

Not sure why this should cause a problem, however. In both cases the Tj tag is used. In any event, what is probably needed here is someone with experience in using psfrag, which I do not have.

Revision history for this message
grey tomorrow (gtomorrow) wrote :

Closing because INVALID: Incomplete.

If you feel this issue has been unjustly closed, please feel free to open a new issue at https://inkscape.org/report . Thank you.

Closed by: https://gitlab.com/greytomorrow

tags: added: bug-migration
Changed in inkscape:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.