Ticket #69 (Fixed)Mon Oct 23 16:43:19 UTC 2006
Radiant is much better at Textile than i2
| Reported by: | Andrew Hodgkinson (6) | Severity: | Normal |
| Part: | Web site: General (miscellaneous issues) | Release: | 2nd public site release |
| Milestone: | 2nd public site release completed | Status | Fixed |
Details by Andrew Hodgkinson (6):
Radiant’s handling of Textile is very good. The unescaping hack for, e.g. “C++”, is not needed as it is in I2. Other applications have their own Textile quirks. Can it be standardised, preferably on the Radiant code?
Changelog:
Modified by Andrew Hodgkinson (6) Thu, January 25 2007 - 20:31:59 GMT
I2 (the Wiki) has even worse behaviour, in fact; it seems to be pretty buggy. Definitely need to get this sorted. Note that there is a reference to the formatting problems in the Help page for the Wiki within the Wiki itself – if this bug is fixed, that reference should be deleted.
Modified by Andrew Hodgkinson (6) Sun, March 25 2007 - 18:49:22 GMT
- Status changed from Open to Fixed
The “hard breaks bug” was being triggered. After Changeset #184, I2 uses the system-supplied RedCloth 3.0.3 (rather than the broken 3.0.4) and does not activate hard breaks. Textile handling is as good as Radiant, Collaboa etc. now.
The author of RedCloth, “Why”, is producing a successor aimed at fixing the bugs in the comparatively ancient exising library. It would be good to upgrade to this at some point, provided it gives a material benefit. In the mean time, Textile is fairly stable but does need to be used with some care. The XML-style tag ‘notextile’ is very useful when things aren’t working out how you’d like, particularly with things like ‘C++’.
