(httpd-site) branch asf-site updated: Automatic Site Publish by Buildbot
[email protected] Mon, 22 Jun 2026 17:47:09 +0000
| Newsgroups | gmane.comp.apache.cvs |
|---|---|
| Message-ID | <178215042954.1957818.9554270942753475456@gitbox3-he-fi.apache.org> |
This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/httpd-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 266b942 Automatic Site Publish by Buildbot
266b942 is described below
commit 266b942e07dbc70ff25e3338bafd52fc7e908d12
Author: buildbot <[email protected]>
AuthorDate: Mon Jun 22 17:47:05 2026 +0000
Automatic Site Publish by Buildbot
---
output/docs-project/avail_translations.html | 2 +-
output/docs-project/contribute.html | 18 +++++++
output/docs-project/goingfurther.html | 73 +---------------------------
output/docs-project/index.html | 63 +++++++-----------------
output/docs-project/svn.html | 29 +++++++++++
output/docs-project/translations.html | 74 ++++++++++++++++++++++++++---
6 files changed, 135 insertions(+), 124 deletions(-)
diff --git a/output/docs-project/avail_translations.html b/output/docs-project/avail_translations.html
index 2b396c9..56de39c 100644
--- a/output/docs-project/avail_translations.html
+++ b/output/docs-project/avail_translations.html
@@ -93,7 +93,7 @@ translated into each language. There's plenty of room to help — if you
see gaps in a language you speak, we'd welcome your contribution.</p>
<p>To get started translating, see the <a href="translations.html">translation guide</a>.
To learn about keeping translations up to date, see
-<a href="goingfurther.html">Maintaining Translations</a>.</p>
+<a href="translations.html#maintaining">Maintaining Translations</a>.</p>
<p>If you can provide translations into any of these languages (or any
others not yet listed), please let us know on
<a href="mailto:[email protected]">[email protected]</a>.</p>
diff --git a/output/docs-project/contribute.html b/output/docs-project/contribute.html
index bafcbaa..4fb3af4 100644
--- a/output/docs-project/contribute.html
+++ b/output/docs-project/contribute.html
@@ -95,6 +95,16 @@ difference. Your work will be read by millions of httpd users worldwide.</p>
<p>This page is about <em>contributing to the docs</em>, not about configuring
httpd. For configuration help, see the
<a href="../userslist.html">Users mailing list</a>.</p>
+<h2 id="before-you-start">Before You Start<a class="headerlink" href="#before-you-start" title="Permalink">¶</a></h2>
+<ul>
+<li><strong>No ICLA or ASF account is needed</strong> to submit documentation patches.
+Anyone can contribute.</li>
+<li><strong>The GitHub mirror</strong> (github.com/apache/httpd) is read-only — do NOT
+open pull requests there. They won't be reviewed. Patches go through
+SVN and the mailing list.</li>
+<li><strong>Patches sent to the mailing list</strong> are typically reviewed within a
+few days.</li>
+</ul>
<h2 id="ways-to-contribute">Ways to Contribute<a class="headerlink" href="#ways-to-contribute" title="Permalink">¶</a></h2>
<p>There's something for every skill level:</p>
<h3 id="quick-wins-no-svn-needed">Quick Wins (no SVN needed)<a class="headerlink" href="#quick-wins-no-svn-needed" title="Permalink">¶</a></h3>
@@ -108,6 +118,14 @@ idea.</li>
<li><strong>Join the conversation</strong> — Subscribe to <code>[email protected]</code> and
weigh in on ongoing discussions.</li>
</ul>
+<h3 id="fast-path-for-small-fixes">Fast Path for Small Fixes<a class="headerlink" href="#fast-path-for-small-fixes" title="Permalink">¶</a></h3>
+<p>You don't need SVN to report a problem or suggest a fix. For typos or
+small corrections, just describe the fix in an email to
+<code>[email protected]</code>, or open a Bugzilla ticket with the corrected
+text. A committer will apply it for you.</p>
+<p>For anything more than a sentence or two, the SVN patch workflow
+(described below) is preferred — it gives reviewers the full context of
+your change.</p>
<h3 id="fix-and-improve-svn-patch-workflow">Fix and Improve (SVN patch workflow)<a class="headerlink" href="#fix-and-improve-svn-patch-workflow" title="Permalink">¶</a></h3>
<ul>
<li>Fix typos, broken examples, or unclear explanations.</li>
diff --git a/output/docs-project/goingfurther.html b/output/docs-project/goingfurther.html
index fcaa241..3b8618d 100644
--- a/output/docs-project/goingfurther.html
+++ b/output/docs-project/goingfurther.html
@@ -5,7 +5,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1">
<link href="/css/apsite.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet">
<meta name="author" content="Documentation Group"><meta name="email" content="[email protected]">
- <title>Maintaining Translations - The Apache HTTP Server Project</title>
+ <title>Maintaining Translations (Moved) - The Apache HTTP Server Project</title>
<style>
.headerlink {
visibility: hidden;
@@ -87,76 +87,7 @@ h1:hover > .headerlink, h2:hover > .headerlink, h3:hover > .headerlink, h4:hover
</div>
<!-- RIGHT SIDE INFORMATION -->
<div id="apcontents">
- <h1 id="maintaining-translations">Maintaining Translations<a class="headerlink" href="#maintaining-translations" title="Permalink">¶</a></h1>
-<p>Once you've started translating, the ongoing work is keeping your
-translations up to date as the English source evolves. This page
-describes a practical workflow for tracking changes and updating your
-translated files.</p>
-<h2 id="the-basic-idea">The Basic Idea<a class="headerlink" href="#the-basic-idea" title="Permalink">¶</a></h2>
-<p>The English documentation changes over time — bugs get fixed, features
-get documented, examples get improved. As a translator, you need to:</p>
-<ol>
-<li>Detect which English files have changed since you last translated</li>
-<li>See what specifically changed</li>
-<li>Apply the equivalent changes to your translated files</li>
-<li>Verify your work builds correctly</li>
-</ol>
-<h2 id="recommended-workflow">Recommended Workflow<a class="headerlink" href="#recommended-workflow" title="Permalink">¶</a></h2>
-<h3 id="set-up-your-working-environment">Set Up Your Working Environment<a class="headerlink" href="#set-up-your-working-environment" title="Permalink">¶</a></h3>
-<p>Check out both active branches:</p>
-<pre><code>svn checkout https://svn.apache.org/repos/asf/httpd/httpd/trunk/docs httpd-trunk
-svn checkout https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/docs httpd-2.4
-</code></pre>
-<h3 id="track-changes-with-svn">Track Changes with SVN<a class="headerlink" href="#track-changes-with-svn" title="Permalink">¶</a></h3>
-<p>The simplest way to see what's changed since a known revision is
-<code>svn diff</code> between revisions. If you noted that you last synchronized
-your translation at revision 1900000, you can see all changes since then:</p>
-<pre><code>svn log -r 1900000:HEAD docs/manual/mod/mod_rewrite.xml
-svn diff -r 1900000:HEAD docs/manual/mod/mod_rewrite.xml
-</code></pre>
-<p><strong>Tip:</strong> Note the current revision number each time you finish updating
-a translation. Add it as a comment at the top of your translated file:</p>
-<pre><code><!-- English Revision: 1912345 -->
-</code></pre>
-<p>This makes it easy to check what's changed next time:</p>
-<pre><code>svn diff -r 1912345:HEAD docs/manual/mod/mod_rewrite.xml
-</code></pre>
-<h3 id="update-your-translation">Update Your Translation<a class="headerlink" href="#update-your-translation" title="Permalink">¶</a></h3>
-<p>With the diff output showing what changed in the English source, apply
-the equivalent changes to your translated file. Focus on:</p>
-<ul>
-<li>New paragraphs or sections that need translating</li>
-<li>Changed examples or directive descriptions</li>
-<li>Removed content that should also be removed from your translation</li>
-<li>Corrected technical information</li>
-</ul>
-<h3 id="verify-your-work">Verify Your Work<a class="headerlink" href="#verify-your-work" title="Permalink">¶</a></h3>
-<p>Build the docs to confirm your XML is valid and the output looks right:</p>
-<pre><code>cd docs/manual/build
-./build.sh validate-xml
-./build.sh <your-language-code>
-</code></pre>
-<p>Open the generated HTML in a browser to review the final result.</p>
-<h3 id="submit-your-updates">Submit Your Updates<a class="headerlink" href="#submit-your-updates" title="Permalink">¶</a></h3>
-<p>Send your updated files as a patch:</p>
-<pre><code>svn diff > translation-update.patch
-</code></pre>
-<p>Email the patch to <code>[email protected]</code>, or attach it to a
-<a href="https://bz.apache.org/bugzilla/">Bugzilla ticket</a>.</p>
-<h2 id="staying-in-sync">Staying in Sync<a class="headerlink" href="#staying-in-sync" title="Permalink">¶</a></h2>
-<p>A few habits that make maintenance easier:</p>
-<ul>
-<li><strong>Update regularly</strong> — small, frequent updates are much easier than
-catching up after months of changes.</li>
-<li><strong>Watch the commits list</strong> — subscribe to the svn commits to see
-documentation changes as they happen.</li>
-<li><strong>Coordinate with other translators</strong> — if there are multiple people
-working on your language, divide the work and communicate via the
-mailing list.</li>
-</ul>
-<h2 id="questions">Questions?<a class="headerlink" href="#questions" title="Permalink">¶</a></h2>
-<p>If you get stuck or have questions about maintaining translations, reach
-out to <code>[email protected]</code>. We're happy to help.</p>
+ <p>This content has been merged into the <a href="translations.html#maintaining">Translations</a> page.</p>
<!-- FOOTER -->
<div id="footer">
diff --git a/output/docs-project/index.html b/output/docs-project/index.html
index 82443b5..04079f7 100644
--- a/output/docs-project/index.html
+++ b/output/docs-project/index.html
@@ -95,42 +95,21 @@ help.</p>
<p>You don't need to be a programmer. You don't need to be an httpd expert.
If you can read the docs and spot something that could be clearer, you're
already qualified to contribute.</p>
-<h2 id="quick-links">Quick Links<a class="headerlink" href="#quick-links" title="Permalink">¶</a></h2>
+<h2 id="get-involved">Get Involved<a class="headerlink" href="#get-involved" title="Permalink">¶</a></h2>
<ul>
-<li><a href="#report">Report a problem</a></li>
-<li><a href="#suggestion">Make a suggestion</a></li>
-<li><a href="#contribute">Contribute to the docs</a></li>
-<li><a href="#translate">Translate the documentation</a></li>
-<li><a href="#docs">Find the docs</a></li>
-<li><a href="#ml">Join the mailing list</a></li>
-<li><a href="#irc">Chat with us on IRC</a></li>
+<li><strong><a href="contribute.html">Contribute to the docs</a></strong> — report problems, suggest
+improvements, fix errors, or write new content.</li>
+<li><strong><a href="translations.html">Translate the documentation</a></strong> — help make the docs
+accessible to non-English speakers.</li>
+<li><strong><a href="svn.html">SVN workflow</a></strong> — check out the source and submit patches.</li>
+<li><strong><a href="docsformat.html">Documentation format</a></strong> — learn the XML format used
+for the docs.</li>
+<li><strong><a href="style-guide.html">Style guide</a></strong> — markup and prose conventions.</li>
+<li><strong><a href="tools.html">Tools for contributors</a></strong> — editor and workflow
+recommendations.</li>
+<li><strong><a href="contributors.html">Contributors</a></strong> — the people who built these docs
+(we hope to add your name here soon).</li>
</ul>
-<h2 id="report">Report a Problem<a class="headerlink" href="#report" title="Permalink">¶</a></h2>
-<p>Found something wrong? The best way to report it is to <a href="https://bz.apache.org/bugzilla/enter_bug.cgi?product=Apache%20httpd-2&component=Documentation">open a
-Bugzilla ticket</a>
-with "Documentation" selected as the component.</p>
-<p>You can also check the <a href="http://s.apache.org/httpd-doc-bugs">list of open documentation
-bugs</a> to see if it's already known.</p>
-<h2 id="suggestion">Make a Suggestion<a class="headerlink" href="#suggestion" title="Permalink">¶</a></h2>
-<p>Have an idea for how we could explain something better? Want to propose
-a new how-to or tutorial?</p>
-<p>The best approach is to <a href="#ml">join the mailing list</a> and start a
-conversation. You can also <a href="#report">open a Bugzilla ticket</a> with your
-suggestion. Either way, we're glad to hear from you.</p>
-<h2 id="contribute">Contribute<a class="headerlink" href="#contribute" title="Permalink">¶</a></h2>
-<p>Ready to dive in? Our <a href="contribute.html">contribution guide</a> walks you
-through the different ways to help — from quick fixes to substantial new
-content. The workflow uses SVN and patches, and we have a
-<a href="svn.html">step-by-step SVN guide</a> to get you started.</p>
-<p>New to the XML format we use? That's fine — take a look at the
-<a href="docsformat.html">documentation format</a> page, and don't hesitate to ask
-questions on the mailing list. We're happy to help you get oriented.</p>
-<p>See also: <a href="tools.html">Tools for Contributors</a> for editor and workflow
-recommendations.</p>
-<h2 id="style">Style Guide<a class="headerlink" href="#style" title="Permalink">¶</a></h2>
-<p>When writing or editing documentation, please follow the conventions in
-our <a href="style-guide.html">Documentation Style Guide</a>. It covers markup,
-prose style, and formatting standards.</p>
<h2 id="ml">The Mailing List<a class="headerlink" href="#ml" title="Permalink">¶</a></h2>
<p>All discussion about the docs project happens on
<code>[email protected]</code>. To subscribe, send email to
@@ -140,23 +119,15 @@ and follow the instructions in the reply.</p>
<a href="https://lists.apache.org/[email protected]">lists.apache.org</a>.</p>
<p>If you're not subscribed, your messages may still be moderated through
if they're on-topic.</p>
-<h2 id="translate">Translate the Documentation<a class="headerlink" href="#translate" title="Permalink">¶</a></h2>
-<p>The documentation is available in several languages, but many
-translations are incomplete or out of date. If you're fluent in a
-non-English language, we'd welcome your help. See our
-<a href="translations.html">translation guide</a> to get started, and check the
-<a href="avail_translations.html">translation status</a> to see what's needed.</p>
-<p>Please <a href="#ml">introduce yourself on the mailing list</a> before you begin so
-other translators can coordinate with you.</p>
+<h2 id="irc">IRC<a class="headerlink" href="#irc" title="Permalink">¶</a></h2>
+<p>You can find us in <strong>#httpd</strong> on <a href="https://libera.chat/">irc.libera.chat</a>.
+Drop in if you have quick questions or want to chat with other
+contributors in real time.</p>
<h2 id="docs">Where Are the Docs?<a class="headerlink" href="#docs" title="Permalink">¶</a></h2>
<ul>
<li><a href="../docs/2.4/">Version 2.4</a> (current stable release)</li>
<li><a href="../docs/trunk/">Trunk / Development</a> (next version in progress)</li>
</ul>
-<h2 id="contributors">Contributors<a class="headerlink" href="#contributors" title="Permalink">¶</a></h2>
-<p>The Apache HTTP Server documentation is the product of many people's
-work over many years. See the <a href="contributors.html">contributors page</a>
-for the full list — and we hope to add your name there soon.</p>
<!-- FOOTER -->
<div id="footer">
diff --git a/output/docs-project/svn.html b/output/docs-project/svn.html
index f5fe0c7..a4be654 100644
--- a/output/docs-project/svn.html
+++ b/output/docs-project/svn.html
@@ -114,6 +114,35 @@ svn checkout https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/docs ht
</code></pre>
<p>This gives you a lighter checkout, though you won't have the full source
tree for context.</p>
+<h2 id="repository-layout">Repository Layout<a class="headerlink" href="#repository-layout" title="Permalink">¶</a></h2>
+<p>Once you have a checkout, you'll find the documentation source under
+<code>docs/manual/</code>. Here's what lives where:</p>
+<ul>
+<li><strong><code>mod/</code></strong> — module reference pages (one <code>.xml</code> per module)</li>
+<li><strong><code>howto/</code></strong> — tutorial-style how-to guides</li>
+<li><strong><code>vhosts/</code></strong> — virtual host documentation</li>
+<li><strong><code>rewrite/</code></strong> — mod_rewrite guide and recipes</li>
+<li><strong><code>misc/</code></strong> — miscellaneous reference pages</li>
+<li><strong><code>faq/</code></strong> — frequently asked questions</li>
+<li><strong><code>ssl/</code></strong> — SSL/TLS documentation</li>
+<li><strong><code>programs/</code></strong> — httpd support programs documentation</li>
+<li><strong><code>style/</code></strong> — DTD, XSL, CSS (build system — don't edit unless you
+know what you're doing)</li>
+<li><strong><code>.xml</code> files</strong> — the source you edit</li>
+<li><strong><code>.xml.meta</code></strong> — auto-generated metadata (don't edit)</li>
+<li><strong><code>.html.*</code> files</strong> — auto-generated HTML output (don't edit)</li>
+</ul>
+<h3 id="autogenerated">What's Auto-Generated?<a class="headerlink" href="#autogenerated" title="Permalink">¶</a></h3>
+<p>Several file types in the tree are build output — never edit these
+directly:</p>
+<ul>
+<li><strong><code>.html</code> and <code>.html.*</code> files</strong> — generated HTML output for each
+language. These are rebuilt from the <code>.xml</code> source.</li>
+<li><strong><code>.xml.meta</code> files</strong> — generated by the build system to track
+translation status and revision info.</li>
+<li><strong><code>allmodules.xml</code></strong> — auto-generated when adding new modules.</li>
+</ul>
+<p><strong>Only edit <code>.xml</code> source files.</strong> Everything else is derived from them.</p>
<h2 id="creating-a-patch">Creating a Patch<a class="headerlink" href="#creating-a-patch" title="Permalink">¶</a></h2>
<p>Once you have a checkout, the process is:</p>
<h3 id="1-update-your-checkout">1. Update Your Checkout<a class="headerlink" href="#1-update-your-checkout" title="Permalink">¶</a></h3>
diff --git a/output/docs-project/translations.html b/output/docs-project/translations.html
index 35a6f4f..df75860 100644
--- a/output/docs-project/translations.html
+++ b/output/docs-project/translations.html
@@ -153,10 +153,6 @@ without word spacing, like Chinese and Japanese.)</p>
<p>Send your completed file (or a patch) to <code>[email protected]</code>. A
committer will review it and add it to the repository. Over time, you
may gain commit access yourself.</p>
-<h2 id="keeping-translations-current">Keeping Translations Current<a class="headerlink" href="#keeping-translations-current" title="Permalink">¶</a></h2>
-<p>Once your initial translation is committed, you'll want to keep it up to
-date as the English source evolves. See
-<a href="goingfurther.html">Maintaining Translations</a> for a practical workflow.</p>
<h2 id="review-standards">Review Standards<a class="headerlink" href="#review-standards" title="Permalink">¶</a></h2>
<p>Because the development team can't easily verify non-English content, we
require that all translations be reviewed by another fluent speaker of
@@ -170,14 +166,80 @@ translator and the reviewer.</p>
</code></pre>
<p>The build system tracks the SVN revision of the equivalent English
version, so future translators know where to start updating.</p>
+<h2 id="maintaining">Maintaining Translations<a class="headerlink" href="#maintaining" title="Permalink">¶</a></h2>
+<p>Once your initial translation is committed, the ongoing work is keeping
+it up to date as the English source evolves. Here's a practical workflow
+for tracking changes and updating your translated files.</p>
+<h3 id="the-basic-idea">The Basic Idea<a class="headerlink" href="#the-basic-idea" title="Permalink">¶</a></h3>
+<p>The English documentation changes over time — bugs get fixed, features
+get documented, examples get improved. As a translator, you need to:</p>
+<ol>
+<li>Detect which English files have changed since you last translated</li>
+<li>See what specifically changed</li>
+<li>Apply the equivalent changes to your translated files</li>
+<li>Verify your work builds correctly</li>
+</ol>
+<h3 id="set-up-your-working-environment">Set Up Your Working Environment<a class="headerlink" href="#set-up-your-working-environment" title="Permalink">¶</a></h3>
+<p>Check out both active branches:</p>
+<pre><code>svn checkout https://svn.apache.org/repos/asf/httpd/httpd/trunk/docs httpd-trunk
+svn checkout https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/docs httpd-2.4
+</code></pre>
+<h3 id="track-changes-with-svn">Track Changes with SVN<a class="headerlink" href="#track-changes-with-svn" title="Permalink">¶</a></h3>
+<p>The simplest way to see what's changed since a known revision is
+<code>svn diff</code> between revisions. If you noted that you last synchronized
+your translation at revision 1900000, you can see all changes since then:</p>
+<pre><code>svn log -r 1900000:HEAD docs/manual/mod/mod_rewrite.xml
+svn diff -r 1900000:HEAD docs/manual/mod/mod_rewrite.xml
+</code></pre>
+<p><strong>Tip:</strong> Note the current revision number each time you finish updating
+a translation. Add it as a comment at the top of your translated file:</p>
+<pre><code><!-- English Revision: 1912345 -->
+</code></pre>
+<p>This makes it easy to check what's changed next time:</p>
+<pre><code>svn diff -r 1912345:HEAD docs/manual/mod/mod_rewrite.xml
+</code></pre>
+<h3 id="update-your-translation">Update Your Translation<a class="headerlink" href="#update-your-translation" title="Permalink">¶</a></h3>
+<p>With the diff output showing what changed in the English source, apply
+the equivalent changes to your translated file. Focus on:</p>
+<ul>
+<li>New paragraphs or sections that need translating</li>
+<li>Changed examples or directive descriptions</li>
+<li>Removed content that should also be removed from your translation</li>
+<li>Corrected technical information</li>
+</ul>
+<h3 id="verify-your-work">Verify Your Work<a class="headerlink" href="#verify-your-work" title="Permalink">¶</a></h3>
+<p>Build the docs to confirm your XML is valid and the output looks right:</p>
+<pre><code>cd docs/manual/build
+./build.sh validate-xml
+./build.sh <your-language-code>
+</code></pre>
+<p>Open the generated HTML in a browser to review the final result.</p>
+<h3 id="submit-your-updates">Submit Your Updates<a class="headerlink" href="#submit-your-updates" title="Permalink">¶</a></h3>
+<p>Send your updated files as a patch:</p>
+<pre><code>svn diff > translation-update.patch
+</code></pre>
+<p>Email the patch to <code>[email protected]</code>, or attach it to a
+<a href="https://bz.apache.org/bugzilla/">Bugzilla ticket</a>.</p>
+<h3 id="staying-in-sync">Staying in Sync<a class="headerlink" href="#staying-in-sync" title="Permalink">¶</a></h3>
+<p>A few habits that make maintenance easier:</p>
+<ul>
+<li><strong>Update regularly</strong> — small, frequent updates are much easier than
+catching up after months of changes.</li>
+<li><strong>Watch the commits list</strong> — subscribe to the svn commits to see
+documentation changes as they happen.</li>
+<li><strong>Coordinate with other translators</strong> — if there are multiple people
+working on your language, divide the work and communicate via the
+mailing list.</li>
+</ul>
+<h2 id="questions">Questions?<a class="headerlink" href="#questions" title="Permalink">¶</a></h2>
+<p>If you get stuck or have questions about translating or maintaining
+translations, reach out to <code>[email protected]</code>. We're happy to help.</p>
<h2 id="related-information">Related Information<a class="headerlink" href="#related-information" title="Permalink">¶</a></h2>
<ul>
<li><a href="docsformat.html">Documentation Format</a> — the XML format and how to
build HTML from it</li>
<li><a href="avail_translations.html">Translation Status</a> — what's been
translated and what's needed</li>
-<li><a href="goingfurther.html">Maintaining Translations</a> — keeping your work
-up to date</li>
</ul>
<!-- FOOTER -->