I haven't used any of these modules either, but based on the evidence you've shown, it seems like the "legacy" behavior of "Locale::Maketext::Extract / xgettext.pl" is sub-optimal (to put it nicely) because it is non-compliant with the other tools that it is supposed to interact with.

So, speaking as an outsider, my vote would be to change the default behavior so as to make it "correct" (compliant with gettext and POEdit), but keep the legacy behavior as an option (in case anyone has actually created code dependent on that format), and be very clear about the change in the docs. (And mention that this "backward compatible" option will be deprecated.)

Among the people who have used Local::Maketext::Extract / xgettext.pl, I wonder how many of them have considered its original output format to be troublesome because of its divergence from the norm? (For that matter, I wonder if this issue was involved in one of the POEdit change-log entries: 

Version 1.3.5
-------------
...
- fixed crash when loading some invalid PO files (#1495970)
...

[download]

In reply to Re: RFC for users of Locale::Maketext::Lexicon by graff
in thread RFC for users of Locale::Maketext::Lexicon by clinton

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.