From: James Miller <jamtat@mailsnare.net>
To: linux-newbie <linux-newbie@vger.kernel.org>
Subject: Re: convert windows file names
Date: Fri, 15 Apr 2005 11:37:32 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0504151126000.5717@localhost.localdomain> (raw)
In-Reply-To: <425FDAA8.4060502@vip.cybercity.dk>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset="en_US.UTF-8"; format=flowed, Size: 1192 bytes --]
I tried your perl script and it works really well, Flemming. Thanks for
bringing it to my attention. I see it works for all files in a given
directory--exactly what I need. Now, in place of something like
Patrick\ Cohen\ \&\ Mosaiques\ Quartet\ -\ Quintet\ For\ Piano\ \&\ Strings\ In\ D\ Major\,\ Op.565\,\ G411\ -.\ Andante\ Come\ Prima.mp3
I get
Patrick_Cohen__and__Mosaiques_Quartet_-_Quintet_For_Piano__and__Strings_In_D_Major._Op.56£¯5._G411_-¥²._Andante_Come_Prima.mp3
--a big step in the right direction. But I'm still getting some wierd
characters in there--£¯ and ¥². Are these unicode or something? Anyway, I
can't reproduce these at the command line. Is there any way your script
might be made to catch and replace symbols like these as well (I mean, for
someone who knows absolutely nothing about Perl, and precious little about
scripting in general)? I have no idea what information these symbols are
supposed to be representing. It's probably so inconsequential I don't even
need it, so replacing it with virtually any other symbol should suffice.
I'd say I've got at least 20 files with such symbols, and more are on the
way.
Thanks, James
next prev parent reply other threads:[~2005-04-15 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 15:04 convert windows file names James Miller
2005-04-15 15:15 ` Flemming Greve Skovengaard
2005-04-15 16:37 ` James Miller [this message]
2005-04-15 17:16 ` J.
2005-04-15 18:17 ` Flemming Greve Skovengaard
2005-04-15 19:29 ` James Miller
2005-04-15 15:39 ` Peter
2005-04-15 16:48 ` Ray Olszewski
2005-04-15 18:49 ` James Miller
2005-04-15 18:00 ` chuck gelm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.61.0504151126000.5717@localhost.localdomain \
--to=jamtat@mailsnare.net \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox