LanX has asked for the wisdom of the Perl Monks concerning the following question:
Am I wrong or did metacpan "break" some extended display options cpan.org had?
Like:
On a similar note, github is using README as main entry page and allows using README.pod as alternative to markdown.
But while markdown seems to allow internal links and images this seems hard in pod.
I can't figure out how to write a L<> to link to the main module.
I suppose this is due to ambiguous definition of POD standard.
These links are broken now, going manually to the html files only shows the raw text for me.
OK the link L<lisp/doc/pde/index.html> doesn't use a scheme like html: I suppose this used to work in the old times.
lisp is interpreted as a module name.
On github prepending a ./ will not search a relative path inside the distribution.
Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: POD: embedding/linking/displaying html and images on metacpan and github
by Corion (Patriarch) on Mar 18, 2019 at 13:40 UTC | |
by LanX (Saint) on Mar 18, 2019 at 13:55 UTC | |
|
Re: POD: embedding/linking/displaying html and images on metacpan and github
by LanX (Saint) on Mar 18, 2019 at 13:24 UTC | |
by hippo (Archbishop) on Mar 18, 2019 at 13:53 UTC | |
by stevieb (Canon) on Mar 18, 2019 at 18:27 UTC | |
by LanX (Saint) on Mar 18, 2019 at 13:57 UTC | |
|
Re: POD: embedding/linking/displaying html and images on metacpan and github (=for html workaround)
by LanX (Saint) on Mar 18, 2019 at 14:24 UTC |