E.g., pages look like
SYNOPSIS
git-config [<file-option>] [type] [-z|--null] name [value [value_regex]] git-config [<file-option>] [type] --add name
value git-config [<file-option>] [type] --replace-all name [value [value_regex]] git-config [<file-option>] [type] [-z|
--null] --get name [value_regex] git-config [<file-option>] [type] [-z|--null] --get-all name [value_regex] git-config...
Please see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507475 ,
which was supposed to be forwarded to git@vger.kernel.org but wasn't,
apparently.
The versions I build locally have:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
in each HTML file, which is added by asciidoc. Maybe the package you
are looking at was built with an older version of asciidoc that doesn't
do this (I don't actually know the history of this feature, but it seems
to me that this is something asciidoc should be doing, not git).
-Peff
JK> The versions I build locally have:
JK> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
JK> "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
JK> in each HTML file, which is added by asciidoc. Maybe the package you
JK> are looking at was built with an older version of asciidoc that doesn't
JK> do this (I don't actually know the history of this feature, but it seems
JK> to me that this is something asciidoc should be doing, not git).
JK> -Peff
OK, adding 507476@bugs.debian.org to the CCs.
From: Jeff King <hidden> Date: 2016-06-15 22:45:45
On Fri, Dec 12, 2008 at 04:29:14AM +0800, jidanni@jidanni.org wrote:
E.g., pages look like
SYNOPSIS
git-config [<file-option>] [type] [-z|--null] name [value [value_regex]] git-config [<file-option>] [type] --add name
value git-config [<file-option>] [type] --replace-all name [value [value_regex]] git-config [<file-option>] [type] [-z|
--null] --get name [value_regex] git-config [<file-option>] [type] [-z|--null] --get-all name [value_regex] git-config...
I think this is another asciidoc issue, as git merely specifies "verse"
format for this section. Probably the most friendly thing to do would be
to use
<pre class="verseblock-content">
instead of
<div class="verseblock-content">
so that non-CSS browsers fall back to preserving the line boundaries
(which is what is making it look so unbearable in your text browser).
But it is definitely something to be fixed in asciidoc, not in the git
documentation.
-Peff
From: Jonathan Nieder <hidden> Date: 2016-06-15 22:49:21
Hi,
Sorry for the long silence.
Jeff King wrote:
On Fri, Dec 12, 2008 at 04:32:15AM +0800, jidanni@jidanni.org wrote:
[user-manual.html lacks a !DOCTYPE declaration]
The versions I build locally have:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
in each HTML file, which is added by asciidoc. Maybe the package you
are looking at was built with an older version of asciidoc that doesn't
do this (I don't actually know the history of this feature, but it seems
to me that this is something asciidoc should be doing, not git).
It looks like the HTML for user-manual.html (unlike the reference
manual and other articles) is not generated by asciidoc after all;
instead, the rule in Documentation/Makefile uses xsltproc directly to
convert the asciidoc-generated XML to HTML.
Apparently the caller is supposed to set the
chunker.output.doctype-public parameter.
http://www.sagehill.net/docbookxsl/Chunking.html#OutputDoctype
Maybe something as simple as this would work.
-- 8< --
Subject: Documentation: set a !DOCTYPE for user manual
asciidoc already takes care of including a doctype for most of the
HTML documentation, but the user manual which is processed with
docbook-xsl directly lacks one (at least with Debian docbook-xsl
1.75.2+dfsg-5). This makes it harder to automatically validate the
HTML.
Reported-by: 積丹尼 <redacted>
Signed-off-by: Jonathan Nieder <redacted>
---
From: Jeff King <hidden> Date: 2016-06-15 22:49:21
On Fri, Aug 20, 2010 at 12:04:02AM -0500, Jonathan Nieder wrote:
quoted
The versions I build locally have:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
in each HTML file, which is added by asciidoc. Maybe the package you
are looking at was built with an older version of asciidoc that doesn't
do this (I don't actually know the history of this feature, but it seems
to me that this is something asciidoc should be doing, not git).
It looks like the HTML for user-manual.html (unlike the reference
manual and other articles) is not generated by asciidoc after all;
instead, the rule in Documentation/Makefile uses xsltproc directly to
convert the asciidoc-generated XML to HTML.
My asciidoc-generated pages are xhtml. We are using "html/docbook.xsl"
from docbook, and now "xhtml", so probably some form of html is right.
But is html4 strict right? With nothing else to go on, it seems a good
guess to me, but I'm wondering if you actually found the answer
somewhere.
Also, while testing your patch, I found and fixed the following buglet:
-- >8 --
Subject: [PATCH] docs: fix Makefile dependency for user manual
We use our custom xsl file to build the user manual, so make
sure we depend on it. We don't use it anywhere else, so we
can stick it straight in the rule.
Signed-off-by: Jeff King <redacted>
---
Documentation/Makefile | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)