Thanks Chris, you did not miss the garbled example. Other stuff I cited was just to show there are code snippets, not to show exact garbled examples.
As I work in the database software field, my suggestion to you is to add a field to the database table used for storing the messages with initially two options. One option is "no markup" and the next option is "markdown". In the future you could add other options such as "html", "xml", "bbcode" or whatever formatting that might be used. This field dictates how you treat the text for rendering on the web or emails. With "no markup" there is no treatment of special characters as markdown codes. --- ** [tickets:#6822] Option to bypass or escape markdown** **Status:** open **Created:** Thu Oct 31, 2013 08:41 PM UTC by Dave Brondsema **Last Updated:** Fri Dec 06, 2013 02:07 PM UTC **Owner:** nobody All textareas take markdown input, but if you don't realize that and just type or paste something (e.g. code sample, log file) then certain chars may convert into markdown syntax and not render as actually intended. A checkbox near preview & formatting help buttons could be added. (Maybe expand to a full toolbar to help with syntax some day). Changing the data storage for every artifact and the render calls for every artifact is a lot of work and makes the whole system a bit more complex. If we can use markdown syntax to escape the whole content of the entry, that could work out pretty well I think. Requested via [forge:feature-requests:#134] and [forge:site-support:#3470] --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
