Re: How the MV documentation is maintained

[Erik Aase-Remedios <erik@fourfish.com>]

******    message to minivend-users from Erik Aase-Remedios <erik@fourfish.com>     ******

I believe it's all in POD.  See
<http://www.minivend.com/minivend/minivend.pod> for an example.
POD's pretty simple.  see 'perldoc perlpod' or
<http://www.perl.com/CPAN-local/doc/manual/html/pod/perlpod.html>.

As far as multiple languages, You could start with Babelfish and eventually
have people do translations.  It'd probably be best to maintain separate
POD documents in each language.

Try Babelfish with the description to see how it works:
<http://babelfish.altavista.com/cgi-bin/translate?urltext=http://www.miniven
d.com/minivend/docindex/01.00.DESCRIPTION.html&lp=en_de&doit=done>.
Granted it's not the best with technical documents and sometimes produces
quite humorous results ;-)=

-Erik


>>>>> Birgitt Funk wrote (04:19 AM 2/6/99 ):
>******    message to minivend-users from Birgitt Funk <birgitt@minivend.com> 
>    ******
>
>
>Dear MiniVenders !
>
>I read in the FAQ, that if one provides edited replacement text for
>the documentation, the source is available to understand how it is
>maintained.
>
>I would like to understand how the production of the documentation
>works and wonder what an acceptable method would be to provide a
>translated and may be at times extended documentation/guide to
>the author, Mike Heins, without being interruptive, but with getting
>approval for the provided edited and/or translated text.
>
>Couldn't one use the locale features of an MV catalog itsself to
>create a catalog of documentation pages in several languages ?
>
>Birgitt Funk
>

-
To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list