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
   “line1{{shift+return}}line2{{return}}line3{{shift+return}}line4”
   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

   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  ·  Text/Story/Table  ·  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
   Closed: Different Product  ·  amaarora responded

   Hi,
   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 article for more information: https://www.oreilly.com/library/view/mac-os-x/0596004605/ch01s06.html
   A same analogy is found in excel when saved as a text file

   Thanks

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