This is a test build.
Give it a try; please report any problems.
This build has two contributions from Nafundi:
https://s3.amazonaws.com/opendatakit.downloads/ODK+Collect+v1.4.7+rev+1052+test.apk
sha256 hash for this download is listed in the sha256 hash file on
Html formatting? Enketo has been supporting markdown for over a year... Would have been nice to match that. Html formatting is insecure in web clients.
Hi Martijn,
I didn't know Enketo had Markdown. Regardless, Markdown doesn't
support color and sizing and that's what we need. I'm not aware of an
easy way to do this in Markdown, but glad to work with you to find a
suitable compromise. Maybe a BBCode-ish format?
As to security, it's true that raw HTML in web clients is potentially
insecure, but Enketo can allow the limited subset of safe tags we
support using a sanitizing library, no?
Yaw
On Thu, Aug 27, 2015 at 9:21 PM, mrijdt@gmail.com wrote:
Html formatting? Enketo has been supporting markdown for over a year... Would have been nice to match that. Html formatting is insecure in web clients.
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
You received this message because you are subscribed to the Google Groups "ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thanks Yaw,
Yes, Enketo has had limited markdown support
http://blog.enketo.org/better-notes/ since 2013 before we all agreed to
start collaborating better on these major additions to the form spec 
(for performance reasons it has only been enabled in notes/readonly
questions, but I just got funding to solve that and expand it across all
labels). It would be nice if all those forms using markdown started working
in ODK Collect as well. But of course the key is here is to not have to
explain to users that there are two different ways to format labels. So
thanks for being willing to look into this further.
We chose markdown (back in 2013), because it would be the least problematic
in clients that didn't support it, showing this instead of this. It's
also very easy to use.
Sure, we could have chosen to sanitize html (back in 2013) but it becomes
very complex if you start supporting more complex tags with attributes such
as links. Needlessly complex (and thus fragile) in my opinion.
If font-size can be supported in headings only we could just use #, ##, ###
tags. I question the need to change font sizes in the middle of a sentence.
Is it important to be able to change colors of individual words? Maybe the
color requirement can be met by changing the color of the whole label,
using an appearance? I like this much better as we separate semantics from
style, in the same manner as we already do in XForms.
Cheers,
Martijn