Edgewall Software

Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#9639 closed defect (duplicate)

Escaping the escape character

Reported by: shesek Owned by:
Priority: normal Milestone:
Component: wiki system Version:
Severity: normal Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:


It seems like its currently not possible to write 'foo bar!' in bold, as **foo bar!** will cause the closing ** to be escaped by the !.

**foo bar!!** doesn't seem to work either - the second ! isn't escaped by the first one to be considered a plain !, but rather renders as: foo bar!**

Is there any other undocumented way to do that that I'm not aware of? If so, it should probably be mentioned in the WikiFormatting documentation. If no such way exists, maybe a double !! should be considered as a plain ! character, in the same way \\ works when the \ character is used for escaping?

Attachments (0)

Change History (2)

comment:1 by Christian Boos, 11 years ago

Resolution: duplicate
Status: newclosed

Well, writing **...!!** is not significantly less intrusive than writing **...! **, which already works. Ideally this should be taken care of by the parser…

This is already on the list btw., in #3970. Please follow-up there if needed.

comment:2 by shesek, 11 years ago

Well, it does cause an extra space. I noticed it in the description for #9638, right after the 'best invention since sliced bread!'… the extra space is what I eventually used, but it does look quite odd.

I noticed you added my suggestion to #3970… doubling the character is the approach taken in most places (PHP, SQL [either double \\ in some DBMS or double '' in others] and most places dealing with escape character), so I think its reasonable to use it.

Modify Ticket

Change Properties
Set your email in Preferences
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from (none) 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.