24 Jul
2008
24 Jul
'08
11:56 a.m.
On Jul 24, 2008, at 11:46 AM, Thomas Mortagne wrote:
The only downside is that the more changes we add the more difficult
it'll be for users to migrate their content. We can probably write
some migration scripts for moving links [...] to [[....]], same for
bold, etc. Might be harder to tables.
Personally I'm a bit -0 for a wiki syntax but I'm not sure.
Thanks
-Vincent
On Wed, Jul 23, 2008 at 6:05 PM, Vincent Massol
<vincent(a)massol.net>
wrote:
rationale: creole does it like this.
http://www.wikicreole.org/wiki/Creole1.0#section-Creole1.0-NowikiPreformatt…
In your proposition above I can't see if you're writing single quotes,
double quotes or a mixtures, sounds an issue :)
Anyway so it means you think we need a syntax too right?
Some open issues/questions:
1) I think we need a syntax for escaping a block of text. I'd propose
using {{{whatever here}}} (same as creole and confluence). We could
do
Does not seems very natural as text escaping, why not ""some tex"" ?
it with a
macro but I don't know how we could implement it easily...
2) Do we want double curly braces for macros or simple ones:
{{macro/}} or {macro/}. If we use simple ones then it won't be easy
to
enter { and } chars in a text (they would need to be escaped) and
since we've decided to have double chars for items ( **, --, ~~, etc)
we might as well do that for macros.
+1
3) Do we want to support images in links. For
example:
[[image:someimage.png]]? We already support URIs in links, such as
Sounds like a good idea to me. +1 if it's not too much work.
mailto: so maybe it wouldn't be too hard to
support images too I
guess. Or do we want only the Image macro? A related question is do
we
support http images (http://.../someimage.png) inside links and as an
inline element directly in the text?
4) Tables: do we keep the table macro or do we want a wiki syntax for
tables.
+1 for a wiki syntax.