#4 Allow spaces in WikiWords

(This was transcribed from
FlexWiki.WikiFeatureRequestAllowSpacesInWikiNames. It
was originally submitted by Anon)

Allowing spaces in Wiki names. The thought here is that
a valid name could be [Do Not Forward Email Scenario]
as opposed to DoNotForwardEmailScenario. I'm not
trying to suggest that this changes the thought or
naming process around how you create Wiki names, just
that it might be less geeky if spaces were allowed.

COMMENTS

WikiNames are a core element of WikiWikiWeb. To allow
spaces in them may make them initially seem less geeky,
but would introduce inconsistencies within and between
wikis. These inconsistencies would make wiki harder to
learn and use as a result. This would make things more
geeky, not less.

Either this proposal is trying to "change [...] the naming
process around [... creating] Wiki names," or I don't
understand it. But I can't tell which.

Five quick points. First, since when is "less geeky"
considered a good thing? :) Second, like adding square
brackets as markup around things isn't geeky? Third,
this would seem to preclude me from using square
brackets in normal circumstances. Fourth, part of
WikiMeansQuick means to me that links should pretty
much "just happen" as opposed to marking up a
document with special tags: the ability to effortlessly
create and follow links is a fair part of the value inherent
in wikis. Fifth, where's the geek? There are wikis in the
world with non-geek topics, and they all use the same
basic syntax for links - time to get your Geek-O-Meter
recalibrated. :) -- StuartCelarier, 17 August 2004

A lot of wikis have started allowing white spaces in the
wikinames using the [ and ] brackets because it allows
you to easily define terms and topics that have real life
value for example Delation Ratio versus DeflationRatio ...
Wiki should be quick and efficent if using [ and ] extends
the functionality of wiki and is already a standard used
by many wiki apps why fight it? -- Anon.

Can we have some examples of "a lot of wikis" that allow
spaces in WikiTopics? Maybe there is another wiki
engine out there I'd rather use.

I don't understand the comment about "defining terms
and topics that have real life value." What am I
supposed to see in this example? I'd also like to hear
how use square brackets as literal characters in text
would be supported (the third point above).

Don't get me wrong, I am not "fighting" the concept, but
I do think we need to reasonably question new features
anytime it is not clear what the problem is, how the
feature actually solves the problem, and what additional
problems are created by the solution. And a question is
just that, a request for more information. --
StuartCelarier, 24 August 2004

One problem with CamelCase is that things you don't
want to be wiki words turn into wiki words. For example,
if your last name is McQueen, assuming you don't want
a page called McQueen, you always have to surround it
with double quotes to avoid this, and you might forget
to do this until after you edit and save, which means
another edit and save cycle. The other reason to
disable CamelCase is that it is hard to read. It is
certainly easier to read a link where the words are
separated by spaces. I used a wiki with CamelCase for a
long time, but have recently stared using WikidPad as a
personal wiki, and there I've disabled CamelCase entirely
and so far I'm finding that to be an improvement over
the way I did things before. -- LeilaPearson, 25 August
2004

Leila, I think you meant PascalCase, not CamelCase.
PascalCase words have an initial upper-case letter;
camelCase words have an initial lower-case letter. I
know that both CamelCase and PascalCase are hard to
read, that is why virtual every modern API uses them for
identifiers like the names of functions, classes, etc. And
that's why so many hip company and product names use
them: eBay, iPod, PayPal, GoDaddy, McDonalds (oops,
scratch that one.) They are SlightlyHardToRead, but a
whole_lot_better_than_some_of_the_alternatives.

I agree that FauxTopicNames (like McQueen) present
problems, and I'm interested in ways to address those
problems. But I am not sure that means that (1) the
problems outweigh the benefits, or (2) that introducing
a different syntax doesn't just trade one set of problems
for a different set, perhaps a worse set.

I think something absent from this discussion is that
WikiWikiWebs form LanguagesOfPatterns in the tradition
of ChristopherAlexander, the DesignPatterns book, etc.
Maybe I take this for granted, since the first
WikiWikiWeb, the PortlandPatternRepository, was
concieved of and created to discuss patterns and their
language. WikiTopics make us give names to concepts,
and use those concepts as the principle navigational
paths through the content. If any arbitrary text can
become a link in a wiki, then it is hard to understand the
structure formed by the links . (Pop quiz: where will the
previous link take you? What will you find there?)

I think the strongest case against using PascalCase is
that it is closely tied to Roman-based languages,
especially English. Capitalization carries meaning in some
languages (e.g., German Sie and sie,) and simply doesn't
apply in others (e.g., Japanese or Thai.)

you can also bet that a wiki on the writings of e e
cummings or archy the cockroach would be exercises in
utter futility period end of sentence -- StuartCelarier,
25 August 2004

What about using the PascalCase when you edit the
document but have the word broke apart (like the title's
are) when the page is viewed? This would keep it easy
to edit while making it easier to read through. --
NickLargent [2004.9.28]