13 results found

1. 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 from the way it is calculated for regular viewing of the 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… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  C++ SDK  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. 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_regex

   When a plug-in compiled against SDK 16.0 is used with InDesign 2021 16.1, this entry point does not exist any more.

   Instead, the equivalent entry point is now boost::re_detail_107200 and boost::re_detail_106500 does not exist in InDesign 2021 16.1

   That causes the plug-in to crash InDesign.

   As a result, plug-ins that use boost_regex that are compiled for 2021 16.0 are incompatible with 2021 16.1 and vice-versa.

   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_regex

   When a plug-in compiled against SDK 16.0 is… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  C++ SDK  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. 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 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  C++ SDK  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   FIXED  ·  AdminRavi Kiran (Admin, Adobe InDesign) responded

   The 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

4. 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, InDesign often fails to recognize and interpret the half-space correctly. This leads to formatting disruptions, broken words, or incorrect letter joining, impacting the text flow and readability.

   Headers: If the half-space character is present in headers, InDesign may not handle or display it properly, which can result in incorrect alignment or missing characters, detracting from the document's professional appearance.

   Indexing Issues: During index creation, InDesign does not correctly recognize the half-space character within Persian words. This causes indexing errors, which are particularly problematic in Persian publications, as they lead to incomplete or inaccurate index entries.

   Dictionary and Spell Check Errors: Although custom Persian dictionaries include the ZWNJ character, InDesign frequently fails to recognize words containing it, incorrectly flagging them as misspelled. This hinders the efficiency and reliability of the spell-checking and proofreading process.

   The ZWNJ character (\u{200C}) is essential for proper Persian script handling, as it controls word joins and ensures accurate typesetting. Addressing these issues would greatly enhance the software’s functionality for Persian-speaking users and improve the precision of Persian-language typesetting in Adobe InDesign.

   Thank you very much for your attention to these concerns. We hope that the Adobe team will prioritize full support for the Persian half-space character in future updates to InDesign. Your support on this matter would make a substantial difference for Persian-language users worldwide.

   Sincerely,

   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,… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  C++ SDK  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  C++ SDK  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. 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 above function call now correctly returns false. After quitting and restarting InDesign, the preferences still return false, the correct state.

   Looks like the preferences are NOT setup on first launch, but use a boolean default value of "true".

   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… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  C++ SDK  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Need Control over Adobe Fonts

   Currently there is no straightforward way to detect Adobe Font usage in a document. There needs to be an API to determine which fonts are used in the document (exists) and of those fonts which of them are auto-activated Adobe fonts (does not exist). In addition, it would be great to expose an method for forcing Adobe Fonts used in the document to be activated, and for monitoring the status of the activation. Of course, you can enable auto-activation for the document to trigger when it is opened, but this seems somewhat unreliable in our experience, and in any case there is no method to monitor the state of the font activation, so the plug-in does not know when the activation has been completed.

   Currently there is no straightforward way to detect Adobe Font usage in a document. There needs to be an API to determine which fonts are used in the document (exists) and of those fonts which of them are auto-activated Adobe fonts (does not exist). In addition, it would be great to expose an method for forcing Adobe Fonts used in the document to be activated, and for monitoring the status of the activation. Of course, you can enable auto-activation for the document to trigger when it is opened, but this seems somewhat unreliable in our experience, and in any case… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  C++ SDK  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  C++ SDK  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. FINESTRA DEI COLLEGAMENTI

   Come nella immagine allegata, la parte delle informazioni di collegamento appare trasparente. Così risulta illeggibile e inutilizzabile.

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  C++ SDK  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. 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 - this->fAbsolutePositionInBuffer;
    
        // SHOULD THIS NOT BE `pnum >= numLeftInBuffer`? 
                // If we exhaust the buffer exactly, we are also at EOF
        if (pnum > numLeftInBuffer) 
        {
            numToTransfer = numLeftInBuffer;
            fStreamState = kStreamStateEOF;
        }
        else
        {
            numToTransfer = pnum;
        }
        if (numToTransfer > 0)
            memcpy(buffer, fMyBuffer + fAbsolutePositionInBuffer, numToTransfer);
    
        fAbsolutePositionInBuffer += numToTransfer;
    
    } while (false);
    return numToTransfer;
    

    }
    ...
    ```

    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 -

    … more
    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  C++ SDK  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. issue with find/replace in Text block, the option of article direction is missing in REPLACE panel

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  C++ SDK  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  C++ SDK  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. SDK

    Suport C++SDK

    • 

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  C++ SDK  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating