Put TODO list in the README directly.

README.rst

@@ -30,5 +30,22 @@ For example, if we want to translate some basic multi-block text to HTML:
 
 	print(tohtml(text))
 
+What is left to do for the next release
+---------------------------------------
+
+- Fix the not-passing unit test (``[color=blue]oh[youtube]h4WLX8hfpJw``).
+- Produce a test stylesheet for demonstration purposes.
+- Manage lightscript (or even markdown?) as output languages;
+- Check where the errors are to display them to the user:
+
+  * Count character offset, line number and column number in the lexer;
+  * Produce readable exceptions;
+  * Make a clean interface to transmit them;
+- Check why exceptions on raw tags effectively escape the content, as it
+  shouldn't…?
+- Look for security flaws (we really don't want stored XSS flaws!).
+- Implement match names (such as ``\[\*+\]`` for lists).
+- Manage keywords with tags such as ``[tag key=value other="something else"]``.
+
 .. _Planète Casio: https://www.planet-casio.com/
 .. _the official website: https://textout.touhey.pro/

TODO.rst

@@ -1,15 +0,0 @@
-What is left to do
-==================
-
-- Add an ``[imgurl]`` tag?
-- Manage lightscript (or even markdown?) as output languages;
-- Check where the errors are to display them to the user:
-
-  * Count character offset, line number and column number in the lexer;
-  * Produce readable exceptions;
-  * Make a clean interface to transmit them;
-- Check why exceptions on raw tags effectively escape the content, as it
-  shouldn't…?
-- Look for security flaws (we really don't want stored XSS flaws!).
-- Implement match names (such as ``\[\*+\]`` for lists).
-- Manage keywords with tags such as ``[tag key=value other="something else"]``.