incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Tsai" <ct...@users.sf.net>
Subject [allura:tickets] #6822 Option to bypass or escape markdown
Date Fri, 06 Dec 2013 14:07:58 GMT
Hello Fred, I think you're anticipating that Markdown will interfere much more than it actually
does. As you may have noticed from your own inline example of "when x > 2 the color is
user-defined", there isn't anything there at all that's being affected by markdown formatting.

Further, from the example you cite, it actually comes out quite nicely with the Markdown (dare
I say even better than unformatted?). I've copy/pasted the text from that example, which you'll
see below:

----

Given the following:

    CREATE TABLE tab ( name VARCHAR_IGNORECASE(255)) INSERT INTO tab VALUES('fileß.txt')
<--- Note the 'ß' ! the query: SELECT * FROM tab WHERE name LIKE '%txt%'

returns an empty result set! I would have expected that 'fileß.txt' is returned. Changing
the query to:

    SELECT * FROM tab WHERE name LIKE '%tx%' <--- Note the final 't' is missing here

returns 'fileß.txt'!

With name defined as VARCHAR (instead of VARCHAR_IGNORECASE) the first query works as expected.

Is this a bug or some misunderstanding?

(using HSQL 2.3.0)

----

Of course, we can certainly come up with examples where unintended formatting can occur. In
particular, the use of \*'s which you noted in [forge:site-support:#3470] would probably be
the most common case. But in my experience, the number of incidences of unintended formatting
are relatively rare and are IMO worth the trade-off (though, I do appreciate that I encounter
different text patterns than you regularly do).

Other more common issues are when folks paste in snippets that start with #'s or >'s, but
those should be mitigated by options presented in this ticket.

That said, it would be useful to hear your thoughts on our alternative solutions. Like some
of the ones Dave mentions in his last comment.


---

** [tickets:#6822] Option to bypass or escape markdown**

**Status:** open
**Created:** Thu Oct 31, 2013 08:41 PM UTC by Dave Brondsema
**Last Updated:** Thu Dec 05, 2013 06:26 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 allura-dev@incubator.apache.org 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.
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message