From: Wink Saville <wink@saville.com>
To: Wincent Colaiuta <win@wincent.com>
Cc: git@vger.kernel.org
Subject: Re: asciidoc 8
Date: Mon, 18 Feb 2008 09:37:27 -0800 [thread overview]
Message-ID: <47B9C257.5050109@saville.com> (raw)
In-Reply-To: <54BC65FA-F388-458F-9610-76B7C1413AD3@wincent.com>
Wincent Colaiuta wrote:
> El 18/2/2008, a las 1:23, Wink Saville escribió:
>
>> I ran into the asciidoc 8 issue where some of the docs don't
>> get generated properly on my system with asciidoc 8.2.1.
>>
>> Should I just downgrade? What would be the "best" version
>> to use.
>
> I ran into problems with 8 a while ago, poked around for a while,
> couldn't find the cause of the problem, and so downgraded to the 7
> series (don't recall the exact version, but it was the last release in
> the 7 series). I figured this was just the simplest thing to do seeing
> as the official manual page archives are generated with 7, as far as I
> know.
>
> I know that later a fix for the breakage that I was seeing was checked
> in (see 5162e69), so in theory 8 should be fine now (at least, the
> latest version of it, but I see you're using an older version which
> probably isn't affected by the link problem). What problem are you
> seeing? What version of Git are you using?
>
> Cheers,
> Wincent
>
>
>
I'm seeing the missing "+" problem which, after reading INSTALL, was
fixed by adding
ASCIIDOC8=YesPlease to my command line. But after doing that I was still
seeing .ft C like
this:
.ft C
URL: one of the above URL format
Push: <refspec>
Pull: <refspec>
.ft
where "<pre>" blocks in the html documentation show up. I was first
seeing the problems
with git 1.5.4 and then yesterday built 1.5.4.2 and still have the above
problem.
Wink Saville
prev parent reply other threads:[~2008-02-18 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 0:23 asciidoc 8 Wink Saville
2008-02-18 7:43 ` Wincent Colaiuta
2008-02-18 17:37 ` Wink Saville [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47B9C257.5050109@saville.com \
--to=wink@saville.com \
--cc=git@vger.kernel.org \
--cc=win@wincent.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.