Edgewall Software
Modify

Opened 15 years ago

Closed 15 years ago

Last modified 7 years ago

#645 closed enhancement (worksforme)

More headings in the wiki syntax

Reported by: anonymous Owned by: Jonas Borgström
Priority: normal Milestone:
Component: wiki system Version: 0.7.1
Severity: normal Keywords: wiki headings
Cc: Branch:
Release Notes:
API Changes:

Description

There is now only 2 levels of headings in the wiki.

I would propose too add it to 3 or 4.

So

!=== Heading3 ===

!==== Heading4 ====

How do you escape the above and get rid of the '!' ????

Attachments (0)

Change History (6)

comment:1 by daniel, 15 years ago

Resolution: worksforme
Status: newclosed

The Trac wiki formatter will properly process H1-H6 headers.

Example:

= Header 1 =
== Header 2 ==
=== Header 3 ===
==== Header 4 ====
===== Header 5 =====
====== Header 6 ======
======= Header 7 =======

Display:

Header 1

Header 2

Header 3

Header 4

Header 5
Header 6

======= Header 7 =======

comment:2 by anonymous, 15 years ago

Sorry. I checked and it works for me aswell. I think that settings were just set so that I didnt see that the fonts were different.

Thanks.

in reply to:  1 comment:3 by sid, 12 years ago

Replying to daniel:

The Trac wiki formatter will properly process H1-H6 headers.

Actually, it only supports H1-H5. Anything beyond that is ignored. See WikiFormatting.

comment:4 by marc@…, 7 years ago

What about

info

or

(can anybody see the search keyword? in the header above??)

How to avoid special processing here?

source
== info == 
or
== search ==  
(can anybody see the **search** keyword? in the header above??)

in reply to:  4 ; comment:5 by Christian Boos, 7 years ago

Replying to marc@…:

What about [… anything some-id title that matches #<some-id> CSS rules …]

That's indeed a very unfortunate side-effect of the automatic creation of anchors out of section titles…

How to avoid special processing here?

An easy workaround is to change the id by specifying it explicitly, like in:

Wiki Markup Display
== search == #search-topic

search

The real fix however would be to avoid having CSS rules relying on such common names. If we can get all the ids used in CSS rules to start with the trac- prefix, it would be easy to ensure that no generated anchor would ever clash.

See #8645 for further updates on this topic.

in reply to:  5 comment:6 by anonymous, 7 years ago

Replying to cboos:

Replying to marc@…:

What about [… anything some-id title that matches #<some-id> CSS rules …]

That's indeed a very unfortunate side-effect of the automatic creation of anchors out of section titles…

How to avoid special processing here?

An easy workaround is to change the id by specifying it explicitly, like in:

Wiki Markup Display
== search == #search-topic

search

The real fix however would be to avoid having CSS rules relying on such common names. If we can get all the ids used in CSS rules to start with the trac- prefix, it would be easy to ensure that no generated anchor would ever clash.

See #8645 for further updates on this topic.

WorksForMe! thx!

Gr. Marc

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Jonas Borgström.
The resolution will be deleted. Next status will be 'reopened'.
to as closed The owner will be changed from Jonas Borgström to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.