We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The two modules that generate HTML from POD, namely Pod::To::HTML and BigPage::To::HTML interpret the POD6 specification differently.
P2HTML renders
=begin foo =end foo
as
<section> <h1>foo</h1> </section>
P2BigPage renders the same POD as empty
=begin foo stuff =end foo
as:
<section> <h1> foo </h1><p>stuff</p></section>
This is clear from the tests in the P2HTML module.
P2BigPage renders this as
stuff
Clarify that the pattern =begin name ... =end name is rendered to <section name="name"> ... </section> without an explicit title.
=begin name ... =end name
<section name="name"> ... </section>
The attribute 'name' has no meaning for the tag <section >, so the information from the pod file can be kept without needing to handle it.
<section >
The text was updated successfully, but these errors were encountered:
I really have no idea. What's your take, @tbrowder ?
Sorry, something went wrong.
No branches or pull requests
The problem
The two modules that generate HTML from POD, namely Pod::To::HTML and BigPage::To::HTML interpret the POD6 specification differently.
P2HTML renders
as
P2BigPage renders the same POD as empty
P2HTML renders
as:
This is clear from the tests in the P2HTML module.
P2BigPage renders this as
Suggestions
Clarify that the pattern
=begin name ... =end name
is rendered to<section name="name"> ... </section>
without an explicit title.The attribute 'name' has no meaning for the tag
<section >
, so the information from the pod file can be kept without needing to handle it.The text was updated successfully, but these errors were encountered: