Differences

This shows you the differences between the selected revisions of the page.

2017-05-03 2017-05-03
no_mapping_for_unicode (martin) limit acronym recognition (martin)
Line 488: Line 488:
You get this error message, when you try to execute a [[scripting#using_scripting|script]] that does not use a valid UTF-8 (or UTF-16) encoding. You get this error message, when you try to execute a [[scripting#using_scripting|script]] that does not use a valid UTF-8 (or UTF-16) encoding.
-Older versions of WinSCP used legacy ANSI encoding, when the script file does not have UTF-8 (or UTF-16) byte order mark (BOM). The recent versions of WinSCP default to UTF-8 encoding, when no BOM is present. If you have a script written in ANSI encoding for an old version of WinSCP, you have to convert it to UTF-8 (or UTF-16) encoding, when upgrading to a recent version of WinSCP.+Older versions of WinSCP used legacy ANSI encoding, when the script file does not have %%UTF-8%% (or UTF-16) byte order mark (BOM). The recent versions of WinSCP default to %%UTF-8%% encoding, when no BOM is present. If you have a script written in ANSI encoding for an old version of WinSCP, you have to convert it to %%UTF-8%% (or UTF-16) encoding, when upgrading to a recent version of WinSCP.
A simple way to convert the script encoding is: A simple way to convert the script encoding is:
Line 494: Line 494:
  * Open the script in Notepad;   * Open the script in Notepad;
  * Go to //File > Save As//;   * Go to //File > Save As//;
-  * Change //Encoding// from //ANSI// to //UTF-8//;+  * Change //Encoding// from //ANSI// to //%%UTF-8%%//;
  * Click //Save//.   * Click //Save//.

Last modified: by martin