25 Sep
2010
25 Sep
'10
8:49 a.m.
On Fri, Sep 24, 2010 at 3:05 PM, Robin Gareus <robin@xxxxxxxxxx> wrote:
..and in case there are files with whitespaces in the
filename, change
the default string separator:
#/bin/bash
IFS=:
# do stuff
unset IFS
Or remove spaces from all filenames. Why would one want spaces in filenames anyway ?
To me it feels a bit like putting spaces in variable names, which isn't a good idea
either.
Cheers,
Marc
#! /bin/bash
#
# spaces2underscores.sh
echo
echo "This command changes all spaces in file names into underscores"
echo " for ALL FILES IN THIS DIRECTORY !"
echo " Type ENTER to continue or ^C to quit"
read dummy
for f in *; do
oldname=`echo $f |sed 's/ /~/g'`
newname=`echo $f |sed 's/ /_/g'`
if [ $oldname != $newname ]
then
echo mv $f $newname
mv "$f" $newname
fi
done
3:05 p.m.
New subject: No batch processing on Linux?
Am 25.09.2010 09:39, schrieb Arve Barsnes:
On Sat, Sep 25, 2010 at 8:49 AM, Marc
Groenewegen<marcg(a)dinkum.nl> wrote:
A file-name is a very technical thing. It should be readable and
unmistakable for simple software, if it is readable for subtle humans
also: very good! But the technical aspect should be the 1st priority.
So Miles_Davis, Black_Sabbath or Ludwig_van_Beethoven are perfectly OK
to me. Interesting though what to do with SunO))))) and the like ;-)
The Names in correct Orthography have their place in properly written
ID3-Tags in UTF-8
Why would one want spaces in filenames anyway ?
Because his name isn't Miles_Davis _______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
3:51 p.m.
New subject: No batch processing on Linux?
On Mon, Sep 27, 2010 at 9:33 AM, Jeremy Jongepier <jeremy(a)autostatic.com> wrote:
On 09/25/2010 03:05 PM, Hartmut Noack wrote:
maybe. but that doesn't cover 谭盾 or Ãîñ. Àêàäåìè÷åñêèé ñèìôîíè÷åñêèé
îðêåñòð ÑÑÑÐ, Äèðèæåð Å. Ñâåòëàíîâ
not to mention tracks that feature combinations of all of these
characters: ,:'")(\
this is why you don't want to use shell scripts for this stuff.
basically, the set of all possible UTF-8 characters in a filename is
the full possible set of all UTF-8 characters. there are no characters
left other than null that can act as word separators.
Interesting though what to do with SunO))))) and
the like
One listens to Sun O))) live or from vinyl. 
4:25 p.m.
New subject: No batch processing on Linux?
On Mon, September 27, 2010 6:51 am, Paul Davis wrote:
On Mon, Sep 27, 2010 at 9:33 AM, Jeremy Jongepier
<jeremy(a)autostatic.com>
wrote:
Well I found out today that even perl gets confused with *some* utf-8
chars so don't rely on that either :-)
--
Patrick Shirkey
Boost Hardware Ltd.
On 09/25/2010 03:05 PM, Hartmut Noack wrote:
maybe. but that doesn't cover è°ç¾ or Ãîñ. Ãêà äåìè÷åñêèé
ñèìôîÃè÷åñêèé
îðêåñòð ÃÃÃÃ, Ãèðèæåð Ã
. Ãâåòëà Ãîâ
not to mention tracks that feature combinations of all of these
characters: ,:'")(\
this is why you don't want to use shell scripts for this stuff.
basically, the set of all possible UTF-8 characters in a filename is
the full possible set of all UTF-8 characters. there are no characters
left other than null that can act as word separators.
Interesting though what to do with SunO))))) and
the like
One listens to Sun O))) live or from vinyl. 
7:36 p.m.
New subject: No batch processing on Linux?
On Mon, Sep 27, 2010 at 07:25:41AM -0700, Patrick Shirkey wrote:
Well I found out today that even perl gets confused
with *some* utf-8
chars so don't rely on that either :-)
If you can create a simple test case, it would be helpful to
file a report. Existing unicode related bugs are here:
http://rt.perl.org/rt3/NoAuth/perl5/List.html?Field=Type&Value=Unicode
Regards,
Joel
--
Joel Roth
28 Sep
28 Sep
10:35 p.m.
New subject: No batch processing on Linux?
* Paul Davis [2010-09-27 09:51]:
maybe. but that doesn't cover 谭盾 or Ãîñ.
Àêàäåìè÷åñêèé ñèìôîíè÷åñêèé
îðêåñòð ÑÑÑÐ, Äèðèæåð Å. Ñâåòëàíîâ
You might want to rename/re-tag that last one... That's Windows codepage
1251 (Cyrillic) misinterpreted as Latin-1 (aka mojibake):
$ echo 'Ãîñ. Àêàäåìè÷åñêèé ñèìôîíè÷åñêèéîðêåñòð ÑÑÑÐ, Äèðèæåð Å. Ñâåòëàíîâ' |
recode u8..latin1 | recode windows-1251..u8
Гос. Академический симфоническийоркестр СССР, Дирижер Е. Светланов
(USSR State Academic Symphony Orchestra, conductor: Yevgeny Svetlanov)
29 Sep
29 Sep
12:59 a.m.
New subject: No batch processing on Linux?
On Tue, Sep 28, 2010 at 4:34 PM, Alexandros Diamantidis <adia(a)hellug.gr> wrote:
* Paul Davis [2010-09-27 09:51]:
all relevant software in my house (rhythmbox and our squeezeboxes)
display it correctly. the fact that the shell doesn't is not of much
consequence to me:)
maybe. but that doesn't cover 谭盾 or Ãîñ.
Àêàäåìè÷åñêèé ñèìôîíè÷åñêèé
îðêåñòð ÑÑÑÐ, Äèðèæåð Å. Ñâåòëàíîâ
You might want to rename/re-tag that last one... That's Windows codepage
1251 (Cyrillic) misinterpreted as Latin-1 (aka mojibake):
$ echo 'Ãîñ. Àêàäåìè÷åñêèé ñèìôîíè÷åñêèéîðêåñòð ÑÑÑÐ, Äèðèæåð Å. Ñâåòëàíîâ' |
recode u8..latin1 | recode windows-1251..u8
Гос. Академический симфоническийоркестр СССР, Дирижер Е. Светланов
(USSR State Academic Symphony Orchestra, conductor: Yevgeny Svetlanov) 
5 Oct
5 Oct
1:59 p.m.
New subject: More spaces in filenames [was: No batch processing on Linux?]
On Sat, Sep 25, 2010 at 8:49 AM, Marc Groenewegen <marcg at dinkum.nl>
wrote:
Why would one want spaces in filenames anyway ?
Cheers,
Marc
#! /bin/bash
#
# spaces2underscores.sh
echo
echo "This command changes all spaces in file names into underscores"
echo " for ALL FILES IN THIS DIRECTORY !"
echo " Type ENTER to continue or ^C to quit"
read dummy
for f in *; do
oldname=`echo $f |sed 's/ /~/g'`
newname=`echo $f |sed 's/ /_/g'`
if [ $oldname != $newname ]
then
echo mv $f $newname
mv "$f" $newname
fi
done
The if [ $oldname != $newname ] bit is nice; avoids errors with mv.
You could also get rid of other nasties with
newname=`echo $f | tr ' ' '_' | tr -d '[{}(),\!]' | tr -d
"\'" | sed
's/_-_/_/g'`
But if directories have spaces as well, one solution is (from somewhere
on the Arch Linux forums)
#! /bin/bash
# remove spaces from directory names and contents recursively
IFS=$'\n'
function cleanup {
if [ -d "$1" ];
then
DIR="$1"
cd "$DIR"
fi
pwd
for f in `find . -maxdepth 1`; do
[ -d "$f" -a "$f" != "." ] && (cleanup
"$f")
file=$(echo $f | tr ' ' '_' )
[ -e "$f" ] && [ ! -e "$file" ] && mv
"$f" "$file"
done
[ "$DIR" ] && cd - > /dev/null
}
cleanup .
unset IFS
Even better is this (from perlmonks.org/?node_id=27739)
find2perl . -depth -eval 'my $o=$_; tr/_/ /; -e or rename $o,$_ or warn
"cannot rename $o to $_: $!"' | perl
Does the lot in one hit.
4959
days inactive
4969
days old
linux-audio-user@lists.linuxaudio.org
9 comments
9 participants
participants (9)
-
Alexandros Diamantidis -
Arve Barsnes -
Hartmut Noack -
Jeremy Jongepier -
Joel Roth -
M Watts -
Marc Groenewegen -
Patrick Shirkey -
Paul Davis