(anonymous guest) (logged out)

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

Sponsored by the Wiki Symposium and the Nuveon GmbH.

 

Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-46) was last changed on 05-Oct-2008 17:38 by 69.243.201.36  

This page was created on 04-Sep-2006 01:57 by 217.162.145.188

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 183 added 15 lines
Thank you for your clarification, I think I understand it better now. Personally I'm still somewhat charmed by the (mentioned many times before here) approach suggested recently by EricChartre -- defininng only the absolute minimum we really need for interoperability and disambiguing things, and leave as much detail as possible to the implementers.
On the other hand, I agree that the details you mentioned can be problematic and thus should be defined. We can take the following approach:
__For URLs in text__ (without any markup), use somewhat generous matching algorithm, for example a regexp like {{{\w+//:\S[^,.:;?!|'")\]\}\s]}}}. Obviously, this is not **correct** implementation -- it won't match legitimate urls ending with a comma or dot and such, and it will match more url-like things that are really defined. But it follows the usus. People often put commas or periods or other punctuation right after the ulrs in the text. At the same time, sane URLs rarely even use these characters (except the dot), not to mention ending with them -- you can always use the {{{[[...]]}}} markup to force them.
__For the URLs in links__ (with the {{{[[...]]}}} markup), I'd say that anything that matches '^\w+://' is an URL (external link), while anything else is a page name (some wikis can also check the validity of the page names and refuse to parse malformed links, of course).
__The text and target order__ problem is in my opinion impossible to solve without introducing a totally new markup for links (so that it doesn't collide with existing ones). As you noticed, your approach can change the links of an existing document -- it may be an old and established wiki page, and the change can make it say something totally different than before, and the change won't even appear in the recent changes. That pretty much breaks peer review -- one of the most fundamental mechanisms in wikis.
The used order has an additional advantage -- since the "{{{|}}}" character is forbidden both in URLs, and in most wiki page names, you don't need any kind of escaping, and you can freely use additional pipe characters in the link text. It would be impossible the other way around.
What do you think, is it enough?
-- RadomirDopieralski, 2006-01-02
Version Date Modified Size Author Changes ... Change note
46 05-Oct-2008 17:38 4.08 kB 69.243.201.36 to previous
45 25-Mar-2008 08:16 3.983 kB ChristophSauer to previous | to last respond to Carl
44 25-Mar-2008 05:04 3.85 kB CarlCravens to previous | to last
43 16-Oct-2007 10:01 3.022 kB ChristophSauer to previous | to last moved from talk
42 26-Sep-2007 09:06 2.114 kB ChuckSmith to previous | to last restore
41 26-Sep-2007 00:57 2.124 kB 219.138.204.162 to previous | to last
« This page (revision-46) was last changed on 05-Okt-2008 17:38 by 69.243.201.36