"Mark Overmeer via RT" <bug-Mail-Box@rt.cpan.org> wrote:
Show quoted text>
> <URL:
http://rt.cpan.org/Ticket/Display.html?id=20772 >
>
> * slaven@rezic.de via RT (bug-Mail-Box@rt.cpan.org) [060925 19:46]:
> > > line fully enclosed in an S<< >>. So: I do not need the bug in Pod::Man
> > > anymore.
> > >
> > > OODoc 0.94 contains this fix. MailBox 2.067 has been generated with
> > > that. Both just released. Does it work for you now?
> > >
> >
> > Unfortunately not. If I use pod2man and perldoc now, then the output
> > looks right. However, this is pure coincidence, because every
> > consecutive line pair in the option-describing block has more than 80
> > characters in sum, so the renderer cannot put it into one line, but
> > creates two separate lines. Just try it: shorten the first line
> > containing "Option" and the next line to about 35 characters each, and
> > they will be rendered into on line.
>
> I am aware of this problem. Happily, the lines are usually longer.
> Iff POD only had a <br> equivalent :-(
>
> > If you use another output, e.g. nroff/Postscript with
> > pod2man Dir.pod | groff -Tps -man | gv -
>
> Apparently, the "no-breaking" what is set by pod2man is not working
> for groff. So pod2man is not POD conformant when used in combi
> with groff.
The non-breaking also works, but the generated postscript has
proportional fonts, so lines are usually smaller. If you put everything
in C<< ... >>, then it looks OK.
Show quoted text>
> > or pod2html then you'll see that it still does not align nicely.
>
> Of course, non proportional fonts.
>
Yes, by using C<<...>> it looks much better. But usually the width of
browser windows is such that the breaking of lines does not work.
As a hack, you could use
=for html <div style="width:500px;">
at top and
=for html </div>
at the end of the options block. pod2html would generate invalid HTML
and I have no good feeling about the hardcoded 500px, but in my Mozilla
the output looks like expected.
Show quoted text>
> This seems a bug in the translators: within an S<>, they should translate
> blanks into But after that, non-prop fonts are still spoling the
> table. Put all in C<> as well?
>
Yes, see above, this helps a lot.
Show quoted text> > annocpan.org, or ActivePerl's documentation.
> >
> > What about my other suggestion, emitting a =for html block, so it
> > looks at least OK with HTML renderers? You really don't need L<...>
> > and C<...> entity expansion for plain text renderers like pod2text or
> > pod2man, the difference isn't visible at all. So maybe it's best to
> > have the =for html block for HTML and a normal verbatim block for all
> > others. And meanwhile ask the pod-people if they could specify
> > something better in perlpodspec.
>
> It's the other way around: my starting-point is texts with markup.
> What I need is that either
> * that markup is interpreted within verbatim blocks
> or * that markup can be stripped automatically.
>
> So: if I would may make a =for html block, then I still need the
> second feature for ``=for text''.
And =for man and =for latex and ... I see. There's no "else" for "for"
blocks.
Show quoted text> I favour the first solution,
> But seeing your evidence, the only way-out is presumably to create
> my own markup-stipper :(
Regards,
Slaven
--
__o Slaven Rezic
_`\<,_ slaven <at> rezic <dot> de
__(_)/ (_)____
Show quoted text______________________________________________________________________________
