{"thread":{"id":"32356","subject":"Prebuilt man pages on Google code","startedAt":"2012-12-16T16:28:27Z","lastAt":"2012-12-18T23:03:07Z","messageCount":2,"participants":["John Keeping","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"204968","messageId":"20121216162827.GA22351@river.lan","threadId":"32356","inReplyTo":null,"subject":"Prebuilt man pages on Google code","fromName":"John Keeping","fromEmail":"john@keeping.me.uk","sentAt":"2012-12-16T16:28:27Z","receivedAt":"2012-12-16T16:28:27Z","isPatch":false,"sender":{"key":"john@keeping.me.uk","avatar":"https://avatars.githubusercontent.com/u/1702081?v=4"},"body":"While investigating Asciidoc's quoting in this thread [1], I noticed\nthat my system man pages don't display Asciidoc double quoted text\ncorrectly.\n\n[1] http://article.gmane.org/gmane.comp.version-control.git/211533\n\nFor example in git-fast-import(1):\n\n   Here <name> is the person’s display name (for example `Com M Itter'')\n   and `<email> is the person’s email address (`cm@example.com''). `LT\n   and GT are the literal less-than (\\x3c) and greater-than (\\x3e)\n   symbols.\n\nIt turns out that Gentoo installs the man pages from git-core on Google\ncode, and the error can be seen in the \"source\" there [2].\n\n[2] http://code.google.com/p/git-manpages/source/browse/man1/git-fast-import.1#379\n\nWhen I generate man pages here, I get paired quotes (\\u201C and \\u201D):\n\n   Here <name> is the person’s display name (for example “Com M Itter”)\n   and <email> is the person’s email address (“cm@example.com”). LT and\n   GT are the literal less-than (\\x3c) and greater-than (\\x3e) symbol\n\nI can't see any configuration option that could cause this difference,\nso I assume it must be caused by some particular tool version on the\nmachine used to generate these man pages.\n\nIf the output is a side-effect of avoiding non-ASCII characters, is is\nuseful to do something like this (with appropriate Makefile support)?\n\ndiff --git a/Documentation/asciidoc.conf b/Documentation/asciidoc.conf\nindex 1273a85..6655ec7 100644\n--- a/Documentation/asciidoc.conf\n+++ b/Documentation/asciidoc.conf\n@@ -89,6 +89,16 @@ template::[header-declarations]\n endif::backend-docbook[]\n endif::doctype-manpage[]\n \n+ifdef::doctype-manpage[]\n+ifdef::git-asciidoc-man-ascii[]\n+[attributes]\n+lsquo=&#39;\n+rsquo=&#39;\n+ldquo=&#34;\n+rdquo=&#34;\n+endif::git-asciidoc-man-ascii[]\n+endif::doctype-manpage[]\n+\n ifdef::backend-xhtml11[]\n [attributes]\n git-relative-html-prefix=\n"},{"id":"205165","messageId":"7vhanjdkus.fsf@alter.siamese.dyndns.org","threadId":"32356","inReplyTo":"20121216162827.GA22351@river.lan","subject":"Re: Prebuilt man pages on Google code","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-12-18T23:03:07Z","receivedAt":"2012-12-18T23:03:07Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"John Keeping <john@keeping.me.uk> writes:\n\n> While investigating Asciidoc's quoting in this thread [1], I noticed\n> that my system man pages don't display Asciidoc double quoted text\n> correctly.\n> ...\n> I can't see any configuration option that could cause this difference,\n> so I assume it must be caused by some particular tool version on the\n> machine used to generate these man pages.\n\nYeah, Debian ships with a tad older one, and I've been using\nasciidoc 8.5.2 on my primary box.\n\nI'm experimenting a newer one from the latest tarball (asciidoc\n8.6.8) and the result looks promising.  If everything goes smoothly,\nI'll probably do another -rc before the final 1.8.1 release goes out\nwith the new asciidoc, but no promises (yet).\n\nThanks.\n"}]}