35665 - add support for microsoft-cp1251 to Unix font engine

Status: VERIFIED FIXED

(Core :: Layout, defect, P3)

Description

[Erik van der Poel]

Date: Thu, 13 Apr 2000 01:16:46 +0400
From: "Alexander Voropay" <[e-mail]>

Erik van der Poel <[e-mail]> 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 <[e-mail]>
To: [e-mail] <[e-mail]>
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=-

Comment 1

[Erik van der Poel]

Added.

Comment 2

[Chris Petersen]

Marking verified per last comments.