X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <4E9482B4.5070909@xs4all.nl> Date: Tue, 11 Oct 2011 19:53:56 +0200 From: Erwin Waterlander User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: How To Handle Special Characters in Cygwin, E.G., Trademark Symbol, n with the tilde above it References: <099f01cc882c$aa4021d0$fec06570$@vaultnow.com> In-Reply-To: <099f01cc882c$aa4021d0$fec06570$@vaultnow.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Op 11-10-2011 17:44, Leon Vanderploeg schreef: > Greetings, > > I have recently encountered a problem with accessing files that have special > characters in the file names. The special characters include (a couple > examples) the trademark symbol and the n with a tilde above it. The > recommendation from " > http://www.cygwin.com/cygwin-ug-net/using-specialnames.html" is: > ============================= > Filenames with unusual (foreign) characters > Windows filesystems use Unicode encoded as UTF-16 to store filename > information. If you don't use the UTF-8 character set (see the section > called "Internationalization") then there's a chance that a filename is > using one or more characters which have no representation in the character > set you're using. > Note > > In the default "C" locale, Cygwin creates filenames using the UTF-8 > charset. This will always result in some > valid filename by default, but again might impose problems when > switching to a non-"C" or non-"UTF-8" charset. > > Note > > To avoid this scenario altogether, always use UTF-8 as the character > set. > ============================= > > Suggestions on how to access these files? > > What problems do you get? As long as you stick to UTF-8 character encoding there should be no problems. The language doesn't need to be C. I use locale nl_NL.UTF-8 without problems. In case your program uses gettext/libintl set the LANG environment variable explicitly to something.UTF-8. Otherwise a bug in libintl may cause that your program doesn't see the UTF-8 locale encoding. Use mintty instead of the default console for correct display. Erwin -- 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