Thanks for the script.

I have experienced problems when converting files containing utf8 characters (like spanish accents, etc.). The alternative was to convert the file first to isolatin: 

#!/usr/bin/perl -w
use strict;
use Pod::Simple::RTF;
my $file = shift || die "Provide a file name\n";
die "Provide a file name\n" unless -r $file;

my $latin = $file;
$latin = "$file.latin";

my $parser = Pod::Simple::RTF->new();

my $outfile = $file;
$outfile =~ s/\.\w*$/.rtf/ or $outfile = "$file.rtf";

open STDOUT, "> $outfile";

system("iconv -f UTF-8 -t ISO_8859-15 $file > $latin") and die "Can't 
+execute iconv\n";

Pod::Simple::RTF->filter($latin)->any_errata_seen;

unlink $latin;

[download]

In reply to Re: pod2rtf by casiano
in thread pod2rtf by jmcnamara

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.