|
From: Michalis K. <ka...@us...> - 2026-03-30 01:56:54
|
- **status**: open --> closed - **Group**: --> --- **[feature-requests:#2] add a wiki "markup" parser** **Status:** closed **Group:** **Created:** Thu May 01, 2003 06:28 PM UTC by Johannes Berg **Last Updated:** Mon Mar 30, 2026 01:56 AM UTC **Owner:** Johannes Berg When writing documentation, it can sometimes be very convenient to be able to write things in "<b>bold</b>" or "<i>italic</i>", make lists with "<ul><li>" etc. This is just being discussed on the mailing list, and Thomas says that the output should change all characters into their respective HTML entities. This would mean that such code as I wrote above is written as-is, and displayed, instead of being printed. I think that is the correct way to handle it, getting rid of those strange "@<" and "@>" constructs. But on the other hand, I do think that some documentation formatting is needed. But this again is impossible to produce in - for example - latex output, because there this is completely different. So the real solution to this is to add a (very) limited HTML parser, that can recognise only the basic tags: <b>, <i>, <ul>, <li> and maybe something along the lines of pseudo-html: <red>, <green>, <blue>, <#1278EF> for colours all along their respective closing tags (closing tag for colour would be </#> then). This parser would have to have a generic interface so that each output generator would be able to provide the correct translation. I think error checking should be kept rather low, it is the developer's responsibility to feed this something sane (ie, if the output breaks, don't bother in the program). --- Sent from sourceforge.net because pas...@li... is subscribed to https://sourceforge.net/p/pasdoc/feature-requests/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/pasdoc/admin/feature-requests/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |