> As for the problem--I actually think this IS what we want. It > shows up in the page exactly how it shows up the edit box. Same as if > you entered < -- which I suspect before would have automatically > converted to < in the display and in a text box. Now, in either case, > you get exactly what you put in. > > If we want to convert to a literal non-breaking space, we would > just need to get a markup rule for that. So when you edited it, you > can retain the in your edit box. But in general I think our > first goal is to get the page display and what shows in the edit box > to be as close as possible (apart from markup). And then secondarily > to have the source page close as well. >
Sorry, I beg to differ on this one. I want to be able to enter HTML special character code as code with the expectation that the HTML output decodes it (as any browser does), unless I escape it with some special code escape markup to show as code. Or if I enter HTML character code on a code page I want the page to save with the code intact, and the page to display with th ecode not decoded (because it is a code page and I expect to see the code). Before this last version HTML character codes were not saved, instead they were decoded, and that was saved. With this latest version HTML character codes are not saved either, but each '&' is replaced by '&' I just want them saved as I entered them, letter by letter. As to entering characters like < and >: I also want them to be saved as they are. But if or when they are used for output in a normal page, they should be HTML encoded in order to play safely. Same for displaying them in a code page. But if a snippet with such characters is used in a page zone, they should be used as they are, i.e. become working, active code (javascript tags for example). As to '\n' line break code: same as HTML special characters. Save it as it is. Display it as written. If it is in a code page, use it as line break when the snippet gets used. There should be no need for double encoding as it happens with the latest release. Cheers, Hans --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
