Woops, silly me for not searching previous posts... and shame on me for finding I was the one who asked the question the last time. It's turning out to be one of those days...Anyway, here was Tung's original reply to my own foolish question.
"set sgmlselection=off" should fix it.
On 5/29/07, Keith Berard <
Hopefully this will have an easy solution, but it is a problem that has been getting worse for us over time.
It seems that when one of our writers pastes a URL
(from IE, FireFox, etc) into Epic, any instance of an ampersand followed by a word gets somehow auto-translated into an entity. This causes completeness errors, as the value is not an entity.
For example, given the url
Epic seems to interpret "three" as an entity, and post-paste, the XML looks like this:http://www.somesite.com/blah.asp?one=two&three;=four
This makes three show up as an entity in Epic, rather than just an argument within the URL
, causing a completeness error.
To make things easier, our writers do not use any entities, so I'd just as easily be willing to disable all entities if possible.
On a related note, we're still stuck on UTF-8 and have problems when writers paste things like the copyright symbol from Word, etc. If we can disable the paste of such characters (we'd prefer <superscript>3</superscript> to ³ and <copyright>2007</copyright> to ©2007) that would be great, but it's secondary to the first issue.
Thanks in advance for any suggestions.
XML Systems Analyst
Milliman Care Guidelines LLC, A Milliman Company
719 Second Avenue, Suite 300
Seattle, WA 98104
Tel +1 206 firstname.lastname@example.org
Delivering evidence-based knowledge at the point of care