We recently migrated from 4.3.1 to 5.4. On 4.3.1, the editor did not acknowledge line breaks in the SGML, which is how an SGML editor is supposed to behave. On 5.4, however, line endings in the SGML are recognized and displayed on screen. This makes it very difficult for the authors to search on phrases.
Any ideas? Thank you.
Thanks, Steve. Unfortunately, that had no effect--the line endings in the SGML still are being honored in the editor. I consider this a bug and I am submitting it to PTC. Thanks for taking the time to reply--sounded to me like it would work.
In Reply to Steve Thompson:
Or, you could just set 'outputrecordlength' to 'Infinity' and save the file. No carriage returns.
Setting is found by going to Tools -> Preferences and clicking the "Advanced" button. List is alphabetical.
When the only tool you have is a hammer,
Everything looks like a hard disk...
I've attached a Word document that illustrates the problem.
The first line of text, "FS 158.00 BULKHEAD" has a carriage return at the end. On our prior version of EPIC 4.3.1, EPIC would ignore carriage returns, soft-wrapping text where it saw fit. The author expects to be able to search on phrases like
"FS 158.00 BULKHEAD CAP, PN 16B1240"
So the issue is simply that we would lile Arbortext Editor to ignore carriage returns like it used to.
Steve: I think I replied to you at the wrong point in the thread. Anyways, at the end is a post with an example of my issue.