On 05/03/16 15:30, Erik Christiansen via luv-main wrote:
Well, a quick check of your post in vim, with "8g8" shows no illegal UTF characters anywhere. With "g8" you can read the UTF-8 for the character under the cursor, e.g. é is "c3 a9".
Thanks for the tip - I am not much of a vim specialist
I'd elide characters from a sample filename, until gsutil stops complaining. Then do a g8 on the offending character. Then you'd have have specific fault diagnostics for a bug report, if that's the way it goes. (It's two-to-one in favour, so far.)
As much as I would want to help Google write better tools for its customers * I really need to get this done so that I can actually get a sever migration done before tomorrow. I have ended up using: # find filenames I want to change find . -regex '.*[é].*' > /root/bad.txt # use PHP to write a bash script ## Because I can code in PHP but it suffers from the same encoding issue # Execute a bash file to copy & delete files ~~~~ Elegant? No. Does the job? Yes * There are two faults that I have with the gsutil -m rsync applications: 1) Does not skip on the file - one broken file means backup no-worky 2) The error message breaks that file name across two+lines so does not paste right into the shell. Thanks for your help Cheers Piers