Issues.00060 History
Hide minor edits - Show changes to output
Changed lines 19-21 from:
:Status:Active
:Resolution:Fixed, installed and tested on the Affinity server. Awaiting word from Onesquared that we can install the revised compiled code on the wikipublisher server. :+
to:
:Status:Closed
:Resolution:Fixed, installed and tested on the Affinity server. Awaiting word from Onesquared that we can install the revised compiled code on the wikipublisher server. In fact, they had installed it, but not bothered to inform us. :+
Changed line 24 from:
to:
Changed lines 19-20 from:
to:
Changed lines 21-22 from:
:Resolution:Fixed, installed and tested on the Affinity server. Awaiting word from Onesquared that we can install the revised compiled code on the wikipublisher server.
to:
:Resolution:Fixed, installed and tested on the Affinity server. Awaiting word from Onesquared that we can install the revised compiled code on the wikipublisher server. :+
In future, if the need arises, it will still be possible to support alternate bullet and numbering conventions, for which Latex uses the square bracket notation. The transformation marks all document text before tansforming document tags to their Latex equivalents. Only square brackets within marked text are converted to their character code equivalents.
Changed lines 1-2 from:
:Summary:misinterprets [Bracketed text] at start of list items
to:
:Summary:Misinterprets [Bracketed text] at start of list items
Changed lines 9-12 from:
:Description:If a list item starts with text in square brackets (ie not markup) the bracketed text is interpreted as over-riding the default list symbol. For example:
* [some text] then regular text
to:
:Description:If a list item starts with text in square brackets (ie not markup) the bracketed text is interpreted as over-riding the default list symbol. For example the list item:
* [text in square brackets] then regular text
Changed lines 21-22 from:
:Resolution:Fixed, installed and tested on the Affinity server. Awaiting word from Onesquared that we can install the revised complied code on the wikipublisher server.
to:
:Resolution:Fixed, installed and tested on the Affinity server. Awaiting word from Onesquared that we can install the revised compiled code on the wikipublisher server.
Changed lines 21-22 from:
to:
:Resolution:Fixed, installed and tested on the Affinity server. Awaiting word from Onesquared that we can install the revised complied code on the wikipublisher server.
Changed lines 1-2 from:
:Summary:misinterprets [Bracketed text] at the start of a list item
to:
:Summary:misinterprets [Bracketed text] at start of list items
Changed lines 15-16 from:
:Proposed solution:Options include escaping all square brackets, inserting an invisible character, or perhaps wrapping the brackets in "verbatim" tags.
to:
:Proposed solution:Options include escaping all square brackets, inserting an invisible character, or perhaps wrapping square brackets in "verbatim" tags.
Changed lines 1-2 from:
:Summary:[Bracketed text] at the start of a list item is misinterpreted
to:
:Summary:misinterprets [Bracketed text] at the start of a list item
Changed lines 15-16 from:
:Proposed solution:Options include escaping the square brackets, inserting an invisible character, or perhaps wrapping the brackets in "verbatim" tags.
to:
:Proposed solution:Options include escaping all square brackets, inserting an invisible character, or perhaps wrapping the brackets in "verbatim" tags.
Changed lines 1-2 from:
:Summary:Leading spaces at the start of pre-formatted text are lost
to:
:Summary:[Bracketed text] at the start of a list item is misinterpreted
Changed lines 9-10 from:
:Description:If a line starts with multiple leading spaces, denoting indented preformatted text, the leading spaces are lost on output.
to:
:Description:If a list item starts with text in square brackets (ie not markup) the bracketed text is interpreted as over-riding the default list symbol. For example:
* [some text] then regular text
Changed lines 15-16 from:
to:
:Proposed solution:Options include escaping the square brackets, inserting an invisible character, or perhaps wrapping the brackets in "verbatim" tags.
Added lines 1-21:
:Summary:Leading spaces at the start of pre-formatted text are lost
:Type:Bug
:Raised by:[[~John Rankin]]
:Date opened:2006-01-17
:Description:If a line starts with multiple leading spaces, denoting indented preformatted text, the leading spaces are lost on output.
:Importance:3
:Proposed solution:
:Urgency:3
:Status:Open
:Resolution:
:Date closed: