{"thread":{"id":"12165","subject":"asciidoc 8","startedAt":"2008-02-18T00:23:27Z","lastAt":"2008-02-18T17:37:27Z","messageCount":3,"participants":["Wink Saville","Wincent Colaiuta"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"69065","messageId":"47B8CFFF.6090902@saville.com","threadId":"12165","inReplyTo":null,"subject":"asciidoc 8","fromName":"Wink Saville","fromEmail":"wink@saville.com","sentAt":"2008-02-18T00:23:27Z","receivedAt":"2008-02-18T00:23:27Z","isPatch":false,"sender":{"key":"wink@saville.com","avatar":"https://avatars.githubusercontent.com/u/1024284?v=4"},"body":"I ran into the asciidoc 8 issue where some of the docs don't\nget generated properly on my system with asciidoc 8.2.1.\n\nShould I just downgrade? What would be the \"best\" version\nto use.\n\nWink Saville\n"},{"id":"69095","messageId":"54BC65FA-F388-458F-9610-76B7C1413AD3@wincent.com","threadId":"12165","inReplyTo":"47B8CFFF.6090902@saville.com","subject":"Re: asciidoc 8","fromName":"Wincent Colaiuta","fromEmail":"win@wincent.com","sentAt":"2008-02-18T07:43:14Z","receivedAt":"2008-02-18T07:43:14Z","isPatch":false,"sender":{"key":"greg@hurrell.net","avatar":"https://avatars.githubusercontent.com/u/7074?v=4"},"body":"El 18/2/2008, a las 1:23, Wink Saville escribió:\n\n> I ran into the asciidoc 8 issue where some of the docs don't\n> get generated properly on my system with asciidoc 8.2.1.\n>\n> Should I just downgrade? What would be the \"best\" version\n> to use.\n\nI ran into problems with 8 a while ago, poked around for a while,  \ncouldn't find the cause of the problem, and so downgraded to the 7  \nseries (don't recall the exact version, but it was the last release in  \nthe 7 series). I figured this was just the simplest thing to do seeing  \nas the official manual page archives are generated with 7, as far as I  \nknow.\n\nI know that later a fix for the breakage that I was seeing was checked  \nin (see 5162e69), so in theory 8 should be fine now (at least, the  \nlatest version of it, but I see you're using an older version which  \nprobably isn't affected by the link problem). What problem are you  \nseeing? What version of Git are you using?\n\nCheers,\nWincent\n"},{"id":"69176","messageId":"47B9C257.5050109@saville.com","threadId":"12165","inReplyTo":"54BC65FA-F388-458F-9610-76B7C1413AD3@wincent.com","subject":"Re: asciidoc 8","fromName":"Wink Saville","fromEmail":"wink@saville.com","sentAt":"2008-02-18T17:37:27Z","receivedAt":"2008-02-18T17:37:27Z","isPatch":false,"sender":{"key":"wink@saville.com","avatar":"https://avatars.githubusercontent.com/u/1024284?v=4"},"body":"Wincent Colaiuta wrote:\n> El 18/2/2008, a las 1:23, Wink Saville escribió:\n>\n>> I ran into the asciidoc 8 issue where some of the docs don't\n>> get generated properly on my system with asciidoc 8.2.1.\n>>\n>> Should I just downgrade? What would be the \"best\" version\n>> to use.\n>\n> I ran into problems with 8 a while ago, poked around for a while, \n> couldn't find the cause of the problem, and so downgraded to the 7 \n> series (don't recall the exact version, but it was the last release in \n> the 7 series). I figured this was just the simplest thing to do seeing \n> as the official manual page archives are generated with 7, as far as I \n> know.\n>\n> I know that later a fix for the breakage that I was seeing was checked \n> in (see 5162e69), so in theory 8 should be fine now (at least, the \n> latest version of it, but I see you're using an older version which \n> probably isn't affected by the link problem). What problem are you \n> seeing? What version of Git are you using?\n>\n> Cheers,\n> Wincent\n>\n>\n>\nI'm seeing the missing \"+\" problem which, after reading INSTALL, was \nfixed by adding\nASCIIDOC8=YesPlease to my command line. But after doing that I was still \nseeing .ft C like\nthis:\n\n           .ft C\n                   URL: one of the above URL format\n                   Push: <refspec>\n                   Pull: <refspec>\n\n           .ft\n\nwhere \"<pre>\" blocks in the html documentation show up. I was first \nseeing the problems\nwith git 1.5.4 and then yesterday built 1.5.4.2 and still have the above \nproblem.\n\nWink Saville\n"}]}