Adobe InDesign: SDK/Scripting Bugs and Features
12 results found
-
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 -
Some plug-ins compiled for InDesign 2021 16.0 crash InDesign 2021 16.1 - the 16.0 and 16.1 SDK are incompatible
When a plug-in relies on the embedded Boost framework to support regular expressions, it can cause a crash because of unresolved dependencies.
The issue is that the 16.0 SDK uses Boost 1.65 and the 16.1 SDK uses Boost 1.72
Plug-ins compiled against the 16.0 SDK that use regular expressions will try to access an entry point
__ZN5boost16re_detail_10650018get_default_syntaxEh(unmangled:boost::re_detail_106500) when handling regular expressions.The problem is that this entrypoint's name is dependent on the Boost version (1.65).
This entry point is provided by the (on Mac) embedded framework
/Applications/Adobe InDesign 2021.app/Contents/Frameworks/boost_regex.framework/Versions/A/boost_regexWhen a plug-in compiled against SDK 16.0 is…
4 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).
4 votesThe fix for this issue is now available in the latest versions of InDesign – version 16.0 and above.
Please update to this version to get the fix.—
Adobe InDesign team -
Request for Full Support of Persian Standard Half-Space (\u{200C})
Subject: Request for Full Support of Persian Standard Half-Space (Zero-Width Non-Joiner: \u{200C}) in Adobe InDesign
Dear Adobe Support Team,
I am reaching out to highlight some significant issues with Adobe InDesign’s handling of the Persian half-space character, also known as the zero-width non-joiner (ZWNJ), encoded as \u{200C}, which is widely used and essential for accurate Persian typography. InDesign currently does not fully support this character, which leads to numerous issues that affect document formatting and usability for Persian-language users.
Specific Issues with Persian Half-Space Support
Text Import from Microsoft Word: When importing Persian text from Word documents that contain ZWNJs,…2 votes -
Simple script crashes vanilla InDesign 2024 19.5 Debug version
Running this simple script (tested on Mac x86, Mac M1, and Windows) will crash Adobe InDesign 2024 Debug. It will not crash Adobe InDesign 2024 (regular version).
2 votes -
False state with app.gpuPerformancePreferences.enableGpuPerformance if no GPU available
Function GetEnableGPUPerformance() of interface IGPUPerformancePrefs of GetExecutionContextSession()->QueryWorkspace() returns true in case no GPU or a not supported GPU is installed on your macOS computer.
To reproduce launch InDesign CC 2018 or later with modifier keys command, option, control, and shift pressed and confirm resetting the preferences.
If you now check the setting either with some C++ code, or ExtendScript "app.gpuPerformancePreferences.enableGpuPerformance", in both cases the returned result is true , which is not the expected result.
When you now choose Preferences > GPU Performance the properties are shown deselected and disabled, which is correct. If you now click in "OK", the…
2 votes -
Inserted special character for current page number is not refreshed from the plugin since version 20.0
Inserted special character for current page number is not refreshed from the plugin since version 20.0.
In previous versions, after adding a new section using kNewSectionCmdBoss, the page information was refreshed.
Now the section is changing, the page number in the information bar at the bottom is correct, but the page number in the text frame with inserted special character has stopped updating.When the same is done via the Sections window in Indesign (Numbering & Section Options) with the start of new section field set, it works.
1 vote -
FINESTRA DEI COLLEGAMENTI
Come nella immagine allegata, la parte delle informazioni di collegamento appare trasparente. Così risulta illeggibile e inutilizzabile.
1 vote -
Potential bug in IDHAMemoryXferBytes.cpp
Not 100% sure, but I think there is a small 'off by one' bug in IDHAMemoryXferBytes.cpp.
It's possible it is not causing issues - it all depends on what the calling code does with the class.
I think
pnum > numLeftInBuffer
should really be
pnum >= numLeftInBuffer
otherwise the routine does not flag EOF when we happen to request the exact number of remaining bytes.
See line with comment before it:
```
...
uint32 IDHAMemoryXferBytes::Read(void* buffer, uint32 pnum){
uint32 numToTransfer = 0;
…do { if (buffer == nil) { ASSERT_FAIL("buffer is nil!"); break; } uint32 numLeftInBuffer = this->fCountBytesStored -1 vote -
1 vote
-
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?