#476: Option to disable CamelCase for non-direct-Wiki pages.
----------------------------------+-----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: cboos
Type: enhancement | Status: closed
Priority: normal | Milestone: 0.9
Component: wiki | Version: devel
Severity: normal | Resolution: fixed
Keywords: CamelCase |
----------------------------------+-----------------------------------------
Changes (by cboos):
* keywords: camelcase => CamelCase
* milestone: => 0.9
* resolution: => fixed
* status: assigned => closed
Comment:
I agree, this ticket was about the possibility to disable CamelCase
links because when rendering text which contains lots of CamelCase
names which are '''not''' meant to be names of Wiki pages, displaying
them as ''missing links'' makes the whole text hard to read.
This was addressed in [milestone:0.9], with the option
{{{
[wiki]
ignore_missing_pages = true
}}}
which solves __that__ specific problem (the option defaults to `false`,
though).
Now, for the problem of wiki formatting in changesets,
there's been the addition in [milestone:0.10] of yet
another option:
{{{
[changeset]
wiki_format_messages = false
}}}
(defaults to `true`, of course). See #2526.
In parallel, there will be some additional changes for
[milestone:0.10] that will make the wiki formatting of
Changelog-like texts much better by default (see #124).
To conclude with this, I'll reiterate the suggestion of tim
that a new ticket should be created if one wants an even greater
control over what will get wiki formatted or not. But before
doing that, I'd suggest the author of such a ticket waits for
the development of [milestone:0.11] to start, and in particular,
for the WorkFlow branch to be integrated. In fact, the WorkFlow
branch has already a mechanism in place for deciding whether
ticket fields should be `.plaintext` or not.
Currently, it's only about custom fields, but we already
discussed about extending that mechanism to cover the
default fields. It should be possible to generalize the approach
even further. Will see by then.
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/476>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
