Re: UTF-8 quoted args passed to program include quotes when run from cmd

[changed subject] On 2020-10-14 15:47, Jérôme Froissart wrote: >> (As evidence of this: the Cygwin command line parser was able to break the >> command line into arguments correctly, but chose to retain the double >> quotes.) >> >> #include >> >> int main(int argc, char *argv[]) >> {

Re: UTF-8 character encoding

On 6/26/18, Michael Enright wrote: > On Mon, Jun 25, 2018 at 11:33 AM, Lee wrote: >> I'm still trying to figure utf-8 out, but it seems to me that 0x0 - >> 0xff is part of the utf-8 encoding. > > I don't see how you arrived at this. I screwed up trying to do hex in my head. For whatever reason

Re: UTF-8 character encoding

On 6/26/18, Thomas Wolff wrote: > This encoding scheme is wrong; where did you get it from? Maybe it's the > obsolete UTF-8... http://www.cl.cam.ac.uk/~mgk25/ucs/utf-8-history.txt I thought I saw something about utf-8 being able to handle a 31 bit value.. is that also obsolete/wrong? how abou

Re: UTF-8 character encoding

On Mon, Jun 25, 2018 at 11:33 AM, Lee wrote: > I'm still trying to figure utf-8 out, but it seems to me that 0x0 - > 0xff is part of the utf-8 encoding. I don't see how you arrived at this. An initial byte of 0xFF is not the initial byte of any valid UTF-8 byte sequence. And it doesn't conform wi

Re: UTF-8 character encoding

Am 25.06.2018 um 20:33 schrieb Lee: On 6/24/18, L A Walsh wrote: Lee wrote: So... keep it simple, set LANG=en_US.UTF-8 and use vi or something else that comes with cygwin to create the file and I'll have a file with UTF-8 character encoding - correct? --- The first 127 characters o

Re: UTF-8 character encoding

On 6/24/18, L A Walsh wrote: > Lee wrote: >> So... keep it simple, set >> LANG=en_US.UTF-8 >> and use vi or something else that comes with cygwin to create the file >> and I'll have a file with UTF-8 character encoding - correct? > --- > The first 127 characters of UTF-8 are identical to t

Re: UTF-8 character encoding

Lee wrote: So... keep it simple, set LANG=en_US.UTF-8 and use vi or something else that comes with cygwin to create the file and I'll have a file with UTF-8 character encoding - correct? --- The first 127 characters of UTF-8 are identical to the first 127 characters of ASCII, and latin

Re: UTF-8 character encoding

Greetings, Lee! > On 6/20/18, Andrey Repin wrote: >> Greetings, Lee! >> >>> I'm looking at >>> https://cygwin.com/packaging-hint-files.html#pvr.hint >>> and it starts off with >>> Use UTF-8 character encoding. >> >>> How do I do that and how do I check that I actually did use UTF-8 >>> charact

Re: UTF-8 character encoding

On 6/20/18, Andrey Repin wrote: > Greetings, Lee! > >> I'm looking at >> https://cygwin.com/packaging-hint-files.html#pvr.hint >> and it starts off with >> Use UTF-8 character encoding. > >> How do I do that and how do I check that I actually did use UTF-8 >> character encoding _without_ using

Re: UTF-8 character encoding

On Thu, 21 Jun 2018 12:12:39, Houder wrote: > On Wed, 20 Jun 2018 14:09:59, Lee wrote: > > I'm looking at > > https://cygwin.com/packaging-hint-files.html#pvr.hint > > and it starts off with > > Use UTF-8 character encoding. > > > > How do I do that and how do I check that I actually did use U

Re: UTF-8 character encoding

On Wed, 20 Jun 2018 14:09:59, Lee wrote: > I'm looking at > https://cygwin.com/packaging-hint-files.html#pvr.hint > and it starts off with > Use UTF-8 character encoding. > > How do I do that and how do I check that I actually did use UTF-8 > character encoding _without_ using file? [snip] >

Re: UTF-8 character encoding

Greetings, Lee! > I'm looking at > https://cygwin.com/packaging-hint-files.html#pvr.hint > and it starts off with > Use UTF-8 character encoding. > How do I do that and how do I check that I actually did use UTF-8 > character encoding _without_ using file? https://www.joelonsoftware.com/2003

Re: UTF-8 character encoding

Am 20.06.2018 um 20:09 schrieb Lee: > I'm looking at > https://cygwin.com/packaging-hint-files.html#pvr.hint > and it starts off with > Use UTF-8 character encoding. > > How do I do that and how do I check that I actually did use UTF-8 > character encoding _without_ using file? > > for whatev

Re: UTF-8 compatibility between Windows and Cygwin

Greetings, Nellis, Kenneth! > I have (BOM-less) UTF-8 text files that I can read fine in > Cygwin, but not Windows. When I create text files in Windows > containing non-ASCII characters, I cannot read them in > Cygwin. I understand why, but wondering the best way to be > able to share text fil

Re: utf-8 support with getclip?

Am 19.04.2012 02:18, schrieb Charles Wilson: On 4/18/2012 8:06 AM, Andy Koppe wrote: On 17 April 2012 13:35, Chris Sutcliffe wrote: I'm having an issue with getclip and pasting utf-8 strings (like "PONIEDZIAŁEK" for example). Using mintty and right clicking I get exactly what's in the clipboar

Re: utf-8 support with getclip?

On 4/18/2012 8:06 AM, Andy Koppe wrote: > On 17 April 2012 13:35, Chris Sutcliffe wrote: >> I'm having an issue with getclip and pasting utf-8 strings (like >> "PONIEDZIAŁEK" for example). Using mintty and right clicking I get >> exactly what's in the clipboard. If I call getclip from the command

Re: utf-8 support with getclip?

On 17 April 2012 13:35, Chris Sutcliffe wrote: > I'm having an issue with getclip and pasting utf-8 strings (like > "PONIEDZIAŁEK" for example).  Using mintty and right clicking I get > exactly what's in the clipboard.  If I call getclip from the command > line, I get PONIEDZIA?EK.  My LANG is set

Re: utf-8 support with getclip?

I'm having an issue with getclip and pasting utf-8 strings (like "PONIEDZIAŁEK" for example).  Using mintty and right clicking I get exactly what's in the clipboard.  If I call getclip from the command line, I get PONIEDZIA?EK.  My LANG is set to en_CA.UTF-8. Any help would be appreciated. Thank

Re: UTF-8 breaks 'ascii'

On 4/14/2010 11:45 AM, Charles Wilson wrote: > Kenneth wrote: >> Maybe it shouldn't attempt to display code points 128..255 >> since they aren't really ascii. > > You're probably right. Originally, ascii didn't display those code > points; I added it back when a big concern was getting the "corre

Re: UTF-8 breaks 'ascii'

Charles Wilson wrote: > Kenneth wrote: >> Maybe it shouldn't attempt to display code points 128..255 >> since they aren't really ascii. > > You're probably right.  Originally, ascii didn't display those code > points; I added it back when a big concern was getting the "correct" > fonts for rxvt-win

Re: UTF-8 breaks 'ascii'

Kenneth wrote: > Maybe it shouldn't attempt to display code points 128..255 > since they aren't really ascii. You're probably right. Originally, ascii didn't display those code points; I added it back when a big concern was getting the "correct" fonts for rxvt-windows and cmd.exe so that line gra

Re: UTF-8 in ftp client.

> Oleksandr Gavenko wrote: >>> ...which is good advice.  The other clients MAY support UTF-8 or some >>> 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 religiou

Re: UTF-8 in ftp client.

On 4/7/2010 2:41 AM, Oleksandr Gavenko wrote: > On 2010.04.07 4:02, Charles Wilson wrote: >> ...which is good advice. The other clients MAY support UTF-8 or some >> other explicit i18n/NLS, but the inetutils bare-bones ftp client >> doesn't, and won't. >> > Won't because religion don't allow? No,

Re: UTF-8 in ftp client.

On 2010.04.07 4:02, Charles Wilson wrote: On 4/6/2010 9:22 AM, Václav Haisman wrote: Install lftp or other FTP client using setup.exe. ...which is good advice. The other clients MAY support UTF-8 or some other explicit i18n/NLS, but the inetutils bare-bones ftp client doesn't, and won't. Wo

Re: UTF-8 in ftp client.

On 4/6/2010 9:22 AM, Václav Haisman wrote: > There is no such thing (AFAIK) as "Cygwin ftp client." As reported downthread, this is untrue. The inetutils package contains a bare-bones ftp client (and server). Eventually I plan to provide these as separate packages ("ftp"/"ftp-server" packages). T

Re: UTF-8 in ftp client.

Oleksandr Gavenko: > How can I force Cygwin ftp client use UTF-8? > > ftp> ls > 200 Port command successful > 150 Opening data channel for directory list. > drwxr-xr-x 1 ftp ftp              0 Oct 16  2009 music > drwxr-xr-x 1 ftp ftp              0 Sep 11  2009 pub > drwxr-xr-x 1 ftp ftp          

Re: UTF-8 in ftp client.

On 2010.04.06 16:22, Václav Haisman wrote: On Tue, 06 Apr 2010 15:58:18 +0300, Oleksandr Gavenko<> wrote: On 2010.04.06 12:50, Oleksandr Gavenko wrote: I use filezilla to host file server. As explain article: http://wiki.filezilla-project.org/Character_Set for multilang environment need use

Re: UTF-8 in ftp client.

On Tue, 06 Apr 2010 15:58:18 +0300, Oleksandr Gavenko <> wrote: > On 2010.04.06 12:50, Oleksandr Gavenko wrote: >> I use filezilla to host file server. As explain article: >> >> http://wiki.filezilla-project.org/Character_Set >> >> for multilang environment need use UTF-8. >> >> How can I force Cy

Re: UTF-8 in ftp client.

On 2010.04.06 12:50, Oleksandr Gavenko wrote: I use filezilla to host file server. As explain article: http://wiki.filezilla-project.org/Character_Set for multilang environment need use UTF-8. How can I force Cygwin ftp client use UTF-8? ftp> ls 200 Port command successful 150 Opening data ch

Re: UTF-8 versus utf8

On Sat, 3 Apr 2010, Andy Koppe wrote: Tim McDaniel: Why does talk all about a charset of UTF-8, then "For a list of locales supported by your Windows machine, use the new locale -a command", which shows "utf8" (which matches my XP machine)? .

Re: UTF-8 versus utf8

On Apr 2 16:29, Eric Blake wrote: > On 04/02/2010 04:27 PM, Tim McDaniel wrote: > > Why does talk all > > about a charset of UTF-8, then "For a list of locales supported by > > your Windows machine, use the new locale -a command", which shows > >

Re: UTF-8 versus utf8

Tim McDaniel: > Eric Blake: >>> Why does talk >>> all about a charset of UTF-8, then "For a list of locales supported >>> by your Windows machine, use the new locale -a command", which >>> shows "utf8" (which matches my XP machine)? >> >> UTF-8 is

Re: UTF-8 versus utf8

On Fri, 2 Apr 2010, Eric Blake wrote: On 04/02/2010 04:27 PM, Tim McDaniel wrote: Why does talk all about a charset of UTF-8, then "For a list of locales supported by your Windows machine, use the new locale -a command", which shows "utf8" (wh

Re: UTF-8 versus utf8

On 04/02/2010 04:27 PM, Tim McDaniel wrote: > Why does talk all > about a charset of UTF-8, then "For a list of locales supported by > your Windows machine, use the new locale -a command", which shows > "utf8" (which matches my XP machine)? UTF-8

Re: UTF-8 in Cygwin console on 1.7

On Dec 9 11:48, Andy Koppe wrote: > 2009/12/9 Thomas Wolff: > > So the #define IGN should go as well... > > Yep. > > > Actually, I don't really understand this code part: > > * What is the purpose of the lookup table for the switch rather than just > > switching on a few special control characte

Re: UTF-8 in Cygwin console on 1.7

2009/12/9 Thomas Wolff: > So the #define IGN should go as well... Yep. > Actually, I don't really understand this code part: > * What is the purpose of the lookup table for the switch rather than just > switching on a few special control characters? Good question. > * What is the idea of (rando

Re: UTF-8 in Cygwin console on 1.7

[maybe continue on cygwin-developers?] Andy Koppe wrote: 2009/12/9 Cliff Hones I would guess the change is to file cygwin/fhandler_console.cc, and is simply to remove line 1616 [ cursor_rel (1, 0); ] (after case NULL:) Yep, except that the patch removes the (misnamed) IGN case altogeth

Re: UTF-8 in Cygwin console on 1.7

On Dec 9 05:36, Andy Koppe wrote: > 2009/12/9 Cliff Hones > > I think you missed attaching your fix - or else it has got lost. > > Oops. Here's another attempt. > > > I would guess the change is to file cygwin/fhandler_console.cc, and > > is simply to remove line 1616 [ cursor_rel (1, 0); ] (aft

Re: UTF-8 in Cygwin console on 1.7

2009/12/9 Cliff Hones > I think you missed attaching your fix - or else it has got lost. Oops. Here's another attempt. > I would guess the change is to file cygwin/fhandler_console.cc, and > is simply to remove line 1616 [ cursor_rel (1, 0); ] (after case NULL:) Yep, except that the patch remove

Re: UTF-8 in Cygwin console on 1.7

Andy Koppe wrote: > > 2009/12/8 Cliff Hones: >> >> .. >> >> I have just checked Cygwin 1.5 and this aslo mishandles NUL, so I guess >> >> it is a long-standing problem (or Microsoft oddity, or workaround for >> >> something else...). > > > > I don't know what the story behind that is, but a (trivia

Re: UTF-8 in Cygwin console on 1.7

Andy Koppe schrieb: 2009/12/8 Cliff Hones: Perhaps setup.exe should offer to generate a shortcut (as well as .bat and .ico) with, say, the Lucida font selected? Or just do so without asking? ... Yes it should. As I understood, however, this is not immediately easy because the format th

Re: UTF-8 in Cygwin console on 1.7

2009/12/8 Cliff Hones: > Perhaps setup.exe should offer to generate a shortcut (as well as .bat > and .ico) with, say, the Lucida font selected? Or just do so without asking? We've had a number of questions on this already, and there are likely to be many more. People can always choose the raster

Re: UTF-8 in Cygwin console on 1.7

Andy Koppe wrote: > 2009/12/8 Cliff Hones: >> Is UTF-8 character output fully supported in the standard Cygwin >> console ($TERM=cygwin) under Cygwin 1.7? > > Yes (except it's limited to the Basic Multilingual Plane). You need to > select a Unicode-capable font in the console properties though. >

Re: UTF-8 in Cygwin console on 1.7

2009/12/8 Cliff Hones: > Is UTF-8 character output fully supported in the standard Cygwin > console ($TERM=cygwin) under Cygwin 1.7? Yes (except it's limited to the Basic Multilingual Plane). You need to select a Unicode-capable font in the console properties though. Basically, anything but the de

Re: UTF-8 in Cygwin console on 1.7

Cliff Hones wrote: > [I was rather surprised to discover that non-X rxvt does not handle > UTF-8 output at all, not that this causes me any great concern.] rxvt is dead, upstream, and will never support anything but narrow characters. I'm seriously considering marking it _obsolete sometime after

Re: UTF-8 problem/bug with Cygwin 1.7

On Apr 16 20:37, Gunnar Degnbol wrote: > > David Korn skrev: >>> I have a strange problem with UTF-8 characters when running bash from >>> the Windows command line. I hoped it would go away with the new >>> Cygwin 1.7.0-46, but it is still there. Now I have simplified it down >>> to setting LAN

Re: UTF-8 problem/bug with Cygwin 1.7

David Korn skrev: I have a strange problem with UTF-8 characters when running bash from the Windows command line. I hoped it would go away with the new Cygwin 1.7.0-46, but it is still there. Now I have simplified it down to setting LANG=en_US.UTF-8 and running bash -c "echo £" (where '£' can

Re: UTF-8 problem/bug with Cygwin 1.7

Gunnar Degnbol wrote: > I have a strange problem with UTF-8 characters when running bash from > the Windows command line. I hoped it would go away with the new Cygwin > 1.7.0-46, but it is still there. Can't reproduce this with either -45 or -46: Microsoft Windows 2000 [Version 5.00.2195] (C)

Re: utf-8 problems using cygwin

Alexander Brosch wrote: My problem is that these 2 programs need different versions of the cygwin1.dll. id3v2.exe needs version 1005.24.0.0, otherwise german ä,ö,ü are not written correctly sh.exe needs version 1005.25.0.0, otherwise greek characters are not written correctly We on this list

Re: UTF-8 Terminal - How to?

Jason Pyeron wrote: We use utf teraterm which has a cygterm built in. http://www.google.com/search?source=ig&hl=en&rlz=&q=teraterm+utf http://ttssh2.sourceforge.jp/ -- Thank you very much. This looks like it will work well. Jerry -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-

RE: UTF-8 Terminal - How to?

We use utf teraterm which has a cygterm built in. http://www.google.com/search?source=ig&hl=en&rlz=&q=teraterm+utf http://ttssh2.sourceforge.jp/ -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron

Re: UTF-8 Support's extent?

Paul-Kenji Cahier wrote: > Sorry to be possibly intruding here... But with 1.5.25-11 and > both LC_CTYPE=C-UTF-8 CYGWIN=codepage:utf8 a simple command > like ls only seems to be displaying in the locale codepage... > Am I doing something wrong or is the support still limited? The part you're miss

Re: utf-8 and cygwin

Hi Mariusz, On Mon, Nov 26, 2007 at 12:22:41PM -0800, Mariusz Wodzicki wrote: > Microsoft's command 'dir /x' does that, for example. cygpath can perhaps help you (check man cygpath, or cygpath --help). For example executing: $ cygpath -d /cygdrive/c/Program\ Files/Internet\ Explorer/ yields: c

Re: utf-8 and cygwin

Corinna! I would love to help you but I am not competent! What about my other question: how does one find the "short" name of file(s) and folder(s) in cygwin? Microsoft's command 'dir /x' does that, for example. Regards, Mariusz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simp

Re: utf-8 and cygwin

On Nov 25 02:46, Mariusz Wodzicki wrote: > I would like to reopen the discussion about utf-8 support in cygwin. I'd like to close it again. I'm working on converting Cygwin's path handling to use NT's unicode functions. Given that there's practically no coding help from anybody, this will take m

Re: utf-8 and cygwin

On Sun, 25 Nov 2007 20:03:07 -0500, "Larry Hall" wrote: > > Mariusz Wodzicki wrote: > > > > I would like to reopen the discussion about utf-8 support in cygwin. > > > > SIXTEEN months passed since there were some exchanges about it > > on the cygwin mail list. > > > > The lack of support for

Re: utf-8 and cygwin

Mariusz Wodzicki wrote: I would like to reopen the discussion about utf-8 support in cygwin. SIXTEEN months passed since there were some exchanges about it on the cygwin mail list. The lack of support for filenames with non-Latin1 characters is currently the MOST SEVERE LIMITATION of cygwin in

Re: UTF-8 Cygwin

On Wed, Aug 16, 2006 at 04:40:59PM -0300, Paulo Castro wrote: >I would like to ask that the decision to reject Mr Suzuki Hisao's patch >to include UTF-8 file name support in Cygwin was reconsidered. I've >read the discussion between Mr Suzuki Hisao and Mr Christopher Faylor >(cygwin-patches mail l

Re: UTF-8 Cygwin

Hello. I would like to ask that the decision to reject Mr Suzuki Hisao's patch to include UTF-8 file name support in Cygwin was reconsidered. I've read the discussion between Mr Suzuki Hisao and Mr Christopher Faylor (cygwin-patches mail list, thread "UTF-8 Cygwin", 26 Jun - 06 Jul 2006), and Chri

Re: UTF-8 Cygwin

Based on Cygwin 1.5.20-1, I have updated the UTF-8 patch, which modifies filename handling and console I/O to support UTF-8 encoding. In fact, I have just "diff -c"'ed the old ones and have patch'ed the results to cygwin-1.5.20-1-src, except for sys_wcstombs() in miscfuncs.cc. Its definition diff

Re: UTF-8 Cygwin

On Mon, 26 Jun 2006, Linda Walsh wrote: > Christopher Faylor wrote: > > On Tue, Jun 06, 2006 at 02:24:29PM -0700, Linda Walsh wrote: > > > > > SUZUKI Hisao wrote: > > > > > > > I made a patch to cygwin1.dll to support UTF-8. > > > > It allows you to use all of characters and file (or path) names >

Re: UTF-8 Cygwin

Christopher Faylor wrote: On Tue, Jun 06, 2006 at 02:24:29PM -0700, Linda Walsh wrote: SUZUKI Hisao wrote: I made a patch to cygwin1.dll to support UTF-8. It allows you to use all of characters and file (or path) names allowed in Windows, while keeping binary-compatibility with the curr

Re: UTF-8 Cygwin

On Tue, Jun 06, 2006 at 02:24:29PM -0700, Linda Walsh wrote: >SUZUKI Hisao wrote: >>I made a patch to cygwin1.dll to support UTF-8. >> >>It allows you to use all of characters and file (or path) names >>allowed in Windows, while keeping binary-compatibility with the >>current Cygwin. It is fairly

Re: UTF-8 Cygwin

When will we see this in the main-stream cygwin? Soon? :-) linda SUZUKI Hisao wrote: I made a patch to cygwin1.dll to support UTF-8. It allows you to use all of characters and file (or path) names allowed in Windows, while keeping binary-compatibility with the current Cygwin. It is fairly perf

Re: UTF-8 Cygwin

SUZUKI Hisao wrote: > I made a patch to cygwin1.dll to support UTF-8. > > It allows you to use all of characters and file (or path) names > allowed in Windows, while keeping binary-compatibility with the > current Cygwin. It is fairly perfect except for lack of locale > support etc. So it may re

RE: utf-8

, Rajat Bawa -Original Message- From: Corinna Vinschen [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 30, 2002 5:45 PM To: [EMAIL PROTECTED] Subject: Re: utf-8 On Wed, Jan 30, 2002 at 03:39:15PM +0530, Rajat Bawa wrote: > > Why is cygwin not able to handle utf-8 data files .. any idea

Re: utf-8

On Wed, Jan 30, 2002 at 03:39:15PM +0530, Rajat Bawa wrote: > > Why is cygwin not able to handle utf-8 data files .. any idea ?? Sure. Nobody contributed code for it. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer