On Wed, 08 Aug 2007 22:59:01 -0000, Mihai Capotă wrote:
> Let's not forget there's a patch from Microsoft that adds support for
> ș and ț in Windows XP.
Yes, but only for displaying ș and ț, not for generating ș and ț from
keyboard (it is basically a font update, nothing more).
Although a good thing, the update is limited to the most used fonts:
Arial and Times New Roman (for printed documents), Verdana (for web)
and Trebuchet (they said this is for MS Office, but I know that this
also solves a titlebar issue when the user selected desktop appearance
is Windows XP instead of Windows Classic).
Another "problem" is that the font update download *) (not the actual
install) requires genuine validation check, which I doubt it will pass
on many home users. In my opinion this will affect the reading on
web-based forums, but less the e-mail, because most home users
appears to be Yahoo mail users **). The standard Yahoo mail
interface generates broken encoding declaration anyway (it is fixed to
ISO-8859-1) and will ignore the incoming mail encoding declaration
anyway (it treates all incoming mail as ISO-8859-1), so most Yahoo mail
users will see garbage, regardless the cedila or comma story ***).
On Wed, 08 Aug 2007 22:59:01 -0000, Mihai Capotă wrote:
> Let's not forget there's a patch from Microsoft that adds support for
> ș and ț in Windows XP.
Yes, but only for displaying ș and ț, not for generating ș and ț from
keyboard (it is basically a font update, nothing more).
Although a good thing, the update is limited to the most used fonts:
Arial and Times New Roman (for printed documents), Verdana (for web)
and Trebuchet (they said this is for MS Office, but I know that this
also solves a titlebar issue when the user selected desktop appearance
is Windows XP instead of Windows Classic).
Another "problem" is that the font update download *) (not the actual
install) requires genuine validation check, which I doubt it will pass
on many home users. In my opinion this will affect the reading on
web-based forums, but less the e-mail, because most home users
appears to be Yahoo mail users **). The standard Yahoo mail
interface generates broken encoding declaration anyway (it is fixed to
ISO-8859-1) and will ignore the incoming mail encoding declaration
anyway (it treates all incoming mail as ISO-8859-1), so most Yahoo mail
users will see garbage, regardless the cedila or comma story ***).
*) www.microsoft. com/downloads/ details. aspx?FamilyID= 0ec6f335- c3de-44c5- a13d-a1e7cea5dd ea&DisplayLang= en
http://
**) merely my own supposition; comments on this may be required
***) this may change if their new beta interface will become widely
used, which I doubt
Cristi
-- www.secarica. ro/
Cristian Secară
http://