@@ -1,40 +0,0 @@
1−# TODO
2−
3−* Use new downloads feature on google code. Figure out naming
4− scheme for releases.
5−
6−* state license on first page of website. also at top of every
7− source file...some say? (c) date, and license with link to text.
8−
9−* Clean up Haskell code, refactor, etc.
10−
11−* new writers? man page! (but we'd really need definition lists),
12− docbook.
13−
14−* Use XHTML library for HTML writer? Not yet - it's not standard
15− with 6.4.2 (but is with 6.6). When we can drop support for
16− 6.4.2, we can use it.
17−
18−* Windows zipfile: zip -r pandoc-0.3-windows.zip pandoc.exe README LICENSE
19− Be sure to convert to Windows line-endings.
20− in bash: sed -e 's/$'"/`echo \\\r`/" README > README.txt
21−
22−* pandoc's HTML output fails to validate completely (w3c).
23− There are a few quirks:
24− + HTML doesn't like the \> at the end of <meta tags.
25− But if we remove them, we'll have trouble with S5 output,
26− which seems to need the xhtml header?
27− + There's also a problem with the email obfuscation scheme.
28− <noscript> isn't allowed inside <p> blocks. <script> is
29− allowed! Options:
30− - come up with another scheme, perhaps more like markdown.pl's
31− See the nice idea at http://subversion.tigris.org/security.html,
32− using spans.
33− - ignore the validation problems
34− - others?
35−
36−* Consider adding support for acronyms.
37− Perhaps like this: [AAAS]
38− [AAAS]: "American association for the advancement of science"
39− <acronym title="American association for the advancement
40− of science">AAAS</acronym>