WinSCP to Ubuntu SFTP charset problem

Matthew Flaschen matthew.flaschen at gatech.edu
Fri Feb 13 03:49:00 UTC 2009


olopopo wrote:
>> You need to clarify.  Is it the filenames that are the issue, or the
>> file content, or both?
> 
> 
> No sorry, it was only an issue with the contents...

Okay, that makes it much easier.

> But since the clients need to access the webpages later through winscp (to
> modify them or change anything) I should have the contents of the files
> unchanged in the ubuntu box so it can be decoded by Windoze at any time.

Windows *can* decode and encode UTF-8.  Now, sometimes it matters what
program you use.  E.g. Notepad will make incorrect guesses sometimes
(http://blogs.msdn.com/oldnewthing/archive/2004/03/24/95235.aspx).  But
 in practice this isn't usually an issue (one reason is that if you save
a UTF-8 file from Notepad it will correctly open it because of the BOM).
 Besides, other editors, such as Notepad2
(http://www.flos-freeware.ch/notepad2.html) will let you choose the
encoding manually.

Since both Windows and GNU/Linux programs can deal with UTF-8 and it is
The FutureĀ®, I suggest you switch to that (or if you want UTF-16,
UTF-32, etc.).  With iconv, the initial conversion won't take much time,
and from then on just use UTF-8 when editing.

>> iconv does not have any built-in file renaming features.
> 
> 
> Ok, sorry I didn't notice. convmv does it for filenames, iconv for contents.

Right.

Matt Flaschen





More information about the ubuntu-users mailing list