GSoC PyHurd application: Ideas for translators.

1 files changed, 2 insertions, 2 deletions

diff --git a/community/weblogs/ArneBab/2011-04-06-application-pyhurd.mdwn b/community/weblogs/ArneBab/2011-04-06-application-pyhurd.mdwn
index 47d16f3a..8e887e41 100644
--- a/community/weblogs/ArneBab/2011-04-06-application-pyhurd.mdwn
+++ b/community/weblogs/ArneBab/2011-04-06-application-pyhurd.mdwn
@@ -29,9 +29,9 @@ For this years GSoC I want to turn the currently rudimentary Python Bindings of
   3. design a pythonic high-level API for translators.
 2. Realize a pythonic trivfs library and an example translator using it.
 3. Mid-Term: trivfs works. Push the code to https://github.com/ArneBab/PyHurd
-4. Implement more complex and specialized translator libraries, along with example translators.
+4. Implement more complex and specialized translator libraries, along with example translators. This should recreate the Hurd libraries for Python. Ideally seperate the libraries, so programmes can simply import the convenience functionality they need.
 5. Re-implement some hurd specific utils in pyhurd such as settrans.
-6. With the remaining time, create as many cool translators as possible :)
+6. With the remaining time, create as many interesting translators as possible. Ideas include all compression formats supported by Python, markdown to HTML translators to be accessed with nsmux (file.mdwn,,html), automatic version tracking directories and overlay stores which store changes to nonchanging files like squaschfs, but also simple translators like translator-based write-locking of files by not catching write-accesses.
 7. Push the final code to https://github.com/ArneBab/PyHurd
 
 ## Initial Fix