Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-62
Corinna Vinschen wrote: On Oct 6 17:02, Andy Koppe wrote: 2009/10/6 Ken Brown: I've tried to view the attached file (extracted from the output of fc-list) in various ways, and here's what I've found (running XP in the U.S., with no language-related customization): - Using emacs under X, emacs recognizes the file as UTF-8 and displays the foreign characters correctly. - 'cat temp.txt' in the cygwin console produces lots of question marks. You probably need to select a Unicode-enabled font in the console's properties, e.g. Lucida Console. Uh, right. I forgot the font problem. I'm also using Lucida Console in the console, usually. It should be possible (and should be done then) to pre-configure at least the Cygwin desktop link to use Lucida Console. (And maybe an option to mkshorcut for this purpose would be useful, too.) Don't know whether it's possible to select the font from within cygwin.bat, though. Thomas -- 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
Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-62
Thomas Wolff wrote: It should be possible (and should be done then) to pre-configure at least the Cygwin desktop link to use Lucida Console. It does not appear that the extended panels in the cmd.exe shortcut properties are available programmatically [*] The best I found was some utility code that uses undocumented win32 apis to change console properties like Font at runtime: http://www.catch22.net/sites/default/source/files/setconsoleinfo.c (On Vista, you can use SetConsoleScreenBufferEx -- which is supposedly documented but I couldn't find any). However, our w32 import libraries don't include these functions, so it might have to use GetProcAddress to access them. In any case, even if you got these solutions to work, the best they could offer is that we could write a utility program, and set things up in cygwin.bat so that the utility is called. [*] Maybe. It's possible that there is some generic Properties accessor for the ShellLink object, and you could manually peruse the them on an existing, generic cmd.exe shortcut, and you might discover some nifty item that we could modify. But I don't plan on doing that reverse-engineering effort. (And maybe an option to mkshorcut for this purpose would be useful, too.) Don't know whether it's possible to select the font from within cygwin.bat, though. See above. FYI: I discovered that the Consolas font is available for download on non-Vista: http://www.microsoft.com/downloads/details.aspx?familyid=22e69ae4-7e40-4807-8a86-b3d36fab68d3displaylang=en or here: http://www.microsoft.com/downloads/details.aspx?FamilyId=428D5727-43AB-4F24-90B7-A94784AF71A4displaylang=en Then, by following the steps here: http://support.microsoft.com/kb/247815 You can add it to the list of fonts that cmd.exe can use (Windows 7 and Windows Server 2008 R2 already allow this by default). It shows up in the Properties menu immediately, but it has no effect if you select it, until you reboot. It's quite similar to Lucida Console, but a little more appealing character shape (yeah, I'm a font snob). The zero has a slash through it, which is nice, but unfortunately -- unlike Lucida Console -- the lowercase l is more similar to the numeral one than it ought to be. It looks like crap unless you have ClearType turned on, but pretty good if you do. Overall, I think I like it better than Lucida Console -- except that: [1.7]$ LANG=C.CP437 ascii shows the line-draw characters if you're using Lucida Console in a cmd.exe window, but doesn't if you're using Consolas. Similarly: [1.7]$ LANG=C.CP437 /usr/lib/ncurses/test/ncurses.exe -- Chuck -- 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
Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-62
2009/10/7 Charles Wilson: (On Vista, you can use SetConsoleScreenBufferEx -- which is supposedly documented but I couldn't find any). There's a 'SetConsoleScreenBufferInfoEx'. But another one looks more interesting: 'SetCurrentConsoleFontEx' (also ≥Vista). 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
Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-62
On 10/3/2009 9:59 AM, Corinna Vinschen wrote: Apart from bugfixes, this patch contains a change to the internationalization efforts in Cygwin which cristalized out of a couple of longish discussions on the cygwin and cygwin-developer lists. Here's how it's supposed to work in future: [...] - The C locale's default charset is UTF-8. Does this mean that non-ASCII characters are supposed to display OOTB, or is some user configuration expected? Here's a test case. I've tried to view the attached file (extracted from the output of fc-list) in various ways, and here's what I've found (running XP in the U.S., with no language-related customization): - Using emacs under X, emacs recognizes the file as UTF-8 and displays the foreign characters correctly. - 'cat temp.txt' in the cygwin console produces lots of question marks. - 'cat temp.txt' in xterm or mintty produces lots of garbage. The garbage changes in mintty if I change the choice of codepage in the options, but I haven't been able to get rid of the garbage. - If I set LANG=C.UTF-8 before starting xterm, I get correct display of the foreign characters as in emacs (under X). But this doesn't seem to work for the cygwin console or mintty (or at least I haven't figured out how to make it work). Ken P.S. This post is related to the discussion started in http://cygwin.com/ml/cygwin-developers/2009-10/msg00062.html. But I'm approaching the question as a user, so I didn't think I should reply there. (I'm not subscribed anyway.) obyÄejné Îανονικά Normál ÐбÑÑнÑй Normálne -- 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
Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-62
2009/10/6 Ken Brown: I've tried to view the attached file (extracted from the output of fc-list) in various ways, and here's what I've found (running XP in the U.S., with no language-related customization): - Using emacs under X, emacs recognizes the file as UTF-8 and displays the foreign characters correctly. - 'cat temp.txt' in the cygwin console produces lots of question marks. You probably need to select a Unicode-enabled font in the console's properties, e.g. Lucida Console. - 'cat temp.txt' in xterm or mintty produces lots of garbage. The garbage changes in mintty if I change the choice of codepage in the options, but I haven't been able to get rid of the garbage. It should be fine if you set the charset to UTF-8 and rerun the command. Again, you also need to select a suitable font. - If I set LANG=C.UTF-8 before starting xterm, I get correct display of the foreign characters as in emacs (under X). But this doesn't seem to work for the cygwin console or mintty (or at least I haven't figured out how to make it work). mintty-0.4.4 ignores the locale variables, but that's changing in 0.5. 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
Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-62
On Oct 6 11:32, Ken Brown wrote: On 10/3/2009 9:59 AM, Corinna Vinschen wrote: Apart from bugfixes, this patch contains a change to the internationalization efforts in Cygwin which cristalized out of a couple of longish discussions on the cygwin and cygwin-developer lists. Here's how it's supposed to work in future: [...] - The C locale's default charset is UTF-8. Does this mean that non-ASCII characters are supposed to display OOTB, or is some user configuration expected? Here's a test case. I've tried to view the attached file (extracted from the output of fc-list) in various ways, and here's what I've found (running XP in the U.S., with no language-related customization): - Using emacs under X, emacs recognizes the file as UTF-8 and displays the foreign characters correctly. - 'cat temp.txt' in the cygwin console produces lots of question marks. I don't understand this. Are you sure you're running the latest -62 release? Without any environment setting (LC_ALL, LC_CTYPE, LANG), the console is using UTF-8 by default, just like anything else. If I call `cat temp.txt', I get a selection of the finest native characters (looks like a mix of eastern european umlauts, greek, and russian). With vim, I get a few weird characters which appears to be related to the fact that vim doesn't really recognize the file as UTF-8. As soon as I set $LANG to (for instance) C.UTF-8, vim is happy as well. Alternatively, `:set encoding=utf-8' in vim is sufficent as well. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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
Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-62
On Oct 6 17:02, Andy Koppe wrote: 2009/10/6 Ken Brown: I've tried to view the attached file (extracted from the output of fc-list) in various ways, and here's what I've found (running XP in the U.S., with no language-related customization): - Using emacs under X, emacs recognizes the file as UTF-8 and displays the foreign characters correctly. - 'cat temp.txt' in the cygwin console produces lots of question marks. You probably need to select a Unicode-enabled font in the console's properties, e.g. Lucida Console. Uh, right. I forgot the font problem. I'm also using Lucida Console in the console, usually. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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
Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-62
On 10/6/2009 12:02 PM, Andy Koppe wrote: 2009/10/6 Ken Brown: I've tried to view the attached file (extracted from the output of fc-list) in various ways, and here's what I've found (running XP in the U.S., with no language-related customization): - Using emacs under X, emacs recognizes the file as UTF-8 and displays the foreign characters correctly. - 'cat temp.txt' in the cygwin console produces lots of question marks. You probably need to select a Unicode-enabled font in the console's properties, e.g. Lucida Console. Thanks. That was the problem. Ken -- 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
[ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-62
Hi folks, I just uploaded a new Cygwin 1.7 test release, 1.7.0-62. Apart from bugfixes, this patch contains a change to the internationalization efforts in Cygwin which cristalized out of a couple of longish discussions on the cygwin and cygwin-developer lists. Here's how it's supposed to work in future: - UTF-8 rules. - System objects will always be *initially* translated using UTF-8. This includes file names, user names, and initial environment variables. This is also the rule for the consile window. - By setting the locale environ variables you can switch the charset used in subsequent child processes in the console, as well as to translate filenames and other system objects. The conversions in the current process are not affected by this. Only the setting at process startup are binding. This is only a stop-gap measure, to allow to re-use old archives or scripts. Those should be converted to UTF-8 ASAP! - Consequentially, setlocale() calls in a process have only an effect on the process code itself, not on the system object conversions within Cygwin and in the console window. - The C locale's default charset is UTF-8. - Additionally there are now language-neutral C.charset locales (C.CP1252, C.EUCJP, etc). - The user's ANSI codepage remain the default charset for language and language_TERRITORY locales. - Due to potential collision problems, the special filename conversion of characters which are not available in the current character set is now prepended with a Ctrl-X character, rather than Ctrl-N. I fixed the documentation in the user's guide accordingly: http://cygwin.com/1.7/cygwin-ug-net/setup-locale.html http://cygwin.com/1.7/cygwin-ug-net/using-specialnames.html#pathnames-unusual Other changes: = - Stop faking hardlinks on filesystems not supporting them (FAT, FAT32) by copying the file. Instead, the link(2) function returns EPERM, just as on Linux. - Improve multibyte to widechar conversion and vice versa. Bugfixes: = - Fix a typo in the extended attributes handling to support the setxattr call not only on Samba. - Fix a few problems in signal handling. - More workaround an issue with crashes due to invalid references to malloc functions when loading DLLs built against test versions of Cygwin between 1.7.0-49 and 1.7.0-57. - Fix error handling in a couple of file-related functions. - Avoid a failing recv function when trying to receive data on a socket connected via a child process. This works around a WinSock bug. - Fix a bug which disallowed to mq_open the smae message queue in different processes. - Declare getpagesize correctly as int per POSIX. FAQ: - Q: How do I know that I'm running Cygwin 1.7.0-62? A: The `uname -v' command prints 2009-10-03 14:33 Have fun, Corinna *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=3d3dyourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://cygwin.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:cygwin@cygwin.com Red Hat, Inc. -- 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
Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-62
What does all of these means for users converting from cygwin 1.5? Do we have to change anything we are doing today? I live in the good-ole US, speak/understanding english. Did my ancesters get on the wrong boat? Corinna Vinschen wrote: Hi folks, I just uploaded a new Cygwin 1.7 test release, 1.7.0-62. Apart from bugfixes, this patch contains a change to the internationalization efforts in Cygwin which cristalized out of a couple of longish discussions on the cygwin and cygwin-developer lists. Here's how it's supposed to work in future: - UTF-8 rules. - System objects will always be *initially* translated using UTF-8. This includes file names, user names, and initial environment variables. This is also the rule for the consile window. - By setting the locale environ variables you can switch the charset used in subsequent child processes in the console, as well as to translate filenames and other system objects. The conversions in the current process are not affected by this. Only the setting at process startup are binding. This is only a stop-gap measure, to allow to re-use old archives or scripts. Those should be converted to UTF-8 ASAP! - Consequentially, setlocale() calls in a process have only an effect on the process code itself, not on the system object conversions within Cygwin and in the console window. - The C locale's default charset is UTF-8. - Additionally there are now language-neutral C.charset locales (C.CP1252, C.EUCJP, etc). - The user's ANSI codepage remain the default charset for language and language_TERRITORY locales. - Due to potential collision problems, the special filename conversion of characters which are not available in the current character set is now prepended with a Ctrl-X character, rather than Ctrl-N. I fixed the documentation in the user's guide accordingly: http://cygwin.com/1.7/cygwin-ug-net/setup-locale.html http://cygwin.com/1.7/cygwin-ug-net/using-specialnames.html#pathnames-unusual Other changes: = - Stop faking hardlinks on filesystems not supporting them (FAT, FAT32) by copying the file. Instead, the link(2) function returns EPERM, just as on Linux. - Improve multibyte to widechar conversion and vice versa. Bugfixes: = - Fix a typo in the extended attributes handling to support the setxattr call not only on Samba. - Fix a few problems in signal handling. - More workaround an issue with crashes due to invalid references to malloc functions when loading DLLs built against test versions of Cygwin between 1.7.0-49 and 1.7.0-57. - Fix error handling in a couple of file-related functions. - Avoid a failing recv function when trying to receive data on a socket connected via a child process. This works around a WinSock bug. - Fix a bug which disallowed to mq_open the smae message queue in different processes. - Declare getpagesize correctly as int per POSIX. FAQ: - Q: How do I know that I'm running Cygwin 1.7.0-62? A: The `uname -v' command prints 2009-10-03 14:33 Have fun, Corinna *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=3d3dyourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://cygwin.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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
Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-62
Paul McFerrin wrote: What does all of these means for users converting from cygwin 1.5? Do we have to change anything we are doing today? I live in the good-ole US, speak/understanding english. Did my ancesters get on the wrong boat? They sure got on the i-don't-know-how-to-trim-my-email-quotes boat! In practical terms, if you're just using plain English ASCII stuff, you won't need to change anything. cheers, DaveK -- 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
