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.
If I were you, I'd have two files containing pod,
One in English, one in Japanese,
and at Makefile.PL time I'd copy one of them to the appropriate spot (lib/Audio/Beep.pod)
Would it be acceptable to render Makefile.PL interactive and ask which version of the documentation to install?
Yes, but be sure to have a default
Could it broke non-interactive installations by CPAN Testers?
Absolutely. You'll be fine as long as you use ExtUtils::MakeMaker's prompt function or its equivalent.
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.
Locale isn't neccessarily revealing, and even if you do some detecting, you should still prompt.
| MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!" | | I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README). | | ** The third rule of perl club is a statement of fact: pod is sexy. |
-
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.
|
