Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

[doc] POD escape E<> is not handled by HTML generation #534

Closed
fperrad opened this Issue Apr 16, 2009 · 6 comments

Comments

Projects
None yet
5 participants
Contributor

fperrad commented Apr 16, 2009

for example in book/ch09_pasm.pod,

POD E<#x3C0> is not transformed to HTML entity &#x3C0;

```

  set I0, 42        # set integer register #0 to the integer value 42
set N3, 3.14159 # set number register #3 to an approximation of E<#x3C0>
```

Originally http://trac.parrot.org/parrot/ticket/559

Contributor

allisonrandal commented Apr 20, 2009

Which HTML generator are you using?

In the default settings for Pod::Simple (or any Pod parser), tags like E<> aren’t processed in code examples. The behavior can be enabled in Pod::Simple (or subclasses of Pod::Simple) by calling:

$parser-&gt;codes_in_verbatim(1);

where $parser is the instance of Pod::Simple (or subclass).

Contributor

allisonrandal commented Apr 20, 2009

Removed the escape code for ‘pi’ in 38220.

Contributor

coke commented Jan 30, 2011

Tried this:

diff --git a/lib/Parrot/Docs/PodToHtml.pm b/lib/Parrot/Docs/PodToHtml.pm
index 63e1177..6e46adc 100644
--- a/lib/Parrot/Docs/PodToHtml.pm
+++ b/lib/Parrot/Docs/PodToHtml.pm
@@ -49,6 +49,8 @@ sub new {
         PASM_INVALID PASM_TODO
         PIR_FRAGMENT_INVALID
     ));
+    $new->codes_in_verbatim(1);
+
     delete(@{$new-&gt;{'Tagmap'}}{'Data','/Data'});
     return $new;

Doesn't seem to have any effect.

Contributor

coke commented Jan 30, 2011

See also #674.

Contributor

coke commented Jan 30, 2011

See also #1743 & #558.

Contributor

paultcochrane commented Mar 8, 2014

The original documentation issue seems to have been corrected (the file seems to be now called docs/book/pir/ch04_variables.pod). Can this issue thus be considered resolved?

@rurban rurban closed this Mar 11, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment