I just found last week that the POD for my Audio::Beep module has been translated into Japanese by the perldoc.jp project. So I offered them to include their translation into my CPAN release of the module. Now for a few questions:

• What's the best place to install the Japanese documentation? My first thought was to install it as Audio::Beep_jp, but i'm not sure that's correct.
• Would it be acceptable to render Makefile.PL interactive and ask which version of the documentation to install? Could it broke non-interactive installations by CPAN Testers?
• What about checking some locale variable to automatically make a choice? But my guess is it could be error prone, so i'm not sure.

Maybe something coded along the lines of the following pseudo-code could do the trick:

if (shell is interactive) {
    if (ask "Do you want to install Japanese docs?") {
        install japanese_docs;
    } else {
        install standard_docs;
    }
} else {
    if (check_locale == 'jp') {
        install japanese_docs;
    } else {
        install standard_docs;
    }
}
[download]

What you think? Any better ideas or any guidelines or already defined standards? Thanks.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.