[Fonts]Can't input Lao
Hi guys, It wasn't success in try to input Lao in any of the KDE applications. I was able to type Thai and Hebrew using MS Arial and Misc fonts. Here is what I have done: 1. Created Lao keyboard layout and put it in .../xkb/symbols and named named lo for Lao language 2. Addedlo Lao to the xfree86.lst file 3. added Lao keymaps information in the ../xkb/keymap I also installed BDF fonts from Mark Kuhn's website which included lao. Anything else that I need to do here? Any suggestions? Thanks Sak ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]Question on xft font library.
Keith, thanks for your patient to answer these!! > > 1. It seems that XFT is so good, so what's about the conventional fonts > > module inside X, like the xtt, freetype, type1, etc... > > The X server can still provide fonts for applications not yet ported to > Xft. These modules will be useful as long as you have some older > applications left around. Do you mean that, these two module is stable enough, and no active development works is carried on these? > > 3. If I want to use XFT, should I use DRI modules?? > > The older Xft did require the Render extension, but all XFree86-based X > servers have provided that for over a year now, including those built from > sources directly from the DRI project. > > The new Xft (not yet released, but in CVS) doesn't even need Render and > will work on any X server. I have heard something about Xft2, I even get a copy of it from somewhere, I forget, but it is binary. I remember that, I can't find the source from that site. Anyway, what's the version of Xft which is considered latest, and what's the version included in XFree86-4.2? I also heard about fontconfig, by the paper on you web site, but is it include in XFree4.2? Again, what's the current version. May I have some more references relating to fontconfig? Though, I know that these two libraries (Xft, and fontconfig) is develop and maintain by Keith, but does it have a official website, or these two library won't have a website due to the fact that, it is under XFree?? > > 6. In xtt, the ttcap functions is useful for chinese fonts (I am a > > Chinese), however, does freetype provide this, or xft provide this?? > > > > 7. If similar functions of ttcap is not available in xft and freetype > > currently, will it been in the todo list later. > > ttcap isn't relevant for Xft. Xft provides full support for all TrueType > and Type1 fonts, and has some special support for Han languages to ensure > that the right fonts are used in each locale. Xft supports a large number > of rendering configuration options for fonts. The subsetting options > aren't relevant as Xft always incrementally rasterizes fonts. Does "incrementally rasterizes fonts" means, the cache mechanism for inside Xft, ie. Xft will only rasterizes glyphs on demand, right? but I don't understand, why those subsetting options aren't releveant for Xft. IMHO, I just think that, to handle such functionality, I can add these function within freetype, or do something else on top of it. For the fontconfig, and Xft, as these two is responsible for the query fonts, and get glyphs, and render it on X. It should handle the case that, alias a font with regular face to italic or bold, also, get the desired glyphs (transformed) for the client application. Does my logic right, or stupid ?? I want to this answer as this direction is right, as Gnome and Kde is shifting to use Xft, enable the function (bold/italic transformation) would benefit more than any other possible solution. Sorry for my long and a little bit stupid question, as I am new to this field, I am working very hard on studying more material relating to these issue : ) Zenith ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]XFree86 Lao Supports??
Hi Pablo, Thanks for your info..but I still need to clarify the following info: You said: I don't know if Lao keyboard is similar to Thai keyboard or not; if it is, you can start looking at /usr/X11R6/lib/X11/xkb/symbols/th copy it under another name (eg: "lo") and edit it. Thai has symbolic keysyms, as its support was integrated long ago in XFree86, before unicode support. Yes, I did look in the directory where the files are. Thai and Lao are very similar. Tell me what is sybolic keysyms and you said that Thai has integrated into Xfree86. It is the one that I am doing for Lao called kayboard mapping is the 'symbolic keysyms'?? You said: Then, you just need to use an UTF-8 locale, and load your created keyboard. And make your unicode font available as *-iso10646-1 and use it. My question: Where can I find UTF-8 locale?? How do I go about making unicode font available as *-iso10646-1? By the way it is the same as specifying the true type fonts?? Thanks! Sak S. Kaixo! On Thu, Jul 18, 2002 at 10:14:39AM -0400, Anthony Souphavanh wrote: > I am new to the group. I work on Lao Keyboard mapping for XFree86 version > 4.0. I am asking for your kind suggestions as to where to start. I You need to write a keyboard definition using the "unicode keysyms" for the Lao letters. "unicode keysyms" are X11 keysyms of the form 0x100 with replaced with the hexa value of the unicode char you want. I don't know if Lao keyboard is similar to Thai keyboard or not; if it is, you can start looking at /usr/X11R6/lib/X11/xkb/symbols/th copy it under another name (eg: "lo") and edit it. Thai has symbolic keysyms, as its support was integrated long ago in XFree86, before unicode support. > 2. Be able to use Lao UNICODE font under MS Arial UNICODE via XFree86 Lao > input method Then, you just need to use an UTF-8 locale, and load your created keyboard. And make your unicode font available as *-iso10646-1 and use it. > Use #2 to tranlstate or work on Lao KDE version 3.x.x Gtk2 (Gnome) and Qt3 (KDE) have even better mechanisms to handle and display some complex scripts, like Thai, and I suppose Lao works similarly. Now, to know if Lao support has explicitely been developped yet or not you should ask on gtk/gnome/kde mailing-lists. > Any suggestions would greatly be appreciated. > > Thank you, > > Anousak S. > > > > ___ > Fonts mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/fonts -- Ki ça vos våye bén, Pablo Saratxaga http://chanae.stben.be/pablo/ PGP Key available, key ID: 0xD9B85466 [you can write me in Walloon, Spanish, French, English, Italian or Portuguese] ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]Font family name problem
Kaixo! On Thu, Jul 18, 2002 at 10:12:05AM -0700, Keith Packard wrote: > > Around 13 o'clock on Jul 18, Pablo Saratxaga wrote: > > > In other terms, the localized names are used to display in the lists shown > > to the user, when when one of those is choosen, what is returned is not the > > localized name but the ascii-only one. And inversly, when an ascii-only > > name is gotten, it should be possible to retrieve its associated localized > > name if needed. > > Why do you believe the internal interface should only use ASCII names? Not necessarly ASCII names, but unique and locale independent ones. So if a document which embedds fotn names is open under a different locale nothing strange happens. > Note that *all* of these names are locale independent; applications can > use any of the names to access the font, the only question is what name > should be returned when the application requests it, the mapping from the > set of names to a name appropriate for the user is the only locale > -dependent step. Ok then, so it's ok. -- Ki ça vos våye bén, Pablo Saratxaga http://chanae.stben.be/pablo/ PGP Key available, key ID: 0xD9B85466 [you can write me in Walloon, Spanish, French, English, Italian or Portuguese] msg00984/pgp0.pgp Description: PGP signature
Re: [Fonts]Font family name problem
Around 13 o'clock on Jul 18, Pablo Saratxaga wrote: > In other terms, the localized names are used to display in the lists shown > to the user, when when one of those is choosen, what is returned is not the > localized name but the ascii-only one. And inversly, when an ascii-only > name is gotten, it should be possible to retrieve its associated localized > name if needed. Why do you believe the internal interface should only use ASCII names? The underlying infrastructure supports fonts with multiple names, it seems obvious to me that it will be easier to get application support if they need deal with only one name, and that name should be the localized name. Note that *all* of these names are locale independent; applications can use any of the names to access the font, the only question is what name should be returned when the application requests it, the mapping from the set of names to a name appropriate for the user is the only locale -dependent step. Keith PackardXFree86 Core TeamHP Cambridge Research Lab ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]XFree86 Lao Supports??
Kaixo! On Thu, Jul 18, 2002 at 10:14:39AM -0400, Anthony Souphavanh wrote: > I am new to the group. I work on Lao Keyboard mapping for XFree86 version > 4.0. I am asking for your kind suggestions as to where to start. I You need to write a keyboard definition using the "unicode keysyms" for the Lao letters. "unicode keysyms" are X11 keysyms of the form 0x100 with replaced with the hexa value of the unicode char you want. I don't know if Lao keyboard is similar to Thai keyboard or not; if it is, you can start looking at /usr/X11R6/lib/X11/xkb/symbols/th copy it under another name (eg: "lo") and edit it. Thai has symbolic keysyms, as its support was integrated long ago in XFree86, before unicode support. > 2. Be able to use Lao UNICODE font under MS Arial UNICODE via XFree86 Lao > input method Then, you just need to use an UTF-8 locale, and load your created keyboard. And make your unicode font available as *-iso10646-1 and use it. > Use #2 to tranlstate or work on Lao KDE version 3.x.x Gtk2 (Gnome) and Qt3 (KDE) have even better mechanisms to handle and display some complex scripts, like Thai, and I suppose Lao works similarly. Now, to know if Lao support has explicitely been developped yet or not you should ask on gtk/gnome/kde mailing-lists. > Any suggestions would greatly be appreciated. > > Thank you, > > Anousak S. > > > > ___ > Fonts mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/fonts -- Ki ça vos våye bén, Pablo Saratxaga http://chanae.stben.be/pablo/ PGP Key available, key ID: 0xD9B85466 [you can write me in Walloon, Spanish, French, English, Italian or Portuguese] msg00982/pgp0.pgp Description: PGP signature
[Fonts]XFree86 Lao Supports??
Hi! I am new to the group. I work on Lao Keyboard mapping for XFree86 version 4.0. I am asking for your kind suggestions as to where to start. I installed SUSE on AMD based machine and trying to type different language by switching keyboard from KDE Control Manager. My goals are as follow: 1. Complete Lao Keyboard mapping and to be archived on XFree86.org 2. Be able to use Lao UNICODE font under MS Arial UNICODE via XFree86 Lao input method Use #2 to tranlstate or work on Lao KDE version 3.x.x Any suggestions would greatly be appreciated. Thank you, Anousak S. ___ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
Re: [Fonts]Font family name problem
Kaixo! On Wed, Jul 17, 2002 at 06:26:47PM -0700, Keith Packard wrote: > Ok, I'm adding localized names to fontconfig. To allow applications to > continue working with a single name, I'm actually listing the localized > names in the FC_FAMILY value using a new datatype (FcTypeLangString). > Ask for a string, and you'll get back just the family name, but ask for a > LangString and you'll get both. What you mlean by "both" ? Users should see only one name for each font; but that name should be, if exists, the localized one. Then, for programs internally, a unique name (the ascii-only one) be used. In other terms, the localized names are used to display in the lists shown to the user, when when one of those is choosen, what is returned is not the localized name but the ascii-only one. And inversly, when an ascii-only name is gotten, it should be possible to retrieve its associated localized name if needed. The localized lists shoumld be a list of 2-tuples: (ascii-name, localized-name) one used for display, and the other used for the return value in case it is chosen. > A couple of questions: > 2) Should I use the current locale to select a family from those > listed when an application requests a string for FC_FAMILY? yes. (well, it may be interesting to have a possibility to explicitelly tell a given language; but in the general case the current locale should be used, it should follow the same rules as for translations of programs interfaces and menus imho). > That would mean returning different values depending on the > locale. Of course, that is the purpose. And that is why a unique ascii-only value should always be associated with them, so programs can use that unique and locale-independent value; and users see the locale dependent value. It should be seen and handled in a way similar to the localization of programs interfaces; with the difference that translations are not handled trought gettext bu embedded in the fonts and should be handled by a specific api. -- Ki ça vos våye bén, Pablo Saratxaga http://chanae.stben.be/pablo/ PGP Key available, key ID: 0xD9B85466 [you can write me in Walloon, Spanish, French, English, Italian or Portuguese] msg00980/pgp0.pgp Description: PGP signature
