(anonymous guest) (logged out)

Copyright (C) by the contributors. Some rights reserved, license BY-SA.

Sponsored by the Wiki Symposium and the Nuveon GmbH.

 
View Attach Info

Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-44) was last changed on 15-Dec-2007 14:57 by YaroslavStavnichiy  

This page was created on 12-Jan-2007 16:31 by RadomirDopieralski

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 7 changed one line
First, I need to handle inline comment enclosed in curly braces (this is a common notation in set theory, like {A, B}). So if I have four open curlies followed by four closes, how do I handle that? One provisional solution I'm considering is associating the extra close curlies with the ''inside'' of the span, so the regex for the closing markup is three closing curlies not followed by a fourth: {{\}\}\}(?!\})}} in Python syntax, for the coders out there. This would also provide an escape for three or more closing curlies inside a span: just follow those with three closing curlies followed by three opening ones, to open a new span.
First, I need to handle inline comment enclosed in curly braces (this is a common notation in set theory, like {A, B}). So if I have four open curlies followed by four closes, how do I handle that? One provisional solution I'm considering is associating the extra close curlies with the ''inside'' of the span, so the regex for the closing markup is three closing curlies not followed by a fourth: {{{\}\}\}(?!\})}}} in Python syntax, for the coders out there. This would also provide an escape for three or more closing curlies inside a span: just follow those with three closing curlies followed by three opening ones, to open a new span.
At line 377 added 31 lines
Sorry for the apparently trivial reply: the average user won't type a character that he does not see on the keyboard ([AvoidSpecialCharacters]), I really feel that a slice of users is cut apart with the tilde - but if it's not the biggest slice, it could be anyway a good compromise.
About raw transclusion: it is (in my opinion) the only "clean" solution because it would separate the raw block of text from the wiki markup text, any other solution would require to modify the raw block of text. Just my 2cents; by the way, thanks for the additional informations.
-- [[DanieleC.]], 2007-Jul-06
=== User-defined block terminator ===
Here is one more idea for nowiki-block termination syntax - let user define the terminator:
{{{
{{{TERM1
nowiki-text
TERM1~}}}
{{{MY-DELIMITER-2
another nowiki-text, which can contain even TERM1~}}}
MY-DELIMITER-2~}}}
}}}
It can be used by advanced wiki users, who can include everything they like into nowiki-blocks in this way. Basic Creole 1.0 syntax is compatible with this concept (user-defined terminator defaults to empty string).
Same idea is used in Perl for example:
{{{
print <<EOT;
blabla
EOT
}}}
-- [[YaroslavStavnichiy]], 2007-12-15
Version Date Modified Size Author Changes ... Change note
44 15-Dec-2007 14:57 29.148 kB YaroslavStavnichiy to previous
43 15-Dec-2007 12:13 29.147 kB YaroslavStavnichiy to previous | to last
42 26-Sep-2007 09:31 28.525 kB ChuckSmith to previous | to last restore
41 26-Sep-2007 01:09 28.549 kB 194.9.85.141 to previous | to last
« This page (revision-44) was last changed on 15-Dez-2007 14:57 by YaroslavStavnichiy