Hi Frank,
On Apr 10, 2012, at 2:30 PM, Frank Fischer wrote:
Hello,
using a non-WYSIWIG editor my text lines can get quite large
(especially when some markup is included).
With 1.0 syntax this was no problem:
line one
still line one
is rendered in one line.
Is it possible to achieve a similar behaviour with 2.0 (2.1)?
Like:
line one ~
still line one
or:
line one \
still line one
(both examples result in two rendered lines)
(from
http://en.wikipedia.org/wiki/%5C: In the context of line-oriented text, especially
source
code for some programming languages, it is often used at the end of a line to indicate
that
the trailing newline character should be ignored, so that the following line is treated
as if it
were part of the current line. In this context it may be called a
"continuation". The GNU make
manual says, "We split each long line into two lines using backslash-newline; this
is like using
one long line, but is easier to read.")
When we created the XWiki Syntax 2.0 we decided that all characters should be meaningful
so if you put a newline it's going to be rendered.
Could you explain the problem you have with it? You say your lines can get quite large.
But whatever editor you're using, it's usually going to wrap them so that they fit
on your screen.
Now if you really want this behavior you could use the {{velocity}} macro which supports
filters (see
http://extensions.xwiki.org/xwiki/bin/view/Extension/Velocity+Macro+Filter).
For example:
{{velocity filter="html"}}
line one
still line one
{{/velocity}}
I agree that we could easily refactor this in a more generic macro independent of
scripting languages. For example something like:
{{filter name="html"}}
line one
still line one
{{/filter}}
Would that answer your need?
We could decide to escape the last char as you suggested too. I'm not sure about this
though but why not. It would need a vote since it's changing the current syntax. Also
it could only be implemented in XWiki Syntax 2.2 since we keep backward compatibility for
all syntaxes.
Let us know what would work for you.
Thanks
-Vincent