[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: "Strange" characters in file names

From: Flavio Stanchina <flavio_at_stanchina.net>
Date: 2007-03-27 17:52:11 CEST

Hans Salvisberg wrote:
> I use Putty on Windows. I can indeed set it to UTF-8, then the 'รค' becomes a Sigma, because I'm using a OEM/DOS font with Putty (to get proper box drawing characters for working with mc). If I change Putty to use a "Western" font, then the umlaut displays perfectly, but I lose the box drawing characters.

You're seeing another manifestation of the same problem: one of the
steps that bring the file name as stored on disk to your display has a
wrong idea of what character encoding it's dealing with. In this case, I
guess, PuTTY thinks the font you're using is ANSI but it's in fact an
OEM font.

Ironically, your email contained an accented character but no indication
of the character set it used, so my Thunderbird chose to display it as
UTF-8 when it was really ISO-8859-1 (or maybe Windows-1252, which is
almost, but not exactly, the same).

By setting LANG, you're not introducing any bias towards a specific
language, you're just telling the tools on the other side of your
terminal which encoding you're expecting and sending. It's then the
tools' job to encode their output (or decode their input) according to
that setting. In the same way, the users who send files will have to set
their encoding properly so when they send a file with non-ASCII
characters in the name (be it German, French or Chinese) the system
knows how to translate them into the on-disk encoding (which happens to
be UTF-8 or UTF-16 for most modern file systems).

-- 
Ciao, Flavio
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 27 17:52:45 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.