Hello Perl Monks,

im having a small issue with a parameter on the module WWW::Babelfish.

here is the code:
use WWW::Babelfish; $obj = new WWW::Babelfish( service => 'Google', agent => 'Mozilla/8.0' +); die( "Google server unavailable\n" ) unless defined($obj); $en_text = $obj->translate( 'source' => 'English', 'destination' => 'Spanish', 'text' => "i am mexican with black h +air and brown eyes", 'delimiter' => "\n\t", 'ofh' => \*STDOUT); die("Could not translate: " . $obj->error) unless defined($en_text); @languages = $obj->languages;


As i read on CPAN, the parameter 'ofh'
ofh: Output filehandle; if provided, the translation will be written to this filehandle.

ofh parameter must be a filehandle. what kind of filehandle?? <FH>, how many more are they STDOUT.. etc??

my problem is i want to pass the data output to an @array

please help!

In reply to Google Translation using WWW::Babelfish by senik148

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.