For one I ran across, You can't have a '&' in your data.
In this text field on my PO, in the text field the user had typed "type 1 & 2 items"
that barfed when printing:
I can imagine using a REPLACE_PATTERN on the field before printing, BUT if its ALREADY html, then its going to be loaded with &s;
any URL with query parms will have a valid "&" inside the html.
Or consider a non-breaking space: (this could easily be inserted by someone when they are creating their verbage in the HTML editor)
How do we replace "Bob & Ted", or "Bob &Ted" and get "Bob & Ted"
and yet NOT transform or any number of other valid escaped thingies.
OK, so moving on, I just removed the 2 instances of "&" and got past that error.
We all know how much of a pain it is to build a string with embedded quotes.
Cleaner now with SQ() and DQ(), but it was doable before using SystemSettings.DQ
I usually get away with NOT putting double quotes around the style="color:red" types of html. Browser seems to parse it just fine. And since it was a lot of work to clutter the expression with SystemSettings.DQ, since it worked, I skipped it. But not in the HTLM Report now. Thats thing will complain.
I designed it using "class", but it ignores it. A lot more effort for inline styles. I just haven't removed the class descriptors.
And I wanted the option to format each element in the future, which is why they all got a class originally.
I'm building this string and had to add all the quotes tonight to get it working (although poorly).
