Release pango-0.8

Thu Mar  9 19:55:21 2000  Owen Taylor  <otaylor@redhat.com>

	* Release pango-0.8

	* docs/TEXT/coding-style: Added some notes about coding style
	within Pango.

	* modules/*.[ch]: New version from Karl Koehler adding support
	for vowels marks, better ligatures.

	* docs/tmpl/*: Doc updates

        * libpango/pango-layout.[ch] libpango/pangox/.[ch]: Add functions
	for handling paragraphs as 2-D objects, not simple lists of lines,
	to make things easier for people using pango-layout.

        * examples/viewer.c: Simplify using the now 2-D layout-capabable
	PangoLayout.

	* libpango/fonts.c (pango_font_{get_coverage,find_shaper}): Allow
	NULL language tag.

	* libpango/modules.c (_pango_find_map): Fix for allowing
	NULL language tag.

1 files changed, 27 insertions, 17 deletions

diff --git a/TODO b/TODO
index e40dd080..2c2af052 100644
--- a/TODO
+++ b/TODO
@@ -5,25 +5,26 @@ Layout Driver
 =============
 
 The PangoLayout object is a highlevel driver that takes an attributed
-string and produces lines of glyphs. As well as just implementing
-this, there are various improvements that need to be made to 
+string and produces lines of glyphs.
 
 * Figure out better ways of doing line breaks. (This may involve
   implementing the TeX/Raph x0-x1 stuff for line breaks.)
 
-X rendering
-===========
+* Add spacing parameter as illustrated; this should be a quick
+  (10 minute) addition.
 
-* The point-size/pixel size handling is not done right. Right
-  now we are just assuming pixel == point, because trying to
-  use the point-size fields of the X fonts didn't work on
-  systems with both 100 and 75 dpi fonts installed.
+* Although PangoLayout isn't intended to handle large amounts
+  of text, it should be able to handle embedded "\n" and simple
+  multiple paragraphs. This could be done entirely within 
+  pango_layout_check_lines()
 
-  We should query the X server for its actual reported value
-  and use that to translate point size to pixel size.
+* Attribute handling needs to be added (fg/bg/underline, etc.)
+  Each PangoItem should have a list of associated non-font
+  attributes ... though this would require a bit more thought
+  as to memory-management of PangoItem, which is currently add-hoc.
 
-  (This doesn't really handle the case of optically scaled
-   bitmaps properly, but I think that is an ignorable problem.)
+X rendering
+===========
 
 * Right now we assume a single resolution for all fonts on a display;
   but in theory, the resolution could be per-screen. To solve 
@@ -34,8 +35,11 @@ X rendering
 Other rendering engines
 ======================
 
-Somebody should start working on a libart font-system / renderer
-soon, to make sure that the interfaces are suitable.
+* Somebody should start working on a libart font-system / renderer
+  soon, to make sure that the interfaces are suitable.
+
+* FreeType-2.0 support could be very interesting, with the OpenType 
+  that it has.
 
 Engines
 =======
@@ -46,8 +50,10 @@ Engines
 Language Modules
 ================
 
- * It would be nice to have X based renderers for a few more scripts;
-   Arabic in particular is one such script.
+ * It would be nice to have X based shapers for a few more scripts;
+   Hindi is one obvious need. (Actually, there may be a need for
+   a generic framework for Indic shapers to be developed. A
+   libpango-indic...)
 
  * Once we have a libart renderer, porting Raph's devanagari shaper
    to Pango and C (from Perl) would be a cool demo and test case.
@@ -103,4 +109,8 @@ General
 * Finish coverting over from utils.c to Tom Tromey's libunicode.
   Add the remaining useful functions from utils.c into libunicode.
 
-* s/num_chars/n_chars/ etc. (Always use n_ as enumeration prefix)
\ No newline at end of file
+* s/num_chars/n_chars/ etc. (Always use n_ as enumeration prefix)
+
+* Underline attribute should be an enumeration (none/single/double/squiggle/low,
+  where low is below the ink rect - a style appropriate for underline
+  accelerators.)
\ No newline at end of file