pdf24-DocTool.exe floods the command shell with lots of output

Start › Foren › PDF24 Creator › pdf24-DocTool.exe floods the command shell with lots of output

Ansicht von 5 Beiträgen – 1 bis 5 (von insgesamt 5)
  • Autor
    Beiträge
  • #17129
    berniestn
    Teilnehmer

    Hello,

    since years I've been using pdf24-DocTool.exe to frequently convert docx files to pdf. Now I installed pdf24 version 11.13.2 and whenever I convert, I get lots of output in the shell. For example, my 9 page document results in the following output:

    C:\Users\bernie>"C:\Program Files\PDF24\pdf24-DocTool.exe" -convertToPDF -profile default/good D:\testfile.docx -outputFile D:\testfile.pdf

    C:\Users\bernie>Attached
    ================
    "C:\Program Files\PDF24\pdf24-DocTool.exe" "D:\testfile.docx"
    ----------------

    -->================
    ================
    "C:\Program Files\PDF24\gs\bin\gswinc.exe" -dBATCH -dNOPAUSE -dSAFER -dALLOWPSTRANSPARENCY "-sFONTPATH=C:\WINDOWS\Fonts;C:\WINDOWS\Fonts" -dNEWPDF=true -sDEVICE=pdfwrite -dPDFSETTINGS=/prepress "-sOutputFile=C:\Users\bernie\AppData\Local\Temp\PDF24\0_52864000_1071277023.pdf" -dCompatibilityLevel=1.7 -dAutoRotatePages=/PageByPage -dEmbedAllFonts=true -dSubsetFonts=true -dProcessColorModel=/DeviceRGB -dColorConversionStrategy=/LeaveColorUnchanged -dPreserveAnnots=true -dAutoFilterColorImages=true -dAutoFilterGrayImages=true -dAutoFilterMonoImages=true -r300 -dColorImageResolution=300 -dGrayImageResolution=300 -dMonoImageResolution=300 -dDownsampleColorImages=true -dColorImageDownsampleType=/Bicubic -dColorImageDownsampleThreshold=1.0 -dDownsampleGrayImages=true -dGrayImageDownsampleType=/Bicubic -dGrayImageDownsampleThreshold=1.0 -dDownsampleMonoImages=true -dMonoImageDownsampleType=/Subsample -dMonoImageDownsampleThreshold=1.0 -dPassThroughJPEGImages=false -c " <</ColorImageDict <</QFactor 0.25 /Blend 1 /ColorTransform 1 /HSample [1 1 1 1] /VSample [1 1 1 1]>> >> setdistillerparams <</GrayImageDict <</QFactor 0.25 /Blend 1 /ColorTransform 1 /HSample [1 1 1 1] /VSample [1 1 1 1]>> >> setdistillerparams <</ColorACSImageDict <</QFactor 0.25 /Blend 1 /ColorTransform 1 /HSample [1 1 1 1] /VSample [1 1 1 1]>> >> setdistillerparams <</GrayACSImageDict <</QFactor 0.25 /Blend 1 /ColorTransform 1 /HSample [1 1 1 1] /VSample [1 1 1 1]>> >> setdistillerparams" -f "C:\Users\bernie\AppData\Local\Temp\PDF24\DocToolSink\wordToPdf_0_52862359_4172720761.pdf" -c "[ /Creator (PDF24 Creator) /DOCINFO pdfmark"
    ----------------
    GPL Ghostscript 10.01.2 (2023-06-21)
    Copyright (C) 2023 Artifex Software, Inc. All rights reserved.
    This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY:
    see the file COPYING for details.
    Processing pages 1 through 9.
    Page 1
    Loading font ArialMT (or substitute) from C:\WINDOWS\Fonts/arial.ttf
    Page 2
    Page 3
    Loading font Arial-BoldMT (or substitute) from C:\WINDOWS\Fonts/arialbd.ttf
    Page 4
    Page 5
    Page 6
    Page 7
    Page 8
    Page 9
    ================

    C:\Users\bernie>

    If the file has more pages (this is what is typically my use case), the output is even more and hides important messages in my shell script.

    Is there a way to suppress these messages like before? In the command line help, I did not find any option.

    Thanks,

    bernie

    #17130
    Stefan Ziegler
    Forenverwalter

    You can just pipe pdf24-doctool outputs to NUL like this:

    pdf24-doctool.exe ... >NUL  2>NUL
    #19037
    berniestn
    Teilnehmer

    Thanks Stefan for your suggestion, this is what I already did as a workaround. However, I thought it is worth mentioning this issue, because the behavior suddenly changed after upgrading to the latest version. I thought this is a bug which might probably be fixed in one of the newer versions.

    #20257
    PDF24 Support
    Moderator

    Hello,

    thank you for reporting this, you were right. The fix will come with the next version: the DocTool no longer attaches to the console of the caller on every start, and successful conversions no longer write anything to the console (also no Ghostscript output). Until then, redirecting the output with >NUL 2>NUL remains the workaround.

    #20575
    berniestn
    Teilnehmer

    Perfect, that would be great. Until then the workaround works fine for me.

Ansicht von 5 Beiträgen – 1 bis 5 (von insgesamt 5)
  • Du musst angemeldet sein, um auf dieses Thema antworten zu können.