Help language development. Donate to The Perl Foundation

Pod::To::Pager cpan:TYIL last updated on 2018-06-23

t/results/test-program.txt
NAME
        Test Program for App::POD::Manual

AUTHOR
        Patrick Spek

VERSION
        0.0.1

LICENSE
        GNU Affero GPL v3

A test program for App::POD::Manual

        Now we're reaching the real POD document that I care about. Let's add in
        some test cases as well here.

  Text styles

        • This text is bold

        • This text is italic

        • This text is underlined

        • This text is code

        • This text is a link[1] to my blog

        • This text is normal 

        • I'm running ouf of ideas [2]

  Lists

          • Starting off at level 2

                • Progressing to leel 5

        • Back to level 1

          • On to level 2

            • On to level 3

              • On to level 4

                      • But what about an item with content that goes
                        well beyond the 80 characters?

                          • Which can easily occur in a block item, for
                            instance. It should wrap around and bring the
                            next lines on a similar level of indentation.

                            The question is, does it?

    Definition lists

        pod
          Plain Ol' Documentation

        foo
          Not the same as bar

  Code blocks

        Now on to some code blocks. These are generally used to show code
        samples.

            ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
            ┃This is a code block. It is indented by 4 spaces to indicate this.┃
            ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

        Code samples are important to easily show a user how to interact with the
        program they're using. Nobody wants to read through pages of a manual
        when they just want to know how to use it for their particular use case.

            ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
            ┃Named code block                                                                                     ┃
            ┠─────────────────────────────────────────────────────────────────────────────────────────────────────┨
            ┃This is a code block by name. It is covered by a begin and end block. It has no limit to line length.┃
            ┃Spaces  in  the  code  are    preserved    .                                                         ┃
            ┃                                                                                                     ┃
            ┃Similar for newlines, actually.                                                                      ┃
            ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

            ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
            ┃Code on a single line should also work as expected.               ┃
            ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

        And that concludes the test for code blocks!

  IO blocks

        There are blocks to denote program input and output, called IO blocks.
        They also have in-line variants:

        • This is keyboard input

        • This is terminal output

        The bigger blocks deserve a test as well, I think:

    Short-hand input and output

            ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
            ┃A simple input line                                               ┃
            ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

            ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
            ┃A simple output line                                              ┃
            ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

    Big input and output blocks

            ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
            ┃A larger block of input.                                          ┃
            ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

            ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
            ┃A larger block of output.                                         ┃
            ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

  Unicode

        And of course, let's throw in some Unicode stuff. I stole these examples
        from the documentation site, but I don't think that's a bad source of
        input for testing purposes.

        Perl 6 makes considerable use of the « and » characters.

        Perl 6 makes considerable use of the laquo and raquo characters.

        Perl 6 makes considerable use of the « and » characters.

        Perl 6 makes considerable use of the « and » characters.

        Perl 6 makes considerable use of the « and » characters.

        Perl 6 makes considerable use of the « and » characters.

Footnotes and references

        1:  https://www.tyil.work
        2:  Search the Internet for more!