[STATUS] (httpd-docs-1.3) Wed Aug 20 23:46:26 EDT 2003
Apache HTTP Server 1.3 Documentation Status File. Last modified: $Date: 2002/07/05 03:23:41 $ If you are interested in helping accomplish some of the tasks on this list or otherwise improving the documentation, please join the apache-docs mailing list by sending an empty message to [EMAIL PROTECTED] For more information on how to contribute to the Apache Documentation Project, please see http://httpd.apache.org/docs-project/, and http://apache-server.com/tutorials/ATdocs-project.html for an excellent tutorial on how to get started with making your contribution. -- Translations * We appear to have people working on translation into the following languages. These may just be the 'it worked' page, but if so the authors of those should perhaps be contacted to help do the rest.. :-) Note that this list is NOT identical to that for the 2.0 documentation project! [Should we attempt to get a known-current authorlist together? --jsl] - Catalan (.ca) - Czech Republic (.cz) - German (.de) - Danish (.dk) - Estonia (.ee) - Greek (.el) - Spanish (.es) - French (.fr) - Hebrew (.he.iso8859-8) - Italian (.it) - Japanese (.ja.jis) - Korean (.kt.iso-kr) - Luxembourgish (.lb) - Dutch (.nl) - Norwegian (.no) - Polish (.po.iso-pl) - Portuguese (.pt) - Portuguese [Brasilian] (.pt-br) - Russian (.ru.cp-1251, .ru.cp866, .ru.iso-ru, .ru.koi8-r, .ru.ucs[248]) - Swedish (.se) - Chinese (.zh) New User documentation == * Adding more documentation for new users - I believe that we'll need to get more info on what is missing, ie. user feedback and whatnot. --jsl Documentation improvements == * Improving the security docs - More content and better organisation. * 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) - We'll need to audit these and find out which ones need munging, as some of it looks ok. --jsl * 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.].) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[STATUS] (httpd-docs-2.0) Wed Aug 20 23:46:37 EDT 2003
Apache HTTP Server 2.1 Documentation Status File. Last modified: $Date: 2003/07/25 10:54:59 $ For more information on how to contribute to the Apache Documentation Project, please see http://httpd.apache.org/docs-project/ -- Decisions pending = - Remove manual/search/manual-index.cgi from the distribution and httpd-2.0-docs/ repository? These can be maintained in the httpd-site repository but don't belong in distributions unless we introduce the tools to generate the index database or keep a current database checked into cvs. +1: wrowe, nd, slive, erikabele, kess, mads - Remove several out-of-place files into somewhere in the tree outside of the actual web site content? Erik suggests we merge the two icons readmes into one. Perhaps all of these go into httpd-2.0/docs/README? error/readme icons/readme icons/small/readme.txt Votes for a single top-level README reference? +1: wrowe, slive, nd, erikabele, kess, mads Things That Need Fixing === - Windows platform docs are in desperate need of rewrites/updates for 2.0. - Bill Rowe and Bill Stoddard are good contacts for tech questions. - using apache has been done, compiling apache is still open - hints on uninstalling apache (exit monitor, close directories, registry entries etc) (PR 10154) - FAQ: UTF-8 config and URL encoding for non-ascii characters. - FAQ: AcceptEx failed / virusscanner, firewall fun - New Auth system - Much clean-up and enhancement of aaa howto - Independent note on how to upgrade to new auth system - modules docs - mod_suexec: very little documentation - mod_proxy: updates for 2.0 - mod_status: updates for 2.0 - mod_example: updates for 2.0 - mod_rewrite: explain, when which variables are actually available (PR 16402) - MPM documentation - explain what the following command line options do (perhaps in the developer/debugging docs): -D DEBUG -D ONE_PROCESS one-process-mode == no threads, i.e. only one process handling the requests in a single loop? -D NO_DETACH (not in every MPM avail.) no daemon, but detached from terminal? -D FOREGROUND (not in every MPM avail.) ? - Individual docs will need some cleanup. - misc/custom_errordocs.html needs to be updated to essentially describe how the international error docs included in 2.0 work - misc/perf-tuning.html - needs major rewrite for 2.0 - misc/rewriteguide.html - needs cleaning in 1.3 and 2.0 - platform/ebcdic.xml - needs major rework for 2.0 - New build process. - install.html has had a first-pass rewrite, it is basically accurate, but very incomplete: many configure options are missing, especially those inherited from apr. - API documentation - Ben Laurie has written some hooks documentation - authn provider API documentation could be useful - SSL docs are generally good, but they need a refreshing by someone familiar with mod_ssl and openssl. - I've begun working on this (again) --mads - How does Proxy fit into sections.html? Documentation improvements == * New user docs: Directory Handling (mod_dir/mod_autoindex/etc) * Enhancements to the DTD/XSL: - glossary tag that links to the glossary and uses some special style in the css. - New index: directives by context, including listing which directives are available for each AllowOverride setting. - New index: backout modules by type (aaa, mappers, loggers etc.) probably by introducing a category element in modulesynopsis - Use a tag like var in place of em for things like the syntax listing. - in progress - add letter links to glossary and quickreference, perhaps also a term overview (sidebar) - remove pre elements. Use br / and indent elements to get a similar effect. * Improving the documentation of the documentations' build system itself (requirements, procedures) * 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
Re: ja translation new comer
Tetsuya Kitahata [EMAIL PROTECTED] writes: Hayashi-san, please verify the translated file I've put to docs at httpd.apache.org if you can read the file via MUA or online. I'll try to review it as soon as possible but I've just relocated so I cannot tell how soon that will be. I might be able to do it tonight or tomorrow. I think I have some free time until classes begin. P.S. Are you in US (El Paso, Texas??) now? Hayashi-san Yes, it was a really long trip. I'm still trying to recover form jet lag. :-) -- Yoshiki Hayashi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ja translation new comer
On Wed, 20 Aug 2003, William A. Rowe, Jr. wrote: I think the license file could be one of the controversial issues, regarding the accuracy of the translation. If you need assurance of the quality of the translation, I am willing to put the confirmation of laywers in japan (my friends), sooner or later. This has come up - from the perspective that the license may not be enforceable in some jurisdictions without the native translation. At some point translations might become necessary. Eh - you want to be preceice here; generally when you have two entities who are both in X then you want to make sure that their agrement is constructed according to X law and habits. If the entities are in X and Y then generally the law and language of the license granter is used (or the Seller, etc - there is a whole international law framework specially for this). So, say, a German developer using the GPL for his code , may well need a german version. We may have this issue when we accept code from a third party in Germany. However... the apache end user license is 'special' in that it is an agreement with the Apache Software Foundation, a Delaware, US Inc to some other entity. So for _us_ (not for the general open source case) we are fine with a License written in the US langauge and within the US framework - and though it is nice to have translations to _explain_ the license; the authoritative document of the Apache Software Foundation is, and will be, in US English only. Dw - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
