Topic: Gathering thread of what is disturbing on the website

What about dashes? "camel-case"

In all projects I was working on, that was the way of producing urls.

einstein13
calculations & maps packages: http://wuatek.no-ip.org/~rak/widelands/
backup website files: http://kartezjusz.ddns.net/upload/widelands/

Top

Quote

So what do you propose?

einstein13
calculations & maps packages: http://wuatek.no-ip.org/~rak/widelands/
backup website files: http://kartezjusz.ddns.net/upload/widelands/

Top

Quote

Ok, I don't understand all. But as I understand- you have a good idea for the problem and know how to fix it . Sorry for interrupting.

einstein13
calculations & maps packages: http://wuatek.no-ip.org/~rak/widelands/
backup website files: http://kartezjusz.ddns.net/upload/widelands/

Top

Quote

einstein13: It seems there was an idea to use CamelCase for each wiki Articles name to make linking of articles easier when writing another article. So if one wrote "Look at the wiki page LinksPage to get more information" the term LinksPage was automatically turned into a link like "LinksPage". To prevent a term from being turned into a link a special syntax was created: CamelCase with a call sign as first character would not be turned into a link. But there are some reasons where the whole idea not fit:

1. It is just bad style to have terms like "LinksPage", "GameHelpBarbarian", "EditorHelp" and so on
2. It prevent an easy naming scheme like "Links", "Barbarians", "Editor"
3. When creating pages on the fly from external resources like the Changelog or Documentation, it is not possible to have influence on CamelCase by preceding a call sign to each CamelCase word. Yes of course it could be coded, and this is coded. but it blow up the code without a real good reason.

4. The "CamelCase-to-link" function does not work for headers. F.e. the example from GunChleoc in the LinksPage the header in code looks like this:

   ''### Links to !SourceForge ''

   What happens now is:
   a. markdown do his work and creates a toc where each entry is a link. The Entry in the toc look exactly like the header is spelled, so it contains the call sign
   b. After this the "CamelCase-to-link" function went over the text and headers, found a callsign-CamelCase word, remove the call sign and leaves the CamelCase word

   Thats why the call sign is shown in the toc but not in the header.

Removing this selfmade function and using a well tested python markdown extension is better than coding one exception after another... The only disadvantage is: Authors of wiki articles have to learn to make double brackets around a word that should link to another wikipage in the same wiki.

Top

Quote

OK, it's a change to use [[]] rather than CamelCase, but it's not rocket science. Also, if authors are used to WikiMedia (the software that Wikipedia uses), they will already be familiar with [[]].

Busy indexing nil values

Top

Quote