Am Donnerstag, 27. Februar 2014 12:28:03 UTC+1 schrieb Jeremy Ruston: > > The tiddler-dictionary format is intended to be an easier to type > alternative that maps directly onto JSON. >
That's good. > The currently defined format was just the simplest things that would cover > the most common use case > agreed. > . The current format has two major limitations (only being able to produce > a simple flat hashmap object, > We could extend it to something like INI files in WinDOS. > and forcing values onto a single line). But it wins in other respects: > there's no encoding of special characters, or balancing of quotation marks. > That's what I like most. > As Mario says, JSON itself is always available for demanding applications. > So you do not want to extend the dictionary format? That's a pitty. Having blanks as first characters is the option I'd prefer here, but as a second alternative I'd use colon as it would fite really nicely into the current parser, without changing the regular expressions at all. I think we need to consider 2 cases: 1. Multiline values 2. Continuation lines Multiline_Value: line 1 : line 2 : line 3 Continuation_Lines: this is \ a value continued \ on 2 lines. Multiline would simply append all values from lines starting with ":" (so having an empty fieldname) seperated with "\n" to the last field. Continuations would merge the following lines, first removing any leading whitespace from the continuation lines so that we can indent if we want. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/groups/opt_out.
