{SNARF(url=>http://community.livejournal.com/lojban/}http://www.livejournal.com/users/rlpowell/2418.html{SNARF}
Normally the " should be considered only if followin directly = or =>
but the color is ok
so, not even sure this solution is quite correct .... I would regexp
personnaly.
{BOX(title=>Summary "Test"!)} gives Summa ??{BOX}
{BOX(title=>Summary "Test")} gives the same ??{BOX}
Normally the " should be considered only if followin directly = or =>
{BOX(title="Hallo, Bertrand!")}Mein Text{BOX} misses totally the title !!!
as {BOX(title=>"Hallo, Bertrand!", bg=>red, width=>50% )}Mein Text{BOX}
but the color is ok
so, not even sure this solution is quite correct .... I would regexp
personnaly.
{BOX(title=>"Hallo, Bertrand!")}Mein Text{BOX} is right
but {BOX(title=>Hallo, Bertrand!)}Mein Text{BOX} as expected cuts to Hallo
{BOX(title=>Hallo Bertrand!)}Mein Text{BOX} is right
{BOX(title=Hallo Bertrand!)}Mein Text{BOX} also
Test du'e.
-Robin
No such attachment on this page
The new colossal caves text, with new rafsi and errors corrected
CC Text
new_cc.txt
No such attachment on this page
''No such attachment on this page'' The new colossal caves text, with new rafsi and errors corrected CC Text new_cc.txt ''No such attachment on this page'' new_cc.txt
Test.
-Robin
Different testing entirely:
The above created with:
Still other testing:
Codename Sirius
The 1.9 version is the one after 1.8. As we begin to separate stable from devel versions, that 1.9 is intended to become a development branch.
Here is a tarball with latest CVS code updated every 6 hours: http://tikiwiki.org/tikiball.tar.bz2
CVS branching has occured here. Note the new cvs checkout requirements!
export CVS_RSH=ssh export CVSROOT=:ext:sfname@cvs.sf.net:/cvsroot/tikiwiki cvs -z5 co -d tiki19 -r BRANCH-1-9 tikiwiki
If you commit on your current checkout you will commit to Tiki 1.10!
Update through cvs withcvs -z5 up -dP -r BRANCH-1-9
half way fixed:
released on monday 28th june
released on monday 21st june
please contact these people before a RC is made so they can commit any last minute modifications/updates
Different testing:
Code can be used to display lines of preformatted code in wiki pages.
<?php function foo($foo) { print($foo); }?>
some code line numbered
Only php color is available for now. more are expected.
<?php function foo($foo) { print($foo); }?>
some text
(1.7.1.1) If you see confusing output like "&quot;" or so (actually double-processed html special characters), try to check "Allow HTML" option.
You can edit the plugin if you need to change the look and feel of the output. There is only one file to deal with.
{CVS()}lib/wiki-plugins/wikiplugin_code.php{CVS}
- - - Done with different testing.
More testing.
§3016d2c14a027bf0efc4f37f7c96dd81§
§a4e934d5305ae0c67970004c732671e3§ <pRe>§2efb0224f0b5a6aa16578dcc1b0fef4b§
{CODE()}moo~/np{CODE}
~np~{CODE()}help{CODE}
~ np~foo
~/pp~
-Robin
- - - Done with wierd testing.
mi ji'a cipra
CAD software history just went online and welcomes any corrections and additions.
Maybe a Wiki will help offset the workload of correcting/extending the history.
Wow! This is incredible and I love this interface. I am going to get my hands on a copy of Tiki and give it a spin!
All my computer environment speaks UTF-8, except my terminal, but including my web browser and its form editor.
This should render properly if UTF-8 support in Tiki works OK :
« (<<) » (>>) œ (oelig) ß (beta) æ (aelig) — (ndash) ≈ (about equal) … (three dots)
- Preview OK
Some words in Cyrillic: Шла Маша по шоÑÑе и ÑоÑала Ñушку
Some lines in Hebrew (pointed!)
ש×ִמְרוּ ש×ַבּתוֹתַי לְמַעַן ×ªÖ¼Ö´×™× Ö°×§×•Ö¼ וּשְׂבַעְתֶ×
מִזִּיו בִּרְכוֹתַי ×Ö¶×œÖ¾×”Ö·×žÖ¼Ö°× ×•Ö¼×—Ö¸Ö·×” ×›Ö¼Ö´×™ בָ×תֶ×
וּלְווּ עָלַי ×‘Ö¼Ö¸× Ö·×™ ×•Ö°×¢Ö´×“Ö°× ×•Ö¼ ×žÖ·×¢Ö²×“Ö¸× Ö·×™ ש×ַבָּת ×”Ö·×™Ö¼×•Ö¹× ×œÖ·×”×³
Points don't look right, but I think it's a font thing. Looked okay in editing anonymously, but not when logged in.
testing