Test case from TextFormattingRules:

"Create the topic by clicking on the ?. (Try clicking, but then, Cancel - creating the topic would wreck this example!)"

Only the question mark and Cancel should be bold.

-- PTh

And yet another one from TextFormattingRules:

"TWiki Variables are names that are enclosed in percent signs % that are expanded on the fly."

I would like to redefine the release criteria in order to foster changes of high quality during code freeze: All "Urgent" and "Required" bugs resolved, and no new "Urgent" and "Required" bugs for 7 days. This is one topic for the next release meeting.

-- PTh

Peter, it would have been enormously helpful if you could have provided a spec of how emphasis is supposed to work. Trying to deal with these reports on a case-by-case basis is exhausting for both of us. I know you want identical behaviour to Cairo, but we have no spec of Cairo behaviour to compare against. Note that the Cairo REs do not adequately specify Cairo behaviour, because of previous manipulations of the string before the REs are applied (and subsequent manipulations after). Emphasis inside a || table is a good example of this.

I have put together a testcase (TestCaseAutoEmphasis) that I think captures what you intended for Cairo, though Cairo actually fails in a few places. There will still be cases I have missed; if you can add them to that testcase as part of future reports it would be most helpful. This is the only way we can be sure that prior fixes are not broken by subsequent changes.

SVN 8205

On release criteria; you are of course free to propose whatever criteria for a release you want.

CC