8.3 file naming issue

Questions and postings pertaining to the usage of ImageMagick regardless of the interface. This includes the command-line utilities, as well as the C and C++ APIs. Usage questions are like "How do I use ImageMagick to create drop shadows?".
Post Reply
rforgo

8.3 file naming issue

Post by rforgo »

I'm not really sure where to look on this, although I have looked through the IM docs and can't find the relevant info. I'm hoping someone here might have experienced this before. Some background first ...

We use IM to convert PDFs to JPEGs on a W2K3 server. Every night we refresh our PDF files and use xcopy to move them to the server for conversion. During the day if new files arrive, they are moved onesy-twosey to the server for processing as they arrive. We have a watch directory app that moves them there as they arrive. When they get there a .bat file is fired and that launches the IM conversion, and it works just fine.

The .bat file reads:
"C:\Program Files\ImageMagick-6.3.7-Q16\convert.exe" "%WD_FILE%" -resize 20%% "%WD_FILE_D%%WD_FILE_B%.jpg"

The problem occurs in the evening when all the files are refreshed. We have another .bat file that runs an xcopy command that copies all the files from the previous day to our server for processing. When the files get there the same .bat file (from above) fires and the conversion begins. But instead of keeping the same file names as the PDFs, the new JPEGs are truncated using an 8.3 naming convention, which makes them useless for our purposes. When we come back and fire the .bat file with the IM commands again, it produces JPEGs with the files names we expect. But the effect is that we have to process the PDFs twice. Has anyone experienced this before? Is there a way to force IM to keep the long file names? Or is this a Windows issue rather than an IM problem?
User avatar
anthony
Posts: 8883
Joined: 2004-05-31T19:27:03-07:00
Authentication code: 8675308
Location: Brisbane, Australia

Re: 8.3 file naming issue

Post by anthony »

The truncation is probably a result of the filesystem and not from IM. IM itself does not care about the filename execept with regard to the suffix to figure out the final format of the image to be read in, or saved.
Anthony Thyssen -- Webmaster for ImageMagick Example Pages
https://imagemagick.org/Usage/
Post Reply