summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorOwen Taylor <otaylor@redhat.com>2000-04-05 00:31:59 +0000
committerOwen Taylor <otaylor@src.gnome.org>2000-04-05 00:31:59 +0000
commit613302136667231bcefd772b419369516eb3bf45 (patch)
tree919ed907f3ca69f79210d0778c65df8bec97d4d0 /TODO
parent52f2e805bf993f711d09ba6fe4972c7f7ee33eae (diff)
downloadpango-613302136667231bcefd772b419369516eb3bf45.tar.gz
Add user data to PangoContext
Tue Apr 4 20:13:06 2000 Owen Taylor <otaylor@redhat.com> * pango/pango-context.h: Add user data to PangoContext * pango/pangox.[ch] examples/viewer.c: Rework system for create GC's so that the necessary information is stored on the PangoContext instead of being passed to layout_render() * pango/utils.[ch] pango/pango-context.c: fribidi-0.1.9 wants UCS-4 not UCS2; switch accordingly. * pango/fonts.c pango/pango-font.h pango/pangox.c: Add functions to get overall font metrics, possibly per-language. (Right now, just font ascent, descent.) The implementation of this for X is horribly complex.
Diffstat (limited to 'TODO')
-rw-r--r--TODO22
1 files changed, 22 insertions, 0 deletions
diff --git a/TODO b/TODO
index ccf4f828..63af5672 100644
--- a/TODO
+++ b/TODO
@@ -38,6 +38,23 @@ X rendering
as we are. There is a bit of fudging in the underline drawing
code to deal with this and make the underlines look symetric.
+* pangox.c/get_font_metrics_from_string() needs to gutted and
+ replaced with using pango_itemize(); to support this, we need
+ the ability to specifiy a particular font to use when itemizing.
+ This probably means adding a attribute type which contains
+ a PangoFont *, and overrides the description.
+
+* pangox.c needs to be split into at least two separate files.
+
+ (
+ Probably along the lines of
+
+ 1) font map
+ 2) font
+ 3) rendering
+ )
+
+
Other rendering engines
=======================
@@ -132,3 +149,8 @@ General
characters in the glyph. (Trailing is currently a boolean
for us.)
+* pango_font_get_metrics() currently takes a language tag, but
+ really uses that to find out one or more _scripts_; should we
+ define script tags and put those (optionally?) in the
+ interface?
+