ttxgettext: Handle UTF-8 input

[deb/packages.git] / TODO

diff --git a/TODO b/TODO
index 0fc9fd3f4c08fb0125be5d1fc8c84d5d50d99ed1..6e1279dd1cd3aeb443d529d352e55942beb6cd12 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-search_packages.pl:
+search_packages:
 - all searches:
   - Display "$pkg ($section) shortdesc from stable (or if not available, testing, unstable, ...)"
     tersely on one line each, with "#foo" links to what's currently displayed.
@@ -19,10 +19,6 @@ search_packages.pl:
        matches" and abce: 90 matches"
 
 - fulltext search:
-  - Max 100 results
-  - Better exact=1 performance by indexing per word?
-  - drop case-sensitive from options, descriptions.txt all lowercase and without
-       punctuation, such that instead of =~ //, indexof can be used
   - in results, show full descriptions, so one sees what's being matched?
 
 - backend:
@@ -30,14 +26,18 @@ search_packages.pl:
        show_package relies on that. So foreach suite, 'newest entry', and only
        then, all the other entries
 
+search_contents:
+- regain section (main/contrib/non-free) information? It is currently
+   not available at all.
+
+Static pages:
+- try to make it faster
+
 General:
 - Try to break everything with empty/short searches
 - Check for case sensitive consistency
 - Fix assumption that archive doesn't show up in any url, consistency-fy
   dealing with archives of a different set than (us, non-us, security)
-- Some packages are both concrete and virtual, deal with that: in depends
-  display of show_package (now if a package is concrete, you only see that),
-  and eh, somewhere else too ttbomk
 - grep -ri fixme
 - searchon=all -> searchon=descriptions?
 - quicksearch box: copy parameters of current search (exact,suite,arch,etc),
@@ -45,9 +45,29 @@ General:
   obscure, but otoh, for typo fixing more appropriate.
   Maybe best of both worlds is 'modify search' below results, where you can
   generalize/specificy arch, etc etc?
+- In Search.pm, make sure read_entry_small only scans a bit, and not all --
+  once you have #max_nr_of_suites, you know you won't find the queried suite
+  anymore, so search further is futile. Maybe the backend could even add a
+  marker, ignored by read_entry_all, but understood by read_entry_small, that
+  indicates end of $res2 and start of $res3
+- Store in db \1-separated, and split on that, instead of the more fragile
+  '/, /' split
+- Fields we don't handle in any way currently:
+  Conflicts
+  Replaces
+  Enhances
+  Origin    -- not needed
+  Bugs      -- not needed
+  Task
+  Python-Version(s) -- not needed
 
+Cron:
+- Verify Release files
+- refactorize 100syncarchive* so that there is not so much copied code
 
-Bugs:
-- amd64 security is getting displayed weirdly
-- kfreebsd-i386 contents files have no header and aren't read correctly
-  currently
+Missing pieces from old code:
+ - gettext support in templates
+ - search_packages result parser?
+   reportbug in sarge is completly broken in this regard anyway AFAICT
+   reportbug in etch works as long as there is the exact hit but
+   breaks once there is more than one hit