X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 	tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SARE_MSGID_LONG45,SARE_SUB_ENC_UTF8,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4BBC7A21.6020703@cwilson.fastmail.fm>
References: <hpf05p$f9u$1 AT dough DOT gmane DOT org> <hpfb5a$nkd$1 AT dough DOT gmane DOT org> 	 <f2880370bbc92abe3133a595940cf0bf AT shell DOT sh DOT cvut DOT cz> 	 <4BBBD9BF DOT 8060709 AT cwilson DOT fastmail DOT fm> <hph9f8$dq5$1 AT dough DOT gmane DOT org> 	 <4BBC7A21 DOT 6020703 AT cwilson DOT fastmail DOT fm>
Date: Wed, 7 Apr 2010 22:11:10 +0100
Received: by 10.239.185.84 with SMTP id b20mr898237hbh.37.1270674670484; Wed,  	07 Apr 2010 14:11:10 -0700 (PDT)
Message-ID: <o2y416096c61004071411kd3959ebdm36b5a47f5fead581@mail.gmail.com>
Subject: Re: UTF-8 in ftp client.
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

> Oleksandr Gavenko wrote:
>>> ...which is good advice. =C2=A0The other clients MAY support UTF-8 or s=
ome
>>> other explicit i18n/NLS, but the inetutils bare-bones ftp client
>>> doesn't, and won't.
>>>
>> Won't because religion don't allow?

That's a ridiculous question. The GNUs may be rather religious about
software freedom, but they're certainly not opposed to
internationalisation. Quite the opposite, in fact: a lot of effort has
gone into it over many years (see
http://people.redhat.com/drepper/gnuconf96.ps), and I find that GNU
software tends to be better at i18n than most proprietary software.

Charles Wilson wrote:
>> So GNU guies never accept patches for UTF-8 support?
>
> The reason I said it won't, is because *I* have neither the time nor
> sufficient knowledge to implement it -- and I'm the guy that maintains
> cygwin's inetutils (that is, ftp+other stuff) package.

I wouldn't worry about it. 'ftp' supports UTF-8 just fine actually, by
simply passing it through unharmed from the server to the local
system. What it doesn't do is to translate filenames to a local legacy
charset such as CP1251, which is what the OP appears to be using. Of
course he hasn't actually told us, nor has he said whether he's still
using Cygwin 1.5.

Legacy charsets are on their way out, 'ftp' was always meant to be a
barebones client, and more capable alternatives are available anyway,
so there's little point in developing a patch.

Andy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple