[Indic-computing-devel] X vs. Open Type
Status: Alpha
Brought to you by:
jkoshy
From: Tapan S. P. <ta...@ya...> - 2002-02-20 20:14:45
|
> The proposed new algorithm: > > FindPosition(textpos, startx, pixel_width) > // Make a single request to the X Server - this doesn't exist in > // the X protocol yet > nchars = XComputeWidth(textbuf[textpos:end-of-line], startx, pixel_width, > // other args font etc) > > // everything starting from textpos to textpos + nchars is "selected" > Is textbuf supposed to be modified and returned by XComputeWidth? Otherwise it seems with reordering there may be some problems at the boundaries where chars are reordered. Two things I am noticing... 1) My knowledge of X and its design decisions is inadequate. 2) From this inadequate knowledge, it seems to me that the philosophies of Open Type Fonts / True Type Fonts and X may not match so well together, in that the X Server expects clients to send glyph codes, but fonts are maintained server-side (not a big deal if char codes _are_ glyph codes), while in the TTF/OTF world, the font files contain the neccesary information for doing char-glyph mapping. It seems in X both Server and Client would need open type font info (the client for doing char->glyph mapping, the server for doing rfendering, positioning, etc.) Somewhat of a catch-22, or am I missing something? --tapan _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |