Once pstoedit GUI application is installed, setup should add shortcut into Windows start menu
should be solved in 4.02
Add option -nc in PstoeditQTGui
implemented in version 4.02
Thank you!
Add option -nc in PstoeditQTGui
Thanks - I will implement this for the next version 4.02. Best Regards Wolfgang
Add option -nc in PstoeditQTGui
C++ loadpstoeditplugins declaration breaks C compilation
included in 4.01
pstoedit 4.0 fails on macOS
fixed in 4.01
loadpstoeditplugins is using C++ declaration
fixed in 4.01
pstoedit 4.0 fails on macOS
Bug found with the help from Sean. Thanks. Will be fixed in next release.
I can certainly give it a try. Let me know what to change in the build.
Hi Sean, this one looks strange. Unfortunately I don't have maxOS available. Would you be available to run a version with some additional debug traces? I would send you some enriched pstoedit.cpp then. Best Regards Wolfgang
pstoedit 4.0 fails on macOS
C++ loadpstoeditplugins declaration breaks C compilation
will be fixed in next release
loadpstoeditplugins is using C++ declaration
this is a duplicate of https://sourceforge.net/p/pstoedit/patches/5/
loadpstoeditplugins is using C++ declaration
DXF output contains very jagged text edges
Please add -psarg "-r300x300" to your command line to increase the resolution during the frontend processing. Best Regards Wolfgang
This problem actually already shows up with the ps output so apparently that means a frontend bug? pstoedit -f ps -page 1 2023-12-31.ps test.ps
DXF output contains very jagged text edges
Once pstoedit GUI application is installed, setup should add shortcut into Windows start menu
Thanks for the suggestion. I will add this in the next version.
Once pstoedit GUI application is installed, setup should add shortcut into Windows start menu
C++ loadpstoeditplugins declaration breaks C compilation
Compile failure with GNU libstdc++ ver. 12.0.1
fixed in 3.78
Version 3.77 can't find GhostScript
fixed in 3.78
Error: /syntaxerror in /----nostringval----
Hi Wolfgang, I first wanted to try this one: I have downloaded this svg and used inkscape (1.1.1) to save it as an eps - https://www.jpmorgan.com/onyx/images/logo.svg See attachment logo.eps
By only downgrading pstoedit from 3.77 to 3.75, the conversion succeeds without any errors and the metapost file is fine. I am using the following versions from Ubuntu: ii inkscape 1.1.1-2ubuntu2 amd64 vector-based drawing program ii ghostscript 9.55.0~~rc1~dfsg-1 amd64 interpreter for the PostScript language and for PDF ii pstoedit 3.77-1 amd64 PostScript and PDF files to editable vector graphics converter
Then the following commands: pstoedit -f mpost circle.eps circle.mp pstoedit: version 3.77 / DLL interface 108 (built: Sep 4 2021 - release build - g++ 11.2.0 - 64-bit) : Copyright (C) 1993 - 2021 Wolfgang Glunz Error: /syntaxerror in /----nostringval---- Operand stack: false dumptextstring Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1990 1 3 %oparray_pop 1989 1 3 %oparray_pop...
But really it happens with any eps/pdf I save with inkscape, I have attached you a much simpler eps export of a cirlce: see circle.eps Could it be an issue with how inkscape is exporting the files?
Hi Wolfgang, I first wanted to try this one: I have downloaded this svg and used inkscape (1.2-dev) to save it as an eps - https://www.jpmorgan.com/onyx/images/logo.svg See attachment logo.eps
Version 3.77 can't find GhostScript
Error: /syntaxerror in /----nostringval----
Please provide me an example input file for the problem. Thanks Wolfgang
Error: /syntaxerror in /----nostringval----
Version 3.77 can't find GhostScript
This is fixed in later releases. Current release is 3.77.
pstoedit for Win64 calls gswin32c.exe (not present on a 64 bit system)
the recent pstoedit doesn't work on my computer
GS fails to read the source PS file provided
This is fixed in later releases. Current release is 3.77.
GS fails to read the source PS file provided
I'm getting exactly the same result, although I can get round it by using the -gs option to point at the correct executable. pstoedit: version 3.71 / DLL interface 108 (built: Apr 1 2018 - release build - MS VC++ 1912 - 64-bit) : Copyright (C) 1993 - 2018 Wolfgang Glunz pstoedit : path to myself:pstoedit 38 C:\Program Files\pstoedit\pstoedit.DLL loading plugin: C:\Program Files\pstoedit\drvlplot.dll creating Dynloader for C:\Program Files\pstoedit\drvlplot.dll loading dynamic library C:\Program Files\pstoedit\drvlplot.dll...
fixed in 3.76
With -metric, fig file resolution is 450/cm, not 1200/in
With -metric, fig file resolution is 450/cm, not 1200/in
Thanks for the report and a proposed solution. I will take this to the next release. Best Regards Wolfgang
With -metric, fig file resolution is 450/cm, not 1200/in
Hello, Thank you for your answer. Yes, it works! For me, it's: pstoedit -gs gswin64c -nc -f mpost 1001.eps 1001.mp because my ghostscript is 64bit. Best regards François
Salut Francois, Yes - I confirm the problem. It happens because you want the output on standard output and not directly to a file. When running it this way it works fine for me. pstoedit -nc -f mpost 1001.eps 1001.mp I will fix this in the next release. Best Regards Wolfgang
the recent pstoedit doesn't work on my computer
Hi Peter, this is not expected. Could you please send me the output of pstoedit -v -gstest Normally pstoedit calls ghostscript via its DLL and not EXE. The Exe is only used as a fall-back approach. Best Regards Wolfgang
pstoedit for Win64 calls gswin32c.exe (not present on a 64 bit system)
On Tue, 03 Nov 2020 18:49:09 -0000 "Wolfgang Glunz" wglunz@users.sourceforge.net wrote: to my understanding this was nailed down to be a problem in Inkscape's PS export. Please confirm/comment Hallo Wolfgang, My apologies for the delay in responding. Nathan informed me of his doubts, but Monday through Thursday are complicated for me to dedicate time - I have to prepare and teach classes over Zoom for the university. Tomorrow I'll re-check before I confirm either way. John
Hi John, to my understanding this was nailed down to be a problem in Inkscape's PS export. Please confirm/comment Thanks Wolfgang
pstoedit drops figures on converting to DXF
But that confirms that your compiler version is too old. But g++ 9 accepts this file. So you seem to call still the older version somehow.
test.cpp:1:1: error: unknown type name 'constexpr' constexpr int ce = 10; int * p = nullptr; ^ test.cpp:1:11: error: expected unqualified-id constexpr int ce = 10; int * p = nullptr; ^ test.cpp:1:34: error: use of undeclared identifier 'nullptr' constexpr int ce = 10; int * p = nullptr; ^ 3 errors generated.
Hi Chuck, could you please do a small test. Put this line into a new file, e.g. test.cpp constexpr int ce = 10; int * p = nullptr; And then run g++ -c test.cpp What is the output ? Thanks Wolfgang
configure: error: your version of g++ seems to be too old.
pstoedit 3.74 throws /findfont error with Ghostscript 9.26
The original problem with gs 9.26 is a problem of ghostscript itself, not of pstoedit. You can easily reproduce the issue by the following steps echo "/Helvetica findfont setfont" > test.ps gsnd -DDELAYBIND test.ps The problem is solved with gs 9.50 and the recent pstoedit (3.75) should be compatible with that as well. Best Regards Wolfgang
pstoedit (3.74) not working with latest ghostscript (9.50)
I just released pstoedit 3.75 which should now work with latest ghostscript again. Wolfgang
pstoedit (3.74) not working with latest ghostscript (9.50)
Ticket moved from /p/pstoedit/patches/3/