Hi, Thanks both for your very informative answers.
The system I am using is solaris 10. There is no Xorg on it and I am using Xvfb which means XSun with vfb. Is there any patch which gets me the "encoding file" for iso10646. Also I don't find any -unicode-fontspecific fonts, the only fonts i have coming in xlsfonts are sun-fontspecific, adobe-fontspecific. I just wanted to know how can I make unicode truetype fonts display, the X server seems to have the fonts loaded but the XLoadQueryFont opens iso8859-1 fonts. Do i have to run font server for true type fonts or just place the mapping files or patch the x server or load unicode-fontspecific fonts? I would be really thankful if you can point out something concrete which solves this problem i am facing with solaris system. Regards, Raja On Wed, Jun 17, 2009 at 2:41 AM, Suresh Chandrasekharan<Suresh.Chandrasekharan at sun.com> wrote: > Hi, > ? Could you clarify the environment you're running ? Try installing the > ttf-fonts-core package from opensolaris extra repo at > https://pkg.sun.com/opensolaris/extra (needs registration) which gives the > Ascender font with the same XLFD as the *-courier-* you're mentioning and it > works for me when loading in xfd/xterm etc.) > > Also tried a simple XLoadQueryFont app to check if that worked and it did > not give any issues for me. > > (In the old Xsun days, instead of being dependent on iso10646-1 we were > using XCreateFontSet in place of XLoadQueryFont to create a composite > Unicode fonts which were mostly used in CDE/X applications for font Unicode > range coverage. -unicode-fontspecific wasn't a iso10646-1 replacement, but > unicode fonts which have some of the private area mapped with characters and > it was more of a private encoding) > > Regards, > Suresh > > Alan Coopersmith wrote: >> >> rui wrote: >> >>> >>> Hi, >>> >>> I am facing this problem with XSun on opensolaris where I am trying to >>> load a XLFD font using XLoadQueryFont. >>> >> >> If it has Xsun, it cannot be OpenSolaris - OpenSolaris does not include >> Xsun, >> only Xorg, as Xsun is neither open source nor freely redistributable due >> to >> third-party closed source code in it. >> >> >>> >>> The font i am trying to load is -*-courier >>> new-medium-r-*--13-91-*-*-*-*-iso10646-1 and the font which gets loaded is >>> -Misc-Fixed-Medium-R-Normal--15-140-75-75-C-90-ISO8859-1 >>> >>> I also get this error on the output window >>> "Cannot find encoding file for iso10646-1" >>> >>> However this error doesn't occur on the suse linux server. >>> >>> I have copied courier new fonts from windows and they are properly added >>> to font path -- xlsfonts shows them as loaded: >>> /usr/openwin/bin/xlsfonts -display :0 | grep iso10646 >>> -monotype-courier new-bold-i-normal--0-0-0-0-m-0-iso10646-1 >>> -monotype-courier new-bold-r-normal--0-0-0-0-m-0-iso10646-1 >>> -monotype-courier new-medium-i-normal--0-0-0-0-m-0-iso10646-1 >>> -monotype-courier new-medium-r-normal--0-0-0-0-m-0-iso10646-1 >>> >>> How can i load the encoding file for iso10646, i had a look on suse linux >>> as well as solaris, there are files present in /usr/X11/lib/X11/fonts/ and >>> /usr/openwin/lib/X11/fonts with the name of encodings.dir pointing to *.enc >>> files and also on solaris in truetype directory there is a folder called >>> ttmap with files of *.ttmap extension. >>> I have also made sure that there is no file by the name and content of >>> iso10646 on both systems but why doesn't suse linux doesn't complain? >>> >> >> The ttmaps files are used by Xsun, the encodings files by Xorg. ? From a >> quick >> peek in the libfontenc source used by Xorg to read those encodings files, >> it >> seems that it handles "iso10646-1" internally, since the encoding files >> map >> other character set encodings to unicode, and there is no mapping table >> needed >> to map unicode to itself. >> >> >>> >>> The main directories are all added to the fontpath of xserver. >>> >>> What can be the problem with not finding encoding file for iso10646? >>> Is there a way through xlib api or anyway that I can find the encoding >>> file being used by a font, so that I can provide the same file as on suse to >>> sun solaris? >>> >> >> I don't think the Xsun server supports the 10646-1 encoding - I don't >> remember >> what it used for the Unicode encoding name, so I've cc'ed i18n-discuss >> where >> the internationalization experts may know. ? (I do see some fonts listing >> an >> '-unicode-fontspecific' encoding in old Xsun fonts.dir files, but am not >> sure >> if that's correct or not.) >> >> > >
