Ticket #191 (accepted enhancement)

Opened 3 years ago

Last modified 4 months ago

Making CamelCase optional

Reported by: NilsLindenberg Owned by: DarTar
Priority: normal Milestone: 1.2.1
Component: formatters Version: 1.1.6.1
Severity: normal Keywords: CamelCase
Cc:

Description (last modified by NilsLindenberg) (diff)

There are people who do not like Camelcase or environments where it is unpractical. So CamelCase at whole should be optional (with perhaps a message in the edit-window if it is enabled or not).

Perhaps with the option to turn it on/off for a page and/or a list of words which should not be CamelCase formatted.


discussion from the SuggestionBox:

Popular Scottish surnames such as McKenna are wrongly being interpreted as WikiNames - is there any way to prevent that happening? -- host86-133-223-194.range86-133.btcentralplus.com (2005-07-09 13:23:06)

How about something like a lookup table where WikiAdmins enter a list of words that will be ignored for formatting on all pages? -- JsnX

Sounds like a nice addition. Two suggestions: 1) CamelCase parsing should be made optional in the config file. 2) the list of words to be skipped could be implemented as a wiki page (something similar has been proposed for menus, acronyms and group management): this would make it a lot easier to maintain the list. My 2 cents -- DarTar

Displaying words with capital letters in the "middle" as WikiNames is a real problem. I don't want to turn off the automatic parsing because these words ARE WikiNames in most cases. It seems to me that a lookup table (e.g. a list of words as a wiki page) costs a lot of time to maintain. My suggestion is simple: "McKenna" should be interpreted as a wiki name. "Mc _ Kenna" (with underscore) should NOT be interpreted as a wiki name but written without underscore. "Mc _ _ Kenna" (with multiple underscores) should be converted to "Mc _ Kenna" (ignore the spaces, please). -- MichaelSchams

Ok this is probably stupid to point out but if you put double double quotes around words they aren't parsed by the wiki so if you want McKenna to not become a link you can say ""McKenna"" and voila... -- DanielMcNair (who has this problem regularly...) (-:

See also

#864 Less restrictions for (possible) user names #61 Case insensitive CamelCase (Link creation, page loading)

Change History

Changed 3 years ago by DarTar

  • owner changed from unassigned to DarTar
  • status changed from new to assigned
  • summary changed from Making Camelcase optional to Making CamelCase optional
  • component changed from core to formatters
  • milestone set to 1.1.6.3

Changed 3 years ago by DarTar

  • milestone changed from 1.1.7 to 1.1.7.1

I've tested the effects of enabling/disabling CamelCase, but this require more work that I imagined to preserve all the functionality when CamelCase parsing is toggled off.

Changed 2 years ago by BrianKoontz

  • description modified (diff)

Changed 2 years ago by JavaWoman

  • keywords CamelCase added

Changed 4 months ago by NilsLindenberg

  • description modified (diff)
Note: See TracTickets for help on using tickets.