Le 19/08/2020 à 09:47, Joe Orton a écrit :
On Wed, Aug 19, 2020 at 08:36:02AM +0100, Joe Orton wrote:
On Tue, Aug 18, 2020 at 07:08:21AM -0400, Eric Covener wrote:
On Tue, Aug 18, 2020 at 6:34 AM Joe Orton <[email protected]> wrote:

On Tue, Jul 28, 2020 at 07:32:01AM -0400, Eric Covener wrote:
FYI I am seeing if I can coordinate with Humbedooh to change all the
generated files without one of those 17-part commit threads.
But I will probably just commit in the next few hours either way.

Does this still need to be done for trunk?  I'm kind of lost here (as
usual with the docs), but running "./build.sh all" in trunk gives me a
tonne of *.html.en.utf8 files.

I have docs/manual/build at r1880369

Should we do a mass "svn mv" for .html.en to .html.en.utf8?

yes sorry. It looks nearly as noisy in the commit when I tested it but
I did chat with Daniel and he said just bite the bullet and don't
fiddle around with the mailing list.

Thanks & no worries.  The public /docs/trunk/ content still seems to be
working so I'm hoping I haven't completely broken everything:

r1880980 - magic bootstrap step needed to regenerate the typemaps correctly
r1880982 - surely the longest I have ever seen svn commit run for

... in fact in r1880982 I only ran "./build.sh en" I think.

And I am still seeing a big diff changing ISO-8859-1 characters into
HTML entities for other languages when re-running "build.sh all":

$ svn diff vhosts/index.html.de  | head
Index: vhosts/index.html.de
===================================================================
--- vhosts/index.html.de        (revision 1880979)
+++ vhosts/index.html.de        (working copy)
@@ -23,59 +23,59 @@
  <div id="path">
  <a href="http://www.apache.org/";>Apache</a> &gt; <a href="http://httpd.apache.org/";>HTTP-Server</a> &gt; <a 
href="http://httpd.apache.org/docs/";>Dokumentation</a> &gt; <a href="../">Version 2.5</a></div><div id="page-content"><div 
id="preamble"><h1>Apache-Dokumentation zu virtuellen Hosts</h1>
  <div class="toplang">
-<p><span>Verf�gbare Sprachen: </span><a href="../de/vhosts/" 
title="Deutsch">&nbsp;de&nbsp;</a> |
+<p><span>Verf&#252;gbare Sprachen: </span><a href="../de/vhosts/" 
title="Deutsch">&nbsp;de&nbsp;</a> |

FWIW, using:

$ $JAVA_HOME/bin/java -version
openjdk version "11.0.8" 2020-07-14
OpenJDK Runtime Environment 18.9 (build 11.0.8+10)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.8+10, mixed mode, sharing)

Stupid question, why do we need to change the suffix to .utf8 to convert
these files into UTF-8?

I don't think it is needed, just a matter of consistancy in naming.
See r1878788 to see the magic needed to concert to UTF-8 (without renaming files)

CJ



M       man/htdbm.1
M       manual/bind.html.de
M       manual/configuring.html.de
M       manual/glossary.html.de
M       manual/howto/htaccess.html.pt-br
M       manual/index.html.da
M       manual/index.html.de
M       manual/index.html.pt-br
M       manual/install.html.de
M       manual/invoking.html.de
M       manual/mod/core.html.de
M       manual/mod/core.html.es.utf8
M       manual/mod/core.html.ja.utf8
M       manual/mod/core.html.tr.utf8
M       manual/mod/directives.html.de
M       manual/mod/directives.html.ja.utf8
M       manual/mod/directives.html.ko.euc-kr
M       manual/mod/directives.html.tr.utf8
M       manual/mod/directives.html.zh-cn.utf8
M       manual/mod/index.html.de
M       manual/mod/mod_actions.html.de
M       manual/mod/mpm_common.html.de
M       manual/mod/mpm_winnt.html.de
M       manual/mod/prefork.html.de
M       manual/mod/quickreference.html.de
M       manual/mod/quickreference.html.ja.utf8
M       manual/mod/quickreference.html.ko.euc-kr
M       manual/mod/quickreference.html.tr.utf8
M       manual/mod/quickreference.html.zh-cn.utf8
M       manual/mod/worker.html.de
M       manual/mpm.html.de
M       manual/new_features_2_0.html.de
M       manual/new_features_2_0.html.pt-br
M       manual/new_features_2_2.html.pt-br
M       manual/sitemap.html.de
M       manual/stopping.html.de
M       manual/vhosts/index.html.de
M       manual/vhosts/name-based.html.de



Reply via email to