A couple of comments first. Standard comment 1 applies: use strict; use warnings;.

More immportant for your future code: you should use the three parameter open open (FH, "<", $path) to avoid the possibility of nasty stuff happening due to bad (in a couple of senses) file names.

Having dealt with that here is some code to start with:

#! /usr/bin/perl use strict; use warnings; print 'Enter path of old file: '; chomp(my $inPath = <>); open (inFile, "<", "$inPath") || die "Failed to open in file: $!\n"; print 'Enter path of new file: '; chomp(my $outPath = <>); open (outFile, ">", "$outPath") || die "Failed to create out file: $!\ +n"; while (<inFile>){ $_=~ tr/a-zA-Z/0-310/; print outFile " $_\n"; } close inFile; close outFile;

DWIM is Perl's answer to Gödel

In reply to Re: Take file A , translate it, place in new file by GrandFather
in thread Take file A , translate it, place in new file by sub_chick

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.