Nine, count 'em, nine zeros before the search and replace strings. You may also need a /UNICODE= option if either the input file or the output file uses UTF-8 or UTF-16.
Does it work as expected if you use %@CHAR[160] instead of the accented letter? Because I suspect you may be getting bitten by OEM-to-Unicode conversion, somewhere along the line.
(TCC uses Unicode internally, but characters from a batch file, or e.g. copied from the clipboard, can be in an OEM character set. And the conversions don't always work as you might expect.... And to muddy the waters further, console programs like TCC often use a different OEM character set than graphical programs like the text editor you use to write your batch file! Windows is a mess.)
Does it work as expected if you use %@CHAR[160] instead of the accented letter? Because I suspect you may be getting bitten by OEM-to-Unicode conversion, somewhere along the line.
(TCC uses Unicode internally, but characters from a batch file, or e.g. copied from the clipboard, can be in an OEM character set. And the conversions don't always work as you might expect.... And to muddy the waters further, console programs like TCC often use a different OEM character set than graphical programs like the text editor you use to write your batch file! Windows is a mess.)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.