- Package:
- imagemagick-doc
- Source:
- imagemagick
- Submitter:
- David Baron
- Date:
- 2023-04-06 15:18:03 UTC
- Severity:
- wishlist
Using convert inputfile g3:outputfile The width of the inputfile image is not honored in the output image which is then several times too wide. Faxing the g3 image works but the results are not always good (may or may not be because of this bug).
severity 514321 normal tag 514321 + moreinfo thanks Could you please send us a test case ? Could you retest with experimental version ? Regards Bastien
severity 514321 normal tag 514321 + moreinfo thanks Could you please send us a test case ? Could you retest with experimental version ? Regards Bastien
convert resume.pdf 3g:resume.002 yielded that attach results with the version on Sid. the experimental version creates a file 3g\:resume.002 !!!! which has an incorrect result entirely. If the command line options have changed, the man page needs be updated. Tell me how to retest.
convert resume.pdf 3g:resume.002 yielded that attach results with the version on Sid. the experimental version creates a file 3g\:resume.002 !!!! which has an incorrect result entirely. If the command line options have changed, the man page needs be updated. Tell me how to retest.
forwarded 514321 http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=13136 thanks Forwarded to upstream Bastien
severity 514321 wishlist thanks Hi, You type convert resume.pdf 3g:resume.002 instead of convert resume.pdf g3:resume.002 Could you retest using density operator convert -density 200 resume.pdf g3:im.fax The g3 format is a fixed width of 1728 as required by the standard. Will link to documentation issue Regards
Are you referring to unstable/testing or experimental? I put unstable back. Easy enough to try. Which one is supposed to be correct? In any event, outputting a file named "3g:...." is not desired behavior. Linux will eat it. Windows will certainly not. Beautiful. Gave me a normal page layout and very nice quality as well. Took much longer, however (subjective). OK. I think this width is what I am seeing (but the density 200 image SHOWED the normal page layout in viewfax). There is some confusion in the "magic" numbers. The output of a ghostscript conversion is shown as a page format rather than that fixed width. Imagemagick does not see this as a tiff-g3 (or is it tiff-3g?) format! On the other hand, the mimi-types reported in KDE apparently do not see imagemagick's a such. My code will not call convert on text or tiff-g3 mime-types since efax will eat them. Efax accepts both claimed 3g formats (since one may be a bpm format also acceptable to efix).
retitle 514321 Documentation bug: document density for fax image thanks Both 3g is not a Fax format it is g3 (dylexia ;) ) Therefore if you use 3g convert will flatten ie convert to bitmap your pdf and store as pdf (check with file the output). According to upstream it is : Sorry ? Could you If you specify 3g it is normal. Please send input and output each time you suspect incorrect behavior Yes, but fill a bug against kde :) Lack of context I supose, Do not understand :) Regards bastien
Yes, dyslexia. I have been using g3. So the typo was in the bug report. If the command format is ... g3:outputfile, then the "g3:" is syntax, not filename. While Debian Linux will allow a file name like"g3\:name" (which is how it displays it, not much else will correctly save a file that way. Anyway, if I want that, I will type ...g3:g3:.... and may the lord have mercy. If we are changing the syntax to something like conver infile -fmt g3 outfile, I'm cool with that. Just let us all know.
Could try the following script shell on experimental and on unstable and post the output ? Please delete all file except pdf and shell script before running it :) Regards
Here are the two files (which are about the same) OK OK, dyslexic'd the experimental try last week -- saw a 3g:\..... file my directory. If 3g is also a legitimate choice, then that file is in error. If it is not, tell me. Sorry about the false alarm but that exposed something else. That density option does the job, if maybe more slowly. Efax-gtk must use a different converter which is much faster than imagemagick because I do not notice delays when using that. I like imagemagick because I can feed it most anything. I use it in my java xjig front-end as well.
No it is not a legitimate choice Ok Could you try to investigate this, but openning a new bugs please. Particularly could you try to get information about efax-gtk converter. THis bug is really about documentation bug and density option for g3 file format. And lack of documentation of g3 format. Thanks
Their docs say ghostscript. They only accept postscript and pdf so ghostscript is a logical choice.
אני יוצר איתך קשר בנוגע לבני משפחתך שנפטרה בירושה ללא תביעות בשווי 5.5 מיליון דולר ארה"ב. השב להודעת דוא"ל זו בהקדם כדי להמשיך בפרטים. שלך תמיד, פרנסואה ברנדאו, (עורך דין)
בבקשה, מהי הדרך הטובה ביותר ליצור איתך קשר? שלחתי לך מייל אבל זה חזר, תענה בדחיפות