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

I think we can extract 3 concepts from different conversations: 1) do nothing and let things as it is, meaning spaces are meaningful everywhere + nothing to do ;) - it's not possible to indent content in scripts like velocity or cleanly align tables for example 2) make spaces non-meaningful everywhere and have two different spaces in XDOM (space and non breaking space) for "readability" spaces to not desapear + it's easier to align and indent things everywhere - this means XDOM contains useless information for renderer - the user has to understand that when he write multiples space it will render only one - to not break spaces other than non breaking spaces when switching from WYSIWYG to wiki, we have to find a way to store the information in rendered XHTML 3) let spaces meaningful by default (in pure wiki content) and modify behavior by macros (like make spaces/new lines non meaningful for HTML macro etc...) + it's more logical for user that HTML macro content apply HTML behavior on spaces/newline and in the other hand in the simple wiki syntax it's easier to understand for user that 2 spaces will render 2 spaces - it's not possible to cleanly align table Notes that spaces before list (<space><space>* item list) or headers and generally before standalone blocks, etc. are not part of the debate since this was already voted as part of the syntax. WDYT ? -1 for 1) I think we have to do something at least about indentation in scripts -0 for 2) I really don't like the idea of having two different spaces in XDOM one of them being useless for renderer, for me it's look too much like a hack. Also I really think having non meaningful spaces does not makes much sense for users, I remember it was a difficult concept for me the first time I started to do HTML so I imagine how a user that knows nothing about HTML and don't want to can think about that. +1 for 3) since the table align issue is not critical (it's the only "issue" I can think of for pure wiki content) and it makes lots of sense that HTML macros, Velocity macro and wiki content for example are very different contents and should have their own behavior on spaces and new lines. Also note that it's still possible align tables with spaces but this could not render exactly the same thing that non meaningful spaces (sometime the columns will be larger), it's a hack but it makes the table align issue a very small issue compared 2)