CamelCase is a way of writing, WithEveryWordInCapitalLetter and MashedTogether. It's commonly used in many programming languages, and in Wikis, it defines a WikiWord..
JSPWiki supports CamelCase linking from 1.9.2 onwards.
Here is the relevant discussion from Ideas, with a couple of additional thoughts.
AlainRavet: CamelCase is very useful, but we need a way to escape it, like Twiki's <nop>.
Example: JasperReport is only a product name, not a page link.
Automatic CamelCase linking is not good when it comes to software documentation or filenames. See TableTemplate.
<nop> = No operation Why do I feel you already knew it? I didn't even have to tell you. See?
I know it because I use TWiki extensively at some other places :-). TWiki uses <nop> to stop the parsing. And no, I don't think it's a good thing.
Adding new special characters is not necessarily a bad though. Those that need them are typically Java programmers who can deal with such issues anyway. In that sense, using "!" for negation might not be a bad idea. However, using the same special character for two different purposes is a bit of a problem, though.
Since 1.9.27 it's possible to escape CamelCase links by using a (aka tilde, worm) directly in front of the word (like this: CamelCase). The change is now live on this server - let's see how this works out.
and the corresponding page has been created, JSPWiki should automatically turn that text into a link wherever it is found, even when it isn't included inside the markers.
JanneJalkanen: Actually, most wikis just make all words ThatHaveBeenWrittenInCamelCase to links, and you're supposed to just write your text using CamelCase whenever you think might be necessary. This allows you to do automatical linking with ease. We require s everywhere, but I'm slowly starting to think that perhaps allowing CamelCase is quite okay. For now, just write everything you think might be useful as a link later on inside square brackets. It doesn't matter if the link does not exist - someone will create them at some point. If you're bored, you can always go to UndefinedPages and make some =).
JanneJalkanen: Actually, I had a sort-of-working version of using plain CamelCase running already. Then I accidentally deleted the entire source tree (before I was able to put it into CVS). I got so miffed by it that I haven't bothered to hack it back up again. (I am using the word "hack" because the current TranslatorReader structure cannot really do the CamelCase link detection cleanly.) Anyway, it's on the TODOList.
OliBye thanks guys. I can upgrade http://xpdeveloper.org now (after testing ofcourse). OliBye would like to help testing but I can't find a version 1.9.2x to download. Could I get it from anonymous CVS?
AnonymousCoward: Instead of automatically going and shoving a bunch of links into pages when someone starts linking a phrase, maybe it would be better to have a pluginpage that would show you which pages could have that wiki-able phrase turned into links. Something along the lines of UnusedPages. You could view pages that contained the matching link and decide if it is a good candidate to have the link inserted.
An example to consider of when you wouldn't want an autolink inserted for a particular term is disambiguation pages. If you have the wrong thing linked, with a right word, from a bunch of pages it could prove to be a frustrating experience for readers. When using context sensitive words, it would be better for that word to link to the relevant context definition for the word, instead of the disambiguation page, however, a retro-active autolinker may (at first blush/implementation) merrily link to the disambiguation page.
P.S. Taking the idea further, having a page that displays unique/rare word statistics could also be useful for determining what may need wiki links. For example, if you could detect unique or rare words/phrases you may be able to find texts that should be expanded on in a wiki.
CirrusShakeri: Suggestions: Use <notwiki> to prefix non-wiki but wiki-looking words. Use <linkit> to explicitly link to a wiki topic: Default linking to a topic is not a good idea, in my opinion.
Is CamelCase working in 1.9.37-cvs ? I have: jspwiki.translatorReader.camelCaseLinks = true in my jspwiki.properties but cannot get CamelCase to function.
You can see at: http://cowgar.com/Wiki.jsp?page=SystemInfo that it's enabled, then visit: http://cowgar.com/Wiki.jsp?page=SandBox to see that it's not quite functioning. At the bottom I say WikiWiki ... That's a valid CamelCase right? The page even exists: http://cowgar.com/Wiki.jsp?page=WikiWiki ... Any input would be greatly appriciated.
Oh, by the way, I think CamelCase is an essential Wiki feature. Their could be 1,000 people updating one site, how does each person know what is already defined and what should be 'd or not? This way if someone enter's OceanWave and it's defined, it'll show up. However, without CamelCase, if they enter OceanWave and it is defined, a link will not exist to it because this user did not know that it was one of the 300,000 Wiki pages that exist so they did not  it.
No, it was not working in 1.9.37. This was documented in the ChangeLog, which really is the best place to look for change information of the CVS version.
However, thanks to JeffPhillips, we got it up and running in 1.9.39 :-).
You mean 1.9.41 worked? That is odd - there was no change to the CamelCase routine in 1.9.41... Which was the latest version you tried?