Perl: the Markov chain saw | |
PerlMonks |
Re^2: Pod::Simple::Wiki::Textile alternativesby kcott (Archbishop) |
on Aug 25, 2021 at 16:52 UTC ( [id://11136081]=note: print w/replies, xml ) | Need Help?? |
G'day Rolf, ++ Thanks for responding. I think we're very much on the same page here. If I take the HTML produced by the "Textile to HTML converter", then modify it such that it renders the same (or at least equivalent) perldoc output, I have:
If I look at that in my browser, the only difference between it and perldoc is the characters used for the dot points: browser has disc (level 1) and circle (level 2); perldoc has asterisk for both levels (the indentation is correctly rendered in both cases). If I pass the HTML (above) through an HTML to Textile converter, everything after the "Test nesting." paragraph is pure HTML (there's no Textile at all here). It looks like this:
The converter I've been using throughout is Pandoc. Although I've used Textile a lot, I wouldn't claim to be an expert. In HTML, an <li> is a block element allowing the inclusion of other block elements; e.g. <p>, <ul>, and so on. In Textile, you can implement <li> nesting only with very simple constructs, such as:
You can't turn any of those * contructs into real, block-level <li> constructs that allow complex block structures to be included. I believe this to be the fundamental, underlying problem. Textile neither has the capacity for, nor was designed for, this level of markup complexity. "Otherwise share your tests with the author of Pod::Simple::Wiki and file a bug report." Yes, I was definitely thinking along these lines myself; however, looking at https://github.com/jmcnamara/pod-simple-wiki/issues, I was wondering if a fix would be provided in a timely manner, or if I'd just get "Thanks for the report. Can you provide a patch?". I'll await other input and then make a decision on how to procede. Thanks again for your response. — Ken
In Section
Seekers of Perl Wisdom
|
|