Re: [xwiki-devs] [VOTE] Make spaces non meaningfull in XWiki 2.0 syntax (was [Rendering] Should we move to non meaningful spaces?)

Thomas Mortagne wrote: I'd go for a consistent approach, same behaviour in all situations so that it's not hard to know what to expect. I had some trouble defining "block elements" for myself so that I can answer this email so I assume it would be difficult for users too. Therefore either 1) and 2) together or none. Now since wiki syntax is not supposed to be "what you see is what you get" but more of a markup language, I think non-meaningful spaces would be a acceptable (the HTML way) as long as there is a method to force a non-breaking space (HTML's  ). So +1 for 1) 2) and 3)

> +0,5 for 1) it's not critical for me but i'm not against it and we > already decided to remove space before list item, headers etc. > -0 for 2) I don't see the need for that and it's a lot easier for the > parser to make spaces meaningfull (what to do when you have "test ** > bold**" and things like that) > +1 for 3) > > On Sat, Feb 28, 2009 at 15:44, Vincent Massol <vincent(a)massol.net> wrote: >> Hi, >> >> This is our last chance to change this behavior. We've found several >> places where having meaningful spaces are counter-productive: >> >> * in table cells since we can't align table anymore. For example: >> >> |= column1 |= column2 >> | this is some para | second column >> | hello | world >> >> (not sure this will be rendered nicely in mail but you see what I mean) >> >> * in scripts since having meaningful spaces prevents us from aligning >> velocity or groovy scripts. For ex we can't write: >> >> #if (....) >> #if (...) >> do something >> # end >> #end >> >> To see a better example have a look at http://tinyurl.com/ahz669 >> >> What I think users real want are meaningful new lines but I see cons >> overweighting pros for having meaningful white spaces. Thus I'm think >> we should strip whitespaces at beginning and end of lines including >> for line breaks. >> I'm slightly less sure for multiple spaces between words but even >> there I think we could strip them have users use {{{ }}} to put a non >> breaking space for ex (or introduce a {{space/}} macro or another >> special syntax although I'd rather we don't introduce a new syntax). >> >> WDYT?