You use shell_quote where you shouldn't. (And, arguably, you don't use it where you should.)

-e needs a path, not a piece of shell code.

my $src_qfn = 'BulletinV3, 1 Montana 20xx-xx-xx (print).pdf_FN_TEMPLAT +E'; if (-e $src_qfn) { ... } else { ... }

Or with error checking:

my $src_qfn = 'BulletinV3, 1 Montana 20xx-xx-xx (print).pdf_FN_TEMPLAT +E'; if ( stat( $src_qfn ) ) { ... } else { die( "Can't stat `$src_qfn`: $!\n" ) if !$!{ ENOENT }; ... }

As for that message of command at the bottom,

system( "zenity", "--title" => "Rename problem", "--width" => 400, "--error", "--text" => "Can't rename `$src_qfn` to `$dst_qfn`: $!", )

In reply to Re: Problems with special characters in Linux file names by ikegami
in thread Problems with special characters in Linux file names by EigenFunctions

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.