Date: Thu, 13 Apr 2000 01:16:46 +0400 From: "Alexander Voropay" <firstname.lastname@example.org> Erik van der Poel <email@example.com> wrote : > >Mozilla currently only supports the proper XLFD names with 14 hyphens. > >Mozilla implements the CSS spec. It first looks up the "family" name. >Then it tries each encoding, currently in "hash order". I hope to change >this to the XListFonts order soon, to give more control to users. Could you change the XLFD for Microsoft's "Codepages" : . microsoft - CHARSET_REGISTRY, registration authority that owns specified encoding . cp1251 - CHARSET_ENCODING, registered name that identifies the coded character set as defined by that registration authority ftp://ftp.x.org/pub/R6.3/xc/doc/specs/XLFD/ http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/encodings.html http://www.xfree86.org/4.0/fonts3.html -----Original Message----- From: Juliusz Chroboczek <Juliusz.Chroboczek@ens.fr> To: firstname.lastname@example.org <email@example.com> Subject: Re: xfsft and "microsoft-cp1251" vs "windows-1251" [...] I only sugest using this name for XLFD glyph encodings. I do not suggest using it for any other purpose. AV> Could you point out any standarts for this name ? This was chosen by mutual agreement between me, the X-TT developers, and the Wine developers. It is not standard. AV> Why not "cp1251". Because XLFD glyph encoding names need to be of the form <registry>-<encoding> i.e. two fields separated with a dash (`-'). [...] =========== -- -=AV=-
Status: NEW → ASSIGNED
Target Milestone: --- → M16
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
Marking verified per last comments.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.