Skip to content

Adobe InDesign: Bugs

When filing a new bug, please provide:

  1. Version of Adobe InDesign, InCopy or InDesign Server
  2. Steps to reproduce the issues
  3. Expected result
  4. Actual result
  5. Test file, screenshot, video or GIF capturing the issue (optional)
If you are facing a crash in InDesign, please submit the crash report as well. How to Submit Crash Report
Join the InDesign Prerelease Program to try out the new features and the bug fixes that are available in beta builds.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

1 result found

  1. [macOS] soft return converted to hard return in InDesign Tagged Text

    Affected version:
    14.0.3 [macOS]

    Steps to reproduce:
    In a New document, make a new text container.
    Enter this sample text:
    “line1 \n line2 \r line3 \n line4”
    where \n = shift+return
    and \r = return
    Set space before or space after to 0.125”
    Export as Adobe InDesign Tagged Text, Unicode format.
    Import result using File > Place

    Expected result
    Soft returns and hard returns

    Actual result
    Hard returns only (soft returns converted)

    16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thanks for your patience all this while. We investigated on this issue and below are our findings. The problem with this bug is related to ages old standards difference between different operating systems.
    On Mac (OS X and later) there is only one way to identify line end i.e by using a single character LF, while on Windows (and DOS before it) uses a pair of CR and LF characters to terminate lines.
    Hence when writing them down to any text file these characters are written as such.
    Windows, can therefore dedicate LF to understand soft return separately while Mac cannot do any
    such thing. Because of this when we read it back from the text file the LF character is interpreted as line break (or new para) on Mac and soft return on Windows.

    These files require conversion when moved from one OS to another

    Consider this…

  • Don't see your idea?

Feedback and Knowledge Base