How is l10n/i18n generated "pod" going to work (how is the user going to care about it, experience it ... how will you package it )?

_generate_pod would not appear to belong inside App::ClusterSSH::Getopt ... how your project generates documentation is important stuff that should be documented (in pod) for you and other developers of this app of yours

I think its common to seperate code based on if its for-users-of-your modules and for-writers-of-your-module

How pod is generated doesn't sound like something users-of-your-module need to be cluttered with :)

I've seen a few distributions generate pod but they don't take l10n into account

So, Locale::Maketext way of organizing the localization data ( Handel::L10N::fr/Apache::MP3::L10N::fr ) sounds good ; esp if you avoid the pitfalls ( Rassie's Doghouse » On the state of i18n in Perl )

Generating pod sounds good ... be sure to add the headings  =head NAME to your i18n data

So I don't really see anything too messy ... it is what it is ;)

In reply to Re: Organising and localising generated POD by Anonymous Monk
in thread Organising and localising generated POD by duncs

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.