[prev] [thread] [next] [lurker] [Date index for 2004/08/24]
--Sw7tCqrGA+HQ0/zt Content-Type: text/plain; charset=windows-1251 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 23, 2004 at 10:53:56AM -0500, Peter da Silva wrote: > So, do all these flags really turn off the "expression ?: expression" klu= dge? Not quite: gcc -pedantic outputs a warning, and of course, adding -Werror would treat this as a fatal error. However, there is no way that I can see of making gcc treat this particular construct as an error without a blanket -Werror. > [Secondary hate, mail clients that pay attention to charset interacting > with mail clients that take the golden rule to an absurd level by > ignoring charset on input and selecting some weird platform-specific > charset on output. Why would an application on an OS that has Unicode > built in to it at a low level send messages in Windows-1251 or whatever?] I'm not sure what exactly you are implying here - or which particular mail client / message is your hate targeted at. However, if it is my previous message (and consequently this one too), it's not the fault of the Redmond OS, but rather of the dreadful lack of standardization of Cyrillic character sets. This is worthy of a hate rant itself, but I'll sketch it here. This particular character set is now the de facto standard for Cyrillic communications (maybe outside Russia and Ukraine, some of which still stick to koi8-r and koi8-u). In the past couple of years, I've seen web browsers and e-mail clients use all kinds of wacky names for it - just 1251, cp1251, window-1251, win-1251, microsoft-1251 cyrillic-1251, cyr1251, and all their variations with capitalization and with/without a dash between the word and the number. IMHO, CP1251 or cp1251 sounds best, but unfortunately, there seems to have been a convergence at some point and now the majority of MIME clients like windows-1251 better. I've been toying for some time with the idea of hacking up a minimal charset detector, which reads a piece of text and determines whether it should really be marked up as windows-1251 or us-ascii will be enough. If someone knows of something that already does this and can be easily hooked into Mutt, please holler. Until then, I'm afraid that since my e-mail communication is pretty much equally split between messages in Bulgarian and English, windows-1251 it is. G'luck, Peter --=20 Peter Pentchev roam@xxxxxxx.xxx roam@xxxxx.xx roam@xxxxxxx.xxx PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 If I were you, who would be reading this sentence? --Sw7tCqrGA+HQ0/zt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBKyhE7Ri2jRYZRVMRAoOIAJ9M6V6O9FZZOX75zb+XGWYHQFUdxwCeJ694 UBXCd4+W7LSAAcLvOW+hF5Q= =BimV -----END PGP SIGNATURE----- --Sw7tCqrGA+HQ0/zt--There's stuff above here
Generated at 15:00 on 24 Aug 2004 by mariachi 0.52