title)?
- - looking for other good ideas ;-)
- - remove elements. Use
and elements to get
- a similar effect.
-
-* Autogeneration of PDF
- - André is working on this, Erik volunteers to help out
-
-* Improving the "security docs"
- - More content and better organisation.
- - mod_dav ressources are owned by the httpd
-
-* General cleaning and improving of module docs
-
-* Making the directive definitions "less terse" (i.e., adding more
- examples and details to the definitions of the directives)
-
-* Making site-specific enhancements easier, including a documented
- and robust way for 3P module docco to be added -- and have it
- survive a server docco upgrade
-
- - This could be something a simple and hackish as a manual/extra/
- directory (a la the 1.3 src/modules/extra/ directory) and a
- script in the support directory that scans the files there and
- updates the manual indices. (We do something like that now for
- httpd.conf file with apxs [LoadModule, etc.].)
-
-* Summarize all the implemented drafts/standards with short explanations
- within a document. (PR 16938)
-
-XML Conversions
-===============
-
-The following files need to be converted to XML as described at
-http://httpd.apache.org/docs-project/docsformat.html
-# Perhaps these should be left in html to allow the developers to
-# play with them
-# nope. in order to create other formats, we need 'em as xml. --nd
-developer/API.html
+- Provide example solutions for the mapping of encodings, especially
+ for .gz etc. (also in regard to our default configuration)
+
+- How-To style documents for more of the daily tasks
+ - Logging, log rotation, and log reporting
+ - Secure mod_dav configuration
+
+- Writing modules - Can we provide a basic intro to writing modules,
+ perhaps based around mod_example, or one of the other simple example
+ modules?
+
+- http://httpd.apache.org/docs/trunk/developer/ is a graveyard, and a
+ profound embarrassment.
+ - Purge all the dead links
+ - Introductory module authoring doc
+ - Verify links to external resources at least every year
+
+- Update the list of translations at
+ http://httpd.apache.org/docs-project/translations.html Some of those
+ are accurate, and others are way outdated.
+
+- I'd like to expand the discussion of conditional logging, and add a
+ few more useful exmaples.
+ That would be a good place to document logging of cache hit/miss:
+ https://issues.apache.org/bugzilla/show_bug.cgi?id=48241#c2
+
+- Is it worth having a doc that discusses recommended (what does this
+ mean?) third-party modules like mod_security, mod_php, and so on - the
+ things that we all assume everyone uses, but some folks might not know
+ about.
+
+- Clarify which directives only affect requests when they're handled
+ by the default handler. (e.g. ForceType, TraceEnable, etc.)
+
+- Add examples using expr to mod_rewrite recipes. Possibly benchmark the
+ different approaches and make intelligent remarks about the
+ comparative value of each.
+
+- Fix this error message:
+ Request exceeded the limit of 10 internal redirects due to probable
+ configuration error. Use 'LimitInternalRecursion' to increase the limit
+ if necessary. Use 'LogLevel debug' to get a backtrace.
+ This error message is often returned when a RewriteRUle loops, in
+ which case setting LimitInternalRecursion won't do anything towards
+ fixing the problem. However, the error message is already very long.
+ Thoughts?
+
+LaTeX Todo list
+==================
+
+- Dozens of other little problems with presentation, cross-referencing,
+ etc.
+
+- Cleanup xsl to make it more readable. Almost everything
+ that is currently in latex.xsl should probably be moved to common.xsl.
+ There may be a license problem with the atbeginend.sty file, since
+ latex style files rarely have explict licenses. At worst, we can
+ drop this and manually adjust the relevant spacing.
+
+- Reduce the size of the pdf (both bytes and pages) in any way possible.
+
+- Translations.
+
-# converting from nroff to xml
-programs/other.html