Hi James,
> Ideally, I'd like to process the file path strings so that (for example) an
> accented e is reduced to an e and so on, for some 'sane' mapping that leaves
> the input recognisable.
>
> Is there a library to do such a thing?
The build in base library Data.Char module contains
isUpper/toUpper/isAscii, which you can certainly use to spot the
problematic characters, and easily replace with something like "_".
Using the text-icu package looks like exactly what you want, but
installing it on Windows is a real pain - I managed it with the steps
at
http://stackoverflow.com/a/34538201/160673. Once you have that I am
sure there is a function to do the conversion, but I've no real idea
where.
If it were me, I'd just grab the huge conversion table from
http://stackoverflow.com/a/34272324/160673 and code that up - given
your use case sounds personal, I suspect a pretty good solution with a
few fixups is probably fine.
> Also, my nas has two CPUs, but I find that Shake seems to be serialising the
> cmd executions of ffmpeg and the machine is running at just under 50% load.
> I didn't do anything fancy to enable threading - I thought that was
> unnecessary. Is it expected?
Are you using shakeThreads=2 or -j2? By default Shake uses 1 CPU, but
-j2 will make it use 2, and -j will make it pick appropriately based
on your hardware.
Thanks, Neil