Adobe InDesign: SDK/Scripting Bugs and Features
-
INumberConverter being ignore when exporting PDF
I am using CC 2017, but it has been an issue for multiple versions.
I have a custom plugin that implements INumberConverter on kPageNumberingStylesService Boss for a custom numbering format. This works beautifully until I try to export to PDF. If I print to PDF Distiller it works fine, but when I export to PDF it exports with default numbering style.
This is similar to an old stubborn bug, when exporting book to PDF would not do the numbering correctly. I don't know that it is related, but they both seem to say that the numbering on export is decoupled…
5 votes -
Bug in IXMLOutStream.h header file
InDesign2020SDK/source/public/interfaces/xmedia/IXMLOutStream.h:499
void WriteName(const UTF16TextChar* name, bool16 newLine = kFalse)
{ this->WriteName(name, newLine); }This function calls itself. It leads to a stack overflow on Windows but the code analyzer in Xcode catches it and reports an error during compilation. It can be changed to:
void WriteName(const UTF16TextChar* name, bool16 newLine = kFalse)
{ this->WriteName(WideString(name), newLine); }and it will work (it calls the previous function in the file instead).
3 votesThanks for reporting the issue. We are reviewing it
-InDesign Team
-
Enable XML export in Word file format so tagging and attributes are preserved.
InDesign cannot currently export an XML structured file in Word file format, either because Word does not recognize the tags and attributes or because those elements are not within the document content. Please make an export possible so that XML structured content can be exported in Word file format and then reimported into InDesign.
1 vote -
1 vote
- Don't see your idea?