I am trying to do PDF to Image conversion. The command I used to do conversion is
convert -density 150 -define registry:temporary-path=/tmp "original_1492599526_Management__CRC.pdf" -quality 50 "imgmagick1492599530_%09d.jpg"
After running above conversion command on red hat linux(rhel 6) machine getting bellow error.
I gone through these links but no help.
http://imagemagick.org/discourse-server/viewtopic.php?t=17790
https://bugzilla.redhat.com/show_bug.cgi?id=1027534
http://forums.justlinux.com/showthread.php?130769-Ghostscript-fails-to-read-PDF-strange-error
Any help appriciated, thanks in advance.
You are using an archaic version of Ghostscript, if I read that error correctly.
Version 8.70 is now 7 years old. I would suggest that you upgrade to the current version and try again.
If the problem persists then you are going to need to post an example file somewhere to look at. A screenshot of an error doesn't tell me much.
Related
I've been using ImageMagick 6.9.0 for some time, and had setup some Railo scripts using it on a Windows Server 2008 R2 Standard Edition machine a while back. I know that they worked at the time. I just tried to run them on a new set of images now, but ImageMagick is failing on the very first command:
<cfexecute name="#Application.ImageMagickRoot#\identify.exe" variable="imgResult" timeout="60" arguments="-format ""%w|%h"" ""#attributes.infoFullPath#""" />
The error returned is:
identify.exe: RegistryKeyLookupFailed `CoderModulesPath' # error/module.c/GetMagickModulePath/662. identify.exe: no decode delegate for this image format `JPEG' # error/constitute.c/ReadImage/501.
I've never seen anything like this. So I checked and saw that there is a new version out, and downloaded IM 7.0.1. I tried running the above command again with no changes, but this time pointing to the 7.0.1 install folder. This resulted in a different, but similar, error:
identify.exe: unable to load module 'C:\ImageMagick-7.0.1-Q16\modules\coders\IM_MOD_RL_JPEG_.dll': The specified module could not be found. # error/module.c/OpenModule/1275. identify.exe: no decode delegate for this image format `JPEG' # error/constitute.c/ReadImage/505.
I looked in the directory in the error and there is a file named IM_MOD_RL_jpeg_.dll there.
The images that I'm trying to work with are all different, and I've cycled through 50 or so during testing. But all are between 4 and 10 megapixel photos exported from Photoshop CS5 Camera Raw to jpeg format. I've tried fiddling with the case of the drive letter and the file extension without success. A sample path to one of the images is:
c:\galleries_incoming\50\69\01 - Getting Ready\DSC_0001.JPG
I'm unsure what to try next. I tried running this command per an old message on the IM forum to get a list of my decode delegates:
convert -list configure
But IM tells me that configure is not a valid list option. In any case, it sounds like installing new decode delegates is something that requires a recompile, and I've just been relying on precompiled binaries (which I would assume would at least be able to read a jpeg).
I'm using ImageMagick to turn my pdf pages into images. It works just fine with default settings but if I try some options, it keeps telling me command not found
For now, I'm doing all this from a SSH client.
The command I'm attempting is:
-quality 90 /usr/bin/convert public_html/so/November-2015.pdf[0] output.jpg
It works just fine without the quality part. I also tried density with no success.
I found out my issue, although I saw this format on other answers the way it works for me is if I put quality -90 after bringing up convert which makes alot of sense now that I think about it.
/usr/bin/convert -quality 90 public_html/so/November-2015.pdf[0] output.jpg
Users can upload images to my page. The problem is that when I try to convert them I get these errors:
gm convert: Improper image header
gm convert: Memory allocation failed
I can see them in Firefox/Safari/Chrome without a problem. Is there a way to "fix" these images command line. Some other utility to read and save them into a correct(non corrupt) format? Or maybe let graphicsmagick ignore these errors?
I hope you can solve this or at least tell what to do about it because I'm clueless. The thing is that once I've saved a .wxm file and then want to open it appears on wxMaxima this error and the "app" crashes:
Maxima encountered a Lisp error:
decoding error on stream
<SB-SYS:FD-STREAM for "socket 127.0.0.1:62607, peer: 127.0.0.1:4011"
{13F30991}
(:EXTERNAL-FORMAT :ASCII):
the octet sequence (195) cannot be decoded.
Automatically continuing.
To enable the Lisp debugger set debugger-hook to nil.
Thanks in advance.
P.S.: I run the latest Mac OS X version on my iMac.
Create a new file and write it down.
(setf sb-impl::*default-external-format* :utf-8)
(setf sb-alien::*default-c-string-external-format* :utf-8)
Save the file as .sbclrc at Home (User) folder.
I come back on this post as I have been affected by this today.
I am using Ubunutu 14.04 and the same bug appears. To me it is due to Maxima not being able to load anything else than ".mac" files, nothing to do with utf-8/ASCII (I have mv a file that is working to a wxm and vice-versa, it will not work anymore / rework)
Also I have prepared a workaround:
The idea is too have a tool that translates your .wxm files to a .mac file just before you load it (it is actually a very easy bash script)
So:
you put the wxm-to-mac.sh files into your path
then inside maxima, instead of doing
load("foo.wxm")
you simply do
system("wxm-to-mac foo.wxm")$
load("foo.mac")$
Bare in mind you shall not edit the foo.mac file because a routine might re-erase it afterward. Instead keep editing the .wxm file.
Hope it helps someone
Looks like the file has been saved with some non-ASCII characters (e.g. UTF-8) in it, but it is not read as UTF-8; that seems to be a bug in wxMaxima. Can you please post the offending .wxm file?
I was having the same problem, since none here could give a straight and correct answer (at least is not marked with the green icon) i tried to look somewhere else. I couldn't find an answer that solve my problem, but then i thought that i had used WxMaxima on Mac before and it worked pretty nice. The last time i installed wxmaxima on mac and it worked was in september 2012, i went to the http://sourceforge.net website and searched for the maxima file that was available on that date and i found http://sourceforge.net/projects/maxima/files/Maxima-MacOS/5.18.1-MacOS/, i installed it and its working pretty fine (about the problem, it is weird, even if i create a new maxima file typed "a" and saved it, i could no longer open it, so i'm guessing that it has nothing to do with ascii or non-ascii characters) I have no idea why this error happens on the recent version of Maxima/WxMaxima, but it makes no sense that we have to install a previous version for it to work.
Anyway, it's working for me, and i hope it works for you too. Glad i helped :)
I had the same problem.
In my case, the name of the directory where the ".wxm" file is located, contained Korean letter. I changed the directory name with an English one.
Then the problem has been solved.
I hope this works for you, too.
is there anybody out there, with experiences about how to do a gantt-diagram / chart using latex.
I tryed it for a lot of hours today, lastly it worked switching outpout from pdf to dvi.
Maybe someone can tell me what to include, besides pst-gantt, and the normal pstricks stuff.
It showed more than 100 errors for 4 Tasks.. after switching to dvi there was a big 0.
i am using the whole distribution mitex .. upgradet to the newest version. stupidly i have the error log not avaible on this computer. but it was always the same error. i was using pst-gantt, outload missing packages.. hm errors will follow tomorrow morning
Reading the pst-gantt README it looks like this depends on the pstricks package. I believe that the "ps" is for postscript and the functionality is implemented by generating DVI "special" commands; which means that you can't produce output pdf directly using pdflatex. You can get to PDF output, but you must go by way of DVI. Either source->DVI->PDF or even source->DVI->PS->PDF.
I came across this question when having trouble with pst-gantt and pdflatex. As others have pointed out you need to go via DVI, which honestly sucks if you have used pdflatex all the time.
So I did some search, and found this phantastic replacement written by Martin Krumm: http://www.martin-kumm.de/tex_gantt_package.php