Comparing revisions for WantedFormatters
- [7358] 2005-04-18 10:22:08 by DarTar (unregistered user) [Adding link to see also box]
- [19241] 2008-01-28 00:14:44 by NilsLindenberg (unregistered user) [Modified links pointing to docs server]
Additions:
{{lastedit show="3"}}
>>See also:
I created this page to list proposals about [[FormatterInfo formatters]] that might be implemented in future Wikka releases.
//(text higher or lower in the line than normal)//
CategoryDevelopment
>>See also:
I created this page to list proposals about [[FormatterInfo formatters]] that might be implemented in future Wikka releases.
//(text higher or lower in the line than normal)//
CategoryDevelopment
Deletions:
~-AdvancedFormatter
~-AcronymFormatter
I created this page to list proposals about [[Docs:FormatterInfo formatters]] that might be implemented in future Wikka releases.
~&While I agree on "preformatting" things like signatures and possibly "typographical sharpness", escaping ampersands before test is stored will make source harder to edit for people who don't know HTML - unless you also are going to 'unescape' each time the edit form is displayed. It's simpler and more logical to 'educate' the formatter to escape this special character as it's //already// doing for < and >. ''I've already written (and tested) the code to do this (excluding entities); this will probably become part of the next (1.1.6.1) release.'' -- JavaWoman
[[Ticket:160]] //(text higher or lower in the line than normal)//
CategoryDevelopmentFormatters