git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: jidanni@jidanni.org
Cc: git@vger.kernel.org, 507475@bugs.debian.org
Subject: Re: git-doc CSS dependent, breaks down in text browsers
Date: Thu, 11 Dec 2008 22:33:48 -0500	[thread overview]
Message-ID: <20081212033348.GA29663@coredump.intra.peff.net> (raw)
In-Reply-To: <87wse6zc9x.fsf@jidanni.org>

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

  reply	other threads:[~2008-12-12  3:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03  1:32 X-Debbugs-Cc didn't make it to git@vger.kernel.org jidanni
2008-12-11 20:29 ` git-doc CSS dependent, breaks down in text browsers jidanni
2008-12-12  3:33   ` Jeff King [this message]
2008-12-11 20:32 ` user-manual.html invalid HTML jidanni
2008-12-12  2:30   ` Jeff King
2008-12-12  2:47     ` jidanni
2010-08-20  5:04       ` Jonathan Nieder
2010-08-21  6:21         ` Jeff King
2010-08-22  7:23           ` Junio C Hamano
2009-01-08 19:36 ` X-Debbugs-Cc didn't make it to git@vger.kernel.org jidanni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081212033348.GA29663@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=507475@bugs.debian.org \
    --cc=git@vger.kernel.org \
    --cc=jidanni@jidanni.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).