[TODO] Move some items from ROADMAP, and some new ones, into TODO

2 files changed, 34 insertions, 23 deletions

diff --git a/ROADMAP b/ROADMAP
index b5a539f91..ba931f36a 100644
--- a/ROADMAP
+++ b/ROADMAP
@@ -65,23 +65,6 @@ cairo 1.4.0 ideas (think performance!)
 
 ✓ New tessellator
 
- Look into using alloca instead of malloc when copying glyphs/path/etc to edit
- and use in one function and deallocate upon return.
-
- Look into generating EPS.  That may be done using a new constructor for the
- PS backend, or better, using an API similar to
- cairo_svg_surface_restrict_to_version.  The PDF backend needs a restrict_to
- API at some point too.
-
- Look into the glyph cache.  Moreover, make sure we are reusing scaled fonts
- enough.
-
- User-font API---a couple of threads of interest:
-	http://lists.freedesktop.org/archives/cairo/2006-May/006893.html
-	http://lists.freedesktop.org/archives/cairo/2006-May/006888.html
-
- Polling API (cairo_get_serial and cairo_changed)
-
  Bugs to fix
  -----------
    CAIRO_EXTEND_PAD is not implemented for surface patterns
diff --git a/TODO b/TODO
index c44c5f4c5..cc82af67c 100644
--- a/TODO
+++ b/TODO
@@ -75,20 +75,36 @@ Other changes (this text used to be in RODMAP)
      cairo_arc_to
 	see http://lists.freedesktop.org/archives/cairo/2005-August/004801.html
 	or see arc_to branch in bedhad's repository
+      User-font API---a couple of threads of interest:
+        http://lists.freedesktop.org/archives/cairo/2006-May/006893.html
+	http://lists.freedesktop.org/archives/cairo/2006-May/006888.html
+      Polling API (cairo_get_serial and cairo_changed)
 
  PS/PDF improvements
      1. Make image fallbacks finer-grained than a whole page
-     2. Ensure that PDF text output is "selectable"
+     2. Ensure that PDF text output is "selectable". see this thread:
+	http://lists.freedesktop.org/archives/cairo/2007-January/009059.html
+     3. Fix extend modes in PDF
+     4. Fix encoding "issues" reported here:
+        http://lists.freedesktop.org/archives/cairo/2006-December/008985.html
+     5. Use glyph advances to generate more compact PS/PDF
+     6. Look into generating EPS.  That may be done using a new constructor
+        for the PS backend, or better, using an API similar to
+        cairo_svg_surface_restrict_to_version.  The PDF backend needs a
+        restrict_to API at some point too.
+
+ Xlib backend
+     1. xlib backend requires xrender to compile, while it can perform without
+        xrender at run time.  Make it compile without it. see
+	http://lists.freedesktop.org/archives/cairo/2006-October/008075.html
+     2. Cache patterns (maybe solid ones only). see
+	http://lists.freedesktop.org/archives/cairo/2006-December/008916.html
 
  Quartz backend (maintainer needed!)
      1. Mark Quartz backend as supported:
 	 a. Incorporate into test suite
 	 b. Correct output for the entire suite
 
- Misc
-     1. xlib backend requires xrender to compile, while it can perform without
-        xrender at run time.  Make it compile without it.
-
 Some known bugs (this text used to be in BUGS)
 ==============================================
 XXX: Many of these bugs are likely no longer valid. We should
@@ -145,10 +161,22 @@ cairo_scale (cr, 0, 0);
 Text drawn with vertical metrics cannot currently use TrueType
 subsetting for PDF/PS output as the code doesn't write out the necessary
 VHEA or VMTX entries to the TrueType font objects. As a result, cairo uses
-Type3 fonts which generates slightly different outlines.
+Type3 fonts which generates slightly different outlines.  Type1 has the same
+problem.
 
 --
 
 Text transformations is a mess in PS/PDF backends.  Many combinations of
 rotated/scaled ctm, rotated/scaled font_matrix, and subsetting code used
 (Type1/Type3/TrueType) are broken.
+
+--
+
+Move docs inline.  see
+http://lists.freedesktop.org/archives/cairo/2006-July/007431.html
+
+--
+
+Look into the glyph cache.  Moreover, make sure we are reusing scaled fonts
+enough.
+