Indesign ошибка чтения изображения jpeg

Is there anyone who can help me resolve this error? The error message does not specify the problematic image, and Preflight does not provide any clues either. Identifying the problematic image is difficult since I have used multiple jpeg files in my layout.

Export: … Failed. See Alert.

An error has occurred during the
reading JPEG
image processing. It’s possible that the image is either damaged or incompatible. Attempt resaving the image with different settings and try the process again.

Here are some options to consider prior to exporting:

• Take a look at your
  
Links

  dashboard to determine whether there are any images that are either damaged or absent.
• Check for any errors by performing a
  
Preflight

  .
• Verify if there are any images remaining beyond the boundaries of your artboards.
• Determine whether any of the images are currently open or unsaved in other software applications like Photoshop or locked in a syncing tool like Dropbox or Google Drive, or stored on an external drive.

For a while now, I have been facing an issue with exporting my »
Proofing» script
» document in InDesign to two different file formats, one of which is password-protected. While the second file format doesn’t cause any issues, the password-protected one often gets corrupted and can’t be opened by any PDF reader, including Acrobat. The exporting code that I am using is not a standalone program and is responsible for the issue.

/********** BEGIN PDF EXPORTING **********/
// First, let's create and set PDF export preferences.
// This begins with creating a temporary preset if it doesn't already exist.
// This preset will be used for both the Proof page and the Cover sheet.
var tempPreset = app.pdfExportPresets.item("tempPreset");
try
{
    tempPreset.name;
}
catch (eNoSuchPreset)
{
    tempPreset = app.pdfExportPresets.add({name:"tempPreset"});
}
with (tempPreset)
{
    acrobatCompatibility = AcrobatCompatibility.ACROBAT_5;
    bleedMarks = false;
    colorBars = false;
    colorBitmapCompression = BitmapCompression.AUTO_COMPRESSION;
    colorBitmapQuality = CompressionQuality.MAXIMUM;
    colorBitmapSampling = Sampling.BICUBIC_DOWNSAMPLE;
    colorBitmapSamplingDPI = 300;
    compressTextAndLineArt = true;
    cropImagesToFrames = true;
    cropMarks = false;
    exportGuidesAndGrids = false;
    exportNonprintingObjects = false;
    exportReaderSpreads = false;
    exportWhichLayers = ExportLayerOptions.EXPORT_VISIBLE_PRINTABLE_LAYERS;
    generateThumbnails = false;
    grayscaleBitmapCompression = BitmapCompression.AUTO_COMPRESSION;
    grayscaleBitmapQuality = CompressionQuality.MAXIMUM;
    grayscaleBitmapSampling = Sampling.BICUBIC_DOWNSAMPLE;
    grayscaleBitmapSamplingDPI = 300;
    includeBookmarks = false;
    includeHyperlinks = false;
    includeSlugArea = false;
    includeStructure = true;
    monochromeBitmapCompression = MonoBitmapCompression.CCIT4;
    monochromeBitmapSampling = Sampling.BICUBIC_DOWNSAMPLE;
    monochromeBitmapSamplingDPI = 1200;
    omitBitmaps = false;
    omitEPS = false;
    omitPDF = false;
    optimizePDF = true;
    pageInformationMarks = false;
    pageMarksOffset = 0.0833;
    pdfMarkType = MarkTypes.DEFAULT_VALUE;
    printerMarkWeight = PDFMarkWeight.P25PT;
    registrationMarks = false;
    standardsCompliance = PDFXStandards.NONE;
    subsetFontsBelow = 100;
    thresholdToCompressColor = 450;
    thresholdToCompressGray = 450;
    thresholdToCompressMonochrome = 1800;
    useDocumentBleedWithPDF = false;
}
currentProcess.text = "PDF export preferences"; progressWin.show();
progressIndividual.value++; if (aProducts.length > 1) {progressOverall.value++;}
// Now let's actually set the export preferences.  These are for the proof page.
with (app.pdfExportPreferences)
{
    pageRange = proofRange;
    useSecurity = true;
    disallowChanging = true;
    disallowCopying = false;
    disallowDocumentAssembly = true;
    disallowExtractionForAccessibility = false;
    disallowFormFillIn = true;
    disallowHiResPrinting = true;
    disallowNotes = true;
    disallowPlaintextMetadata = true;
    disallowPrinting = false;
    changeSecurityPassword = "sky";
    if (multiColor)
    {
        pageRange = colorTable.toString();
    }
    if (currentProduct.pLabel != "")
    {
        pageRange += "," + labelPage.name;
    }
}
currentProcess.text = "Exporting PDF proof page"; progressWin.show();
progressIndividual.value++; if (aProducts.length > 1) {progressOverall.value++;}
// Before exporting the Proof page(s), hide the color bar on multicolor products.
if (multiColor) {document.layers.item("COLOR BAR").visible = false;}
// Then we save the proof page.
document.exportFile(ExportFormat.PDF_TYPE, File(jobFolder.toString() + "/" + saveName + ".pdf"), false, tempPreset);

In instances where the PDFs were corrupted, I suspected our network structure might be to blame. To test this theory, I opted to export the PDF files to the local hard drive first instead of directly to the network. Afterwards, the file was moved to the network. As a result, I replaced the last line in the code block above.

// First, to the local HDD.
document.exportFile(ExportFormat.PDF_TYPE, File("~/Documents/" + saveName + ".pdf"), false, tempPreset);
$.sleep(1000);
File("~/Documents/" + saveName + ".pdf").copy(File(jobFolder.toString() + "/" + saveName + ".pdf"));
$.sleep(1000);
File("~/Documents/" + saveName + ".pdf").remove();

Despite incorporating 1-second delays as a precautionary measure, the issue of receiving corrupt PDFs still persists. Any potential patterns in the occurrence of these corrupted files have yet to be identified. Would anyone happen to have any suggestions or insights on this matter?

After realizing that corrupted files cannot be opened in Acrobat, I developed a loop to export the PDF file and check if it opens in Acrobat. If the file opens successfully, it is printed and closed, returning a «true» message. If not, a «false» message is returned to the script, and the loop continues until the message is «true». Although it is not a permanent solution for the root cause of the issue, it serves as a workaround that meets our requirements. The only difference is that, because we use Macs, the message is routed through an AppleScript rather than using BridgeTalk to communicate directly with Acrobat.

This is the snippet of code present in the primary loop for PDF verification in
InDesign script
.

// Then we save the proof page.
// The loop is to make sure that the file was saved properly.
var validFile = false; // Flag that states whether or not the file is corrupted after saving.
var rString; // String returned from Acrobat that should be either "true" or "false".
var testAndPrintFile = File("~/Documents/testAndPrint.applescript"); // The applescript file that calls Acrobat and runs a folder-level script.
var pdfFile; // A String of the filename & path that will be passed to through the applescript file to Acrobat.
var pdfArray = new Array(4); // An array to send to Acrobat.  [0] is the PDF filename as a String,
                             // [1] is duplex if true, [2] is the printer name, and [3] is to enable printing.
if (multiTwoSided || twoPages) pdfArray[1] = "true";
    else pdfArray[1] = "false";
pdfArray[2] = localPrinter;
pdfArray[3] = "true";
while (!validFile)
{
    $.writeln("If this message is seen more than once, then the Proof PDF was corrupted.");
    try
    {
        document.exportFile(ExportFormat.PDF_TYPE, File(jobFolder.toString() + "/" + saveName + ".pdf"), false, tempPreset);
    }
    catch (e)
    {
        alert("Could not save the Proof PDF.  Please close any open copies of the Proof PDF, then save and print it manually.");
    }
    pdfFile = jobFolder.toString() + "/" + saveName + ".pdf";
    pdfArray[0] = pdfFile;
    $.writeln("pdfArray contains: " + pdfArray);
    try
    {
        rString = app.doScript(testAndPrintFile, ScriptLanguage.APPLESCRIPT_LANGUAGE, pdfArray);
        validFile = rString == "true";
        // validFile = true;
        $.writeln("validFile is " + validFile);
        if (!validFile)
        {
            alert("It seems that the file " + unescape(pdfArray[0]) + " is corrupted.  Will try to export it again.");
        }
    }
    catch (e)
    {
        $.writeln("ERROR at line number " + e.line);
        $.writeln(e.description);
        throw new Error("ERROR at line number " + e.line + "\n" + e.description);
    }
}

The function that this loop invokes, testAndPrint.
applescript file
.

set pdfFile to item 1 of arguments
set duplexed to item 2 of arguments
set printerName to item 3 of arguments
set printEnabled to item 4 of arguments
tell application "Adobe Acrobat Pro"
    set result to do script ("testAndPrint(\"" & pdfFile & "\", \"" & duplexed & "\", \"" & printerName & "\", \"" & printEnabled & "\");")
end tell
return result

The
folder-level Javascript
file is loaded into memory upon starting Acrobat and is prepared to undergo the
function called
process by the aforementioned
Applescript file
.

var testAndPrint = app.trustedFunction(function (fName, duplexed, sPrinterName, bEnablePrinting)
{
    var success = true;
    app.beginPriv();
    console.println("fName is " + unescape(fName));
    console.println("sPrinterName is " + sPrinterName);
    try
    {
        var printDoc = app.openDoc(unescape(fName));
        var pp = printDoc.getPrintParams();
        if (duplexed == "true") pp.DuplexType = pp.constants.duplexTypes.DuplexFlipLongEdge;
            else pp.DuplexType = pp.constants.duplexTypes.Simplex;
        pp.printerName = sPrinterName;
        pp.interactive = pp.constants.interactionLevel.silent;
        pp.pageHandling = pp.constants.handling.none;
        if (bEnablePrinting == "true") printDoc.print({bUI: false, bSilent: true, bShrinkToFit: false, printParams: pp});
        printDoc.closeDoc(true);
    }
    catch (e)
    {
        console.println("ERROR at line number " + e.lineNumber);
        console.println(e.message);
        success = false;
    }
    app.endPriv();
    console.println("success is " + success);
    return success;
});

It is my wish that this information proves helpful to others who encounter a comparable issue. Although it may not be aesthetically pleasing, it is certainly effective in getting the job done.

To create documents,
Adobe InDesign
must be utilized. The document requires several variables such as company name, project name, and others, which must be filled in.

Is there a means to utilize an already existing template and populate it using a preferred programming language such as Python or Ruby? I attempted to modify an Adobe InDesign file using a text editor (Notepad++), but upon opening the file in InDesign, an error message appeared indicating that the file was corrupted.

It would be greatly appreciated if you could provide any assistance in building
InDesign documents
programmatically or if you could recommend any helpful tutorials.

I attempted to explore ExtendScript by Adobe, but didn’t come across any relevant documentation related to InDesign.

Thanks for the help!

It’s not possible to accomplish this task through Ruby/Python in a lawful manner. Although, it’s theoretically feasible to directly modify InDesign files with any programming language, there are certain limitations to it.

1. Modifying the text alone isn’t sufficient, as you need to gain a deeper understanding of the format.
2. If Adobe discovers, you may face legal action as it goes against the terms of the InDesign license agreement.

For minor tasks like this, ExtendScript is an excellent option. By selecting InDesign as the target in
ExtendScript Toolkit
, you can conveniently explore and search the complete API. It is not a daunting task to perform search and replace for basic text variables.

One option could be to transfer the files to the

.idml

format, which is both simpler and permissible to modify outside of InDesign.

Indesign’s DataMerge feature, which is available at https://helpx.adobe.com/indesign/using/data-merge.html, can be utilized.

I believe that this is precisely the item that meets your requirements.

You have the option of utilizing the Indesign API, specifically by referring to the ObjectModel-Viewer in the Extendscript-Toolkit.