Re: X11R7.5 and C.UTF-8
Thomas Dickey dickey at his.com writes: This means that characters 0..127 have to be treated as ASCII, but No, it means that portable characters and control characters must be 128. ASCII meets this characteristic, but so does EBCDIC, as well as UTF-8. The C locale also implies that you can manipulate bytes = 128 in the naive manner, so long as you don't care about characters embedded in those bytes. And what do you know - ASCII, EBCDIC, and UTF-8 all meet this property, too. beyond that an implementation can do what it wants. And on Cygwin 1.7, plain C actually does imply UTF-8, which happily is backward-compatible with ASCII. That's an interpretation that so far hasn't been blessed by the standards people. Any discussion of this topic should mention that, as a caveat. Actually, the standards people HAVE spoken - and they agreed with our interpretation. POSIX was INTENTIONALLY written with the intent that a UTF-8 encoding is valid for the C locale, for the same reason that it was written that an EBCDIC encoding is valid for the C locale. These emails from the Austin Group (the folks that write POSIX) are telling: https://www.opengroup.org/sophocles/show_mail.tpl? CALLER=show_archive.tplsource=Llistname=austin-group-lid=12982 https://www.opengroup.org/sophocles/show_mail.tpl? CALLER=show_archive.tplsource=Llistname=austin-group-lid=13012 But they also admitted that there is still more work needed in POSIX to make this intent clearly codified (for example, that control characters must be single bytes 128). -- Eric Blake -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: x-server font setting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 http://cygwin.com/acronyms/#PCYMTWLL - your single line was rather long. According to Ling F. Zhang on 8/7/2007 10:12 PM: I just installed cygwin in order to run fontforge on a Windows machine (while my linux machine is down). But since I am interested in working on font that covers the CJK plane, it is important that I can read text encoded in utf-8 or other non-latin codepage. I know that cygwin doesn't like unicode natively, but is it the same for the x-server? Is it safe to use ttf files from Windows (say, via a symbolic link or actual copy) fonts folder? I'll probably encounter more questions as I slowly get fontforge to display Asian glyphs. Wrong list. This is an X related question, and as such, belongs on the cygwin-xfree list (http://cygwin.com/lists.html). Redirected. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGuUkE84KuGfSFAYARAhPfAJ9jK5Ljm1Ez57zTj1Ms2KM4C/q1vgCeLkI7 SQ7Nkh+GgxcV4juXWZ3kuNw= =chQy -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: cannot open display
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ogogon !!! on 9/9/2006 4:24 AM: Good afternoon, colleagues! I have established CygWin to compile under Windows the program developed in gcc. At compilation of console applications - all OK. All applications, even rather complex, are started and work without remarks. However, any attempt to create the program with GTK+, leads to that at their start there is a message Gtk-WARNING **: cannot open display:. At distribution kit CygWin there is a program gtk-demo.exe. Obviously, it it is guaranteed it is compiled without mistakes. It is not started and also writes Gtk-WARNING **: cannot open display:. Then it is probably an X problem, and you asked the wrong list. Try cygwin-xfree; redirecting accordingly. My OS - WindowsXP Pro (Rus). What do I do incorrectly? Probably forgot to set up X. And also didn't follow these directions: Problem reports: http://cygwin.com/problems.html Including the output of 'cygcheck -svr' as a text attachment would have told us what the real problem was. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFAtnT84KuGfSFAYARAptMAJ9I6SZIelcwaaVdsNbFw/WVdotYjACgxYbG emxh/luTjLE9VRQG193V2l8= =CuEC -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Strange-Dangerous behaviour in Cygwin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Carlo Florendo on 5/8/2005 9:30 PM:
Ooops. Sorry, I've read earlier discussions on this issue just a few
seconds ago by Erik Blake et al. So, it's not an xterm issue. It's a
I spell it Eric.
bug with coreutils not being POSIX compliant. A patch has been
applied. We just have to wait for the next annoucement for coreutils.
Hold on there - the bug in POSIX non-compliance was that before coreutils
patch, `rm -i' accepted y as yes, now CVS coreutils obeys POSIX and
interprets it as a match failure (which has the same effect as typing an
answer interpreted as no). Unfortunately, POSIX requires that if your
terminal settings are strange (such as the ctlecho settings that cgf
mentioned on linux), such that raw editing characters escape the terminal
into the program, that y\bn ('y', BACKSPACE, 'n') be interpreted as yes.
The only way this would be an xterm bug is if the default tty settings of
xterm under cygwin can be changed to improve user experience by making it
less likely that raw backspaces are passed through to the program, rather
than being line edited first.
And my next release of cygwin coreutils-5.3.0-6 will not be CVS coreutils
(with all its recent patches in many other areas as well), but stock 5.3.0
with a minimal subset of CVS patches backported as needed (I plan to wait
until 5.3.1 is released before cygwin officially sees all upstream patches
since 5.3.0, unless someone can convince me of a need for cygwin to track
CVS). That means I will not be changing the yes/no behavior in my next
drop of coreutils. But rest assured that I am tracking CVS changes on my
own machine, to try and make sure that there are no regressions introduced
when 5.3.1 is finally released upstream.
- --
Life is short - so eat dessert first!
Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCf18n84KuGfSFAYARAliCAJ9LHbOYO3swwmsLrqlDff0KMyEY4ACeMzAI
x1/ti+7xCZub+fRYc0Kts6Q=
=wTHd
-END PGP SIGNATURE-
