Hi Shannon,
Hmmm.. it does sound like an error related to trying to use the wrong
convert command (as you noted Windows has it's own convert.exe
command). This StackOverflow answer says something similar:
http://stackoverflow.com/a/26163068
After some searching around, it seems like there's a
Thanks Tim, I had read some of those, but hadn't seen the third. I'll try
the regedit,or just rename windows convert. I already have ImageMagick at
the beginning of the PATH. It's seems like I can run/access ImageMagick
convert from cmd when I call/run it directly, but DSpace is trying to use
On 4/15/2015 9:27 AM, Shannon Meisenheimer wrote:
Thanks Tim, I had read some of those, but hadn't seen the third. I'll
try the regedit,or just rename windows convert. I already have
ImageMagick at the beginning of the PATH. It's seems like I can
run/access ImageMagick convert from cmd
It was an issue with DSpace not being able to find ImageMagick
convert.exe, even though the path and environment variables are properly
defined. You do have to set the path in dspace.cfg, but that in itself is
tricky as none the following worked:
--
- C:\\Program Files\\ImageMagick
- C:\Program
I notice the extension is .pdf.jpg. Imagemagick relies on the extension
to know how to do a conversion.
On Tue, 2015-04-14 at 16:39 -0500, Shannon Meisenheimer wrote:
Hi,
We are running DSpace 5.1 (Mirage2) on Windows Server 2012.
I've installed ImageMagick and Ghostscript to same
I assumed that was the output file (thumbnail)...
If it isn't, I wouldn't have any idea what those files are. All 220 errors
(there are 220 titles) show the same double extension.
Thanks,
Shannon
Sent from my iPhone
On Apr 14, 2015, at 5:05 PM, Keir Vaughan-Taylor kei...@optusnet.com.au
6 matches
Mail list logo
