Hi,
After initial pilot of our Cute-Editor-enabled solution, we have received raved reception, but one of the tests produced a very odd behavior. And it's not Cute Editor's fault at all.
We have clients who uses spaces to do formatting (yes.. it's true, it turns out not everyone is a Desktop Publishing Guru...*grin*) and if you put enough ampersand-nbsp-semi's together you end up easily exceeding the line length limit of email transport envelopes. Uh, in english, the line length will be chopped by the nearest mail server--doing it's nicest to be a responsible netizen in email land. Unfortunately this is not a very intelligent chop, and we are starting to see random characters show up in the resulting email in the recipient's hands.
Question: Can we add a advisory length limit to the source generated by Cute Editor? It's not absolute, but please introduce a new-line somewhere near the designated length.
We thought it would be just so cute if Cute Editor can help us in preemptively review the object model in memory and do something with the source code. Keeping it under 991 characters would be ideal in our case of sending HTML-formatted emails (as explained in:
http://mailformat.dan.info/body/linelength.html)Example:
A RecommendSourceLength of 20 would do a best effort of
<P>Blah blah <B>BLAH
!</B> blah blah blah.</P>
To
<P>Blah blah <B>BLAH!</B> blah blah blah.</P>
Okay in this case it can do it perfectly, but it would do the right thing, instead of chopping a tag in half, like this:
<HT
ML>
Any help in this regard would be wildly appreciated. Thank you!! :-)
Best regards,
-- David