fontconfig package updated for Georgian (was: [m17n] Problems with the BPG fonts)

Mike FABIAN <[email protected]>
Newsgroups gmane.linux.suse.m17n
Message-ID <[email protected]>
An updated fontconfig package is available here

ftp://ftp.suse.com/pub/projects/m17n/9.3/i586/fontconfig-2.2.99.20050218-8.1.i586.rpm
ftp://ftp.suse.com/pub/projects/m17n/9.3/i586/fontconfig-devel-2.2.99.20050218-8.1.i586.rpm
ftp://ftp.suse.com/pub/projects/m17n/9.3/src/fontconfig-2.2.99.20050218-8.1.src.rpm
ftp://ftp.suse.com/pub/projects/m17n/9.3/x86_64/fontconfig-2.2.99.20050218-8.1.x86_64.rpm
ftp://ftp.suse.com/pub/projects/m17n/9.3/x86_64/fontconfig-devel-2.2.99.20050218-8.1.x86_64.rpm

It makes "BPG Glaho" the preferred font for "sans-serif", "BPG Chveulebrivi"
the preferred font for "serif" and "BPG Courier" the preferred font
for "monospace" when running in a Georgian locale. I.e.,

    LC_CTYPE=ka_GE.UTF-8 xfd -fa monospace

should give you "BPG Courier".

This works only because I also changed ka.orth with the following
patch:

diff -ru fontconfig-2.2.99.20050218.orig/fc-lang/ka.orth fontconfig-2.2.99.20050218/fc-lang/ka.orth
--- fontconfig-2.2.99.20050218.orig/fc-lang/ka.orth	2004-12-07 02:14:46.000000000 +0100
+++ fontconfig-2.2.99.20050218/fc-lang/ka.orth	2005-05-20 12:42:30.000000000 +0200
@@ -22,9 +22,9 @@
 # PERFORMANCE OF THIS SOFTWARE.
 #
 # Georgian (KA)
-0589	# Armenian full stop (vertsaket)
+# 0589	# Armenian full stop (vertsaket)
 #10a0-10c5	# capital letters, not used in normal writing
-10d0-10f6
+10d0-10f0
 #10f7-10f8	# additional letters for Mingrelian and Svan
 10fb
 #2018	# single quote

Is it really OK to remove U+10f1 -U+10f6 from the requirement because
"BPG Chveulebrivi" doesn't have them or is "BGP Chveulebrivi"
incomplete?

-- 
Mike FABIAN   <[email protected]>   http://www.suse.de/~mfabian



-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.