Page 1 of 1

Problems with © symbol

PostPosted: Sun Feb 23, 2020 4:52 pm
by Stanxx
Hi,
I'm trying to use BRC to change my file names from this format: ©_Stan_Tess_20180512_0392 copy.jpg to this format: _stan_tess_20180512_0392.jpg I hve a problem with the © symbol. I have tried : BRC64.exe /QUIET /DIR:"Q:\Digital Photographs\Gallery\WOW Slider Corrected\Incoming WOW Slider Corrected\images" /REMOVECHARS:© /REPLACECS: _Stan_Tess_:_stan_tess_ /REMOVEFROMTO:25:255 /EXECUTE and BRC64.exe /QUIET /DIR:"Q:\Digital Photographs\Gallery\WOW Slider Corrected\Incoming WOW Slider Corrected\images" /REGEXP:(©):() /REPLACECS: _Stan_Tess_:_stan_tess_/REMOVEFROMTO:25:255 /EXECUTE and BRC64.exe /QUIET /DIR:"Q:\Digital Photographs\Gallery\WOW Slider Corrected\Incoming WOW Slider Corrected\images" /REPLACECS:© _Stan_Tess_:_stan_tess_/REMOVEFROMTO:25:255 /EXECUTE but none of these work. I have used this: BRC64.exe /QUIET /DIR:"Q:\Digital Photographs\Gallery\WOW Slider Corrected\Incoming WOW Slider Corrected\images" /REMOVEFIRSTN:1 /REPLACECS: _Stan_Tess_:_stan_tess_/REMOVEFROMTO:25:255 /EXECUTE which works but this is not a great solution because if I happen to run it multiple times on the same file it keeps removing the first character in the file name shortening the name. The /REMOVECHARS:© would be the desired solution if it would work.
This is on Win 10 and with the latest copy of BRC.

Re: Problems with © symbol

PostPosted: Mon Feb 24, 2020 1:05 pm
by therube
Looks good on my end, Win7.

Code: Select all
C:\TMP\>BRC32.exe"  /removechars:c  /REPLACECS:_Stan_Tess_:_stan_tess_  /REMOVEFROMTO:25:255

Processing Folder C:\TMP\
Filename _stan_tess_20180512_0392.jpg                   requires no changes
Filename abcd_?_Stan_Tess_20180512_0392 copy - Copy.jpg would be renamed to abcd__stan_tess_20180512.jpg
Filename ?_Stan_Tess_20180512_0392 copy.jpg             would be renamed to _stan_tess_20180512_0392.jpg

(In what I display here, & from my command prompt, the © character looks wrong [?], but is correct in the actual file name, & looks like BRC is picking things up correctly & will make the correct changes.
Maybe changing the codepage would help with the display, not sure?)

Is Win10 using the CMD shell or something else?

Re: Problems with © symbol

PostPosted: Mon Feb 24, 2020 3:19 pm
by Stanxx
Thanks for the response. I should have said I'm doing this in a batch script. The problem exists on Win 10 and Win Vista. I should also say that on the desktop version of BRU the the Remove Chars © and the Replace ©_Stan_Tess_ with _stan_tess_ works as it should but in the .bat form it doesn't.


The code lines:

BRC64.exe /QUIET /DIR:"Q:\Digital Photographs\Gallery\WOW Slider Corrected\Incoming WOW Slider Corrected\images" /REMOVEFIRSTN:1 /REPLACECS:_Stan_Tess_:_stan_tess_ /REMOVEFROMTO:25:255 /EXECUTE
BRC64.exe /QUIET /DIR:"Q:\Digital Photographs\Gallery\WOW Slider Corrected\Incoming WOW Slider Corrected\images" /REMOVECHARS:© /REPLACECS:_Stan_Tess_:_stan_tess_ /REMOVEFROMTO:25:255 /EXECUTE
BRC64.exe /QUIET /DIR:"Q:\Digital Photographs\Gallery\WOW Slider Corrected\Incoming WOW Slider Corrected\images" /REGEXP:(©):() /REPLACECS:_Stan_Tess_:_stan_tess_ /REMOVEFROMTO:25:255 /EXECUTE

The first line of code works but is not a desirable solution the other two lines do not remove the © character. I've tried to do the © character removal in the batch script and had the same issue. If I change the file name character to something other than the © character then both BRC and the windows script works. I just tried calling PowerShell in the script to remove the © character and found that it does work. I would prefer to do this all in one place so if I can't get BRC to work I will probably go to PowerShell to do the entire task. Has anyone else come across this issue and found a solution? I find it strange the Desktop version BRU works while BRC doesn't. The coding approach may be different?

Extended ASCII characters in batches

PostPosted: Tue Oct 04, 2022 5:53 pm
by Luuk
Recently there is a similiar problem at https://www.bulkrenameutility.co.uk/forum/viewtopic.php?f=3&t=5958
Except he wanted to conduct the '•' character inside of a batch, but these are both extended-ASCII characters.
So the batch first needs a line like chcp 1252 to properly conduct those characters.