{"thread":{"id":"16798","subject":"[PATCH] Documentation: fix typos, grammar, asciidoc syntax","startedAt":"2008-12-19T12:14:18Z","lastAt":"2008-12-20T21:37:28Z","messageCount":9,"participants":["Markus Heidelberg","Junio C Hamano","Teemu Likonen"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"98351","messageId":"200812191314.19302.markus.heidelberg@web.de","threadId":"16798","inReplyTo":null,"subject":"[PATCH] Documentation: fix typos, grammar, asciidoc syntax","fromName":"Markus Heidelberg","fromEmail":"markus.heidelberg@web.de","sentAt":"2008-12-19T12:14:18Z","receivedAt":"2008-12-19T12:14:18Z","isPatch":true,"sender":{"key":"markus.heidelberg@web.de","avatar":"https://avatars.githubusercontent.com/u/6334512?v=4"},"body":"\nSigned-off-by: Markus Heidelberg <markus.heidelberg@web.de>\n---\n Documentation/diff-format.txt         |    2 +-\n Documentation/diff-generate-patch.txt |    6 +++---\n Documentation/git-commit.txt          |    2 +-\n Documentation/git-diff-tree.txt       |    4 ++--\n Documentation/git-mailinfo.txt        |    2 +-\n Documentation/git-receive-pack.txt    |    4 ++--\n Documentation/git-reflog.txt          |    4 ++--\n Documentation/git-show-branch.txt     |    4 ++--\n Documentation/git-submodule.txt       |    2 +-\n Documentation/git-update-index.txt    |    8 ++++----\n Documentation/gitcore-tutorial.txt    |    8 ++++----\n Documentation/gitk.txt                |    4 ++--\n Documentation/i18n.txt                |    4 ++--\n 13 files changed, 27 insertions(+), 27 deletions(-)\n\ndiff --git a/Documentation/diff-format.txt b/Documentation/diff-format.txt\nindex aafd3a3..1eeb1c7 100644\n--- a/Documentation/diff-format.txt\n+++ b/Documentation/diff-format.txt\n@@ -58,7 +58,7 @@ Possible status letters are:\n be committed)\n - X: \"unknown\" change type (most probably a bug, please report it)\n \n-Status letters C and M are always followed by a score (denoting the\n+Status letters C and R are always followed by a score (denoting the\n percentage of similarity between the source and target of the move or\n copy), and are the only ones to be so.\n \ndiff --git a/Documentation/diff-generate-patch.txt b/Documentation/diff-generate-patch.txt\nindex 517e1eb..0f25ba7 100644\n--- a/Documentation/diff-generate-patch.txt\n+++ b/Documentation/diff-generate-patch.txt\n@@ -143,15 +143,15 @@ different from it.\n \n A `-` character in the column N means that the line appears in\n fileN but it does not appear in the result.  A `+` character\n-in the column N means that the line appears in the last file,\n+in the column N means that the line appears in the result,\n and fileN does not have that line (in other words, the line was\n added, from the point of view of that parent).\n \n In the above example output, the function signature was changed\n from both files (hence two `-` removals from both file1 and\n file2, plus `++` to mean one line that was added does not appear\n-in either file1 nor file2).  Also two other lines are the same\n-from file1 but do not appear in file2 (hence prefixed with ` +`).\n+in either file1 nor file2).  Also eight other lines are the same\n+from file1 but do not appear in file2 (hence prefixed with `{plus}`).\n \n When shown by `git diff-tree -c`, it compares the parents of a\n merge commit with the merge result (i.e. file1..fileN are the\ndiff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt\nindex 6203461..b5d81be 100644\n--- a/Documentation/git-commit.txt\n+++ b/Documentation/git-commit.txt\n@@ -166,7 +166,7 @@ FROM UPSTREAM REBASE\" section in linkgit:git-rebase[1].)\n \t'git-commit' if any paths are given on the command line,\n \tin which case this option can be omitted.\n \tIf this option is specified together with '--amend', then\n-\tno paths need be specified, which can be used to amend\n+\tno paths need to be specified, which can be used to amend\n \tthe last commit without committing changes that have\n \talready been staged.\n \ndiff --git a/Documentation/git-diff-tree.txt b/Documentation/git-diff-tree.txt\nindex 5d48664..23b7abd 100644\n--- a/Documentation/git-diff-tree.txt\n+++ b/Documentation/git-diff-tree.txt\n@@ -43,7 +43,7 @@ include::diff-options.txt[]\n \tshow tree entry itself as well as subtrees.  Implies -r.\n \n --root::\n-\tWhen '--root' is specified the initial commit will be showed as a big\n+\tWhen '--root' is specified the initial commit will be shown as a big\n \tcreation event. This is equivalent to a diff against the NULL tree.\n \n --stdin::\n@@ -63,7 +63,7 @@ and terminated by a newline) is printed before the difference.  When\n comparing commits, the ID of the first (or only) commit, followed by a\n newline, is printed.\n +\n-The following flags further affects the behavior when comparing\n+The following flags further affect the behavior when comparing\n commits (but not trees).\n \n -m::\ndiff --git a/Documentation/git-mailinfo.txt b/Documentation/git-mailinfo.txt\nindex 31eccea..8d95aaa 100644\n--- a/Documentation/git-mailinfo.txt\n+++ b/Documentation/git-mailinfo.txt\n@@ -13,7 +13,7 @@ SYNOPSIS\n \n DESCRIPTION\n -----------\n-Reading a single e-mail message from the standard input, and\n+Reads a single e-mail message from the standard input, and\n writes the commit log message in <msg> file, and the patches in\n <patch> file.  The author name, e-mail and e-mail subject are\n written out to the standard output to be used by 'git-am'\ndiff --git a/Documentation/git-receive-pack.txt b/Documentation/git-receive-pack.txt\nindex 6b2f8c4..514f03c 100644\n--- a/Documentation/git-receive-pack.txt\n+++ b/Documentation/git-receive-pack.txt\n@@ -86,7 +86,7 @@ post-receive Hook\n -----------------\n After all refs were updated (or attempted to be updated), if any\n ref update was successful, and if $GIT_DIR/hooks/post-receive\n-file exists and is executable, it will be invoke once with no\n+file exists and is executable, it will be invoked once with no\n parameters.  The standard input of the hook will be one line\n for each successfully updated ref:\n \n@@ -133,7 +133,7 @@ post-update Hook\n ----------------\n After all other processing, if at least one ref was updated, and\n if $GIT_DIR/hooks/post-update file exists and is executable, then\n-post-update will called with the list of refs that have been updated.\n+post-update will be called with the list of refs that have been updated.\n This can be used to implement any repository wide cleanup tasks.\n \n The exit code from this hook invocation is ignored; the only thing\ndiff --git a/Documentation/git-reflog.txt b/Documentation/git-reflog.txt\nindex d99236e..7f7a544 100644\n--- a/Documentation/git-reflog.txt\n+++ b/Documentation/git-reflog.txt\n@@ -28,7 +28,7 @@ updated.  This command is to manage the information recorded in it.\n \n The subcommand \"expire\" is used to prune older reflog entries.\n Entries older than `expire` time, or entries older than\n-`expire-unreachable` time and are not reachable from the current\n+`expire-unreachable` time and not reachable from the current\n tip, are removed from the reflog.  This is typically not used\n directly by the end users -- instead, see linkgit:git-gc[1].\n \n@@ -71,7 +71,7 @@ them.\n \twhich in turn defaults to 90 days.\n \n --expire-unreachable=<time>::\n-\tEntries older than this time and are not reachable from\n+\tEntries older than this time and not reachable from\n \tthe current tip of the branch are pruned.  Without the\n \toption it is taken from configuration\n \t`gc.reflogExpireUnreachable`, which in turn defaults to\ndiff --git a/Documentation/git-show-branch.txt b/Documentation/git-show-branch.txt\nindex d3f2588..8277577 100644\n--- a/Documentation/git-show-branch.txt\n+++ b/Documentation/git-show-branch.txt\n@@ -30,7 +30,7 @@ OPTIONS\n -------\n <rev>::\n \tArbitrary extended SHA1 expression (see linkgit:git-rev-parse[1])\n-\tthat typically names a branch HEAD or a tag.\n+\tthat typically names a branch head or a tag.\n \n <glob>::\n \tA glob pattern that matches branch or tag names under\n@@ -172,7 +172,7 @@ only the primary branches.  In addition, if you happen to be on\n your topic branch, it is shown as well.\n \n ------------\n-$ git show-branch --reflog='10,1 hour ago' --list master\n+$ git show-branch --reflog=\"10,1 hour ago\" --list master\n ------------\n \n shows 10 reflog entries going back from the tip as of 1 hour ago.\ndiff --git a/Documentation/git-submodule.txt b/Documentation/git-submodule.txt\nindex babaa9b..2f207fb 100644\n--- a/Documentation/git-submodule.txt\n+++ b/Documentation/git-submodule.txt\n@@ -87,7 +87,7 @@ use by subsequent users cloning the superproject. If the URL is\n given relative to the superproject's repository, the presumption\n is the superproject and submodule repositories will be kept\n together in the same relative location, and only the\n-superproject's URL need be provided: git-submodule will correctly\n+superproject's URL needs to be provided: git-submodule will correctly\n locate the submodule using the relative URL in .gitmodules.\n \n status::\ndiff --git a/Documentation/git-update-index.txt b/Documentation/git-update-index.txt\nindex 1d9d81a..25e0bbe 100644\n--- a/Documentation/git-update-index.txt\n+++ b/Documentation/git-update-index.txt\n@@ -55,7 +55,7 @@ OPTIONS\n         default behavior is to error out.  This option makes\n \t'git-update-index' continue anyway.\n \n---ignore-submodules:\n+--ignore-submodules::\n \tDo not try to update submodules.  This option is only respected\n \twhen passed before --refresh.\n \n@@ -78,9 +78,9 @@ OPTIONS\n \n --assume-unchanged::\n --no-assume-unchanged::\n-\tWhen these flags are specified, the object name recorded\n+\tWhen these flags are specified, the object names recorded\n \tfor the paths are not updated.  Instead, these options\n-\tsets and unsets the \"assume unchanged\" bit for the\n+\tset and unset the \"assume unchanged\" bit for the\n \tpaths.  When the \"assume unchanged\" bit is on, git stops\n \tchecking the working tree files for possible\n \tmodifications, so you need to manually unset the bit to\n@@ -122,7 +122,7 @@ you will need to handle the situation manually.\n \t'git-update-index' refuses an attempt to add `path/file`.\n \tSimilarly if a file `path/file` exists, a file `path`\n \tcannot be added.  With --replace flag, existing entries\n-\tthat conflicts with the entry being added are\n+\tthat conflict with the entry being added are\n \tautomatically removed with warning messages.\n \n --stdin::\ndiff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt\nindex 96bf353..da8fa44 100644\n--- a/Documentation/gitcore-tutorial.txt\n+++ b/Documentation/gitcore-tutorial.txt\n@@ -999,8 +999,8 @@ Fast forward\n  2 files changed, 2 insertions(+), 0 deletions(-)\n ----------------\n \n-Because your branch did not contain anything more than what are\n-already merged into the `master` branch, the merge operation did\n+Because your branch did not contain anything more than what had\n+already been merged into the `master` branch, the merge operation did\n not actually do a merge. Instead, it just updated the top of\n the tree of your branch to that of the `master` branch. This is\n often called 'fast forward' merge.\n@@ -1353,7 +1353,7 @@ $ GIT_DIR=my-git.git git init\n ------------\n \n Make sure this directory is available for others you want your\n-changes to be pulled by via the transport of your choice. Also\n+changes to be pulled via the transport of your choice. Also\n you need to make sure that you have the 'git-receive-pack'\n program on the `$PATH`.\n \n@@ -1512,7 +1512,7 @@ You can repack this private repository whenever you feel like.\n 6. Push your changes to the public repository, and announce it\n    to the public.\n \n-7. Every once in a while, \"git-repack\" the public repository.\n+7. Every once in a while, 'git-repack' the public repository.\n    Go back to step 5. and continue working.\n \n \ndiff --git a/Documentation/gitk.txt b/Documentation/gitk.txt\nindex 317f631..4673a75 100644\n--- a/Documentation/gitk.txt\n+++ b/Documentation/gitk.txt\n@@ -21,7 +21,7 @@ git repository.\n \n OPTIONS\n -------\n-To control which revisions to shown, the command takes options applicable to\n+To control which revisions to show, the command takes options applicable to\n the 'git-rev-list' command (see linkgit:git-rev-list[1]).\n This manual page describes only the most\n frequently used options.\n@@ -80,7 +80,7 @@ Examples\n --------\n gitk v2.6.12.. include/scsi drivers/scsi::\n \n-\tShow as the changes since version 'v2.6.12' that changed any\n+\tShow the changes since version 'v2.6.12' that changed any\n \tfile in the include/scsi or drivers/scsi subdirectories\n \n gitk --since=\"2 weeks ago\" \\-- gitk::\ndiff --git a/Documentation/i18n.txt b/Documentation/i18n.txt\nindex 2cdacd9..708da6c 100644\n--- a/Documentation/i18n.txt\n+++ b/Documentation/i18n.txt\n@@ -7,11 +7,11 @@ At the core level, git is character encoding agnostic.\n    to be what lstat(2) and creat(2) accepts.  There is no such\n    thing as pathname encoding translation.\n \n- - The contents of the blob objects are uninterpreted sequence\n+ - The contents of the blob objects are uninterpreted sequences\n    of bytes.  There is no encoding translation at the core\n    level.\n \n- - The commit log messages are uninterpreted sequence of non-NUL\n+ - The commit log messages are uninterpreted sequences of non-NUL\n    bytes.\n \n Although we encourage that the commit log messages are encoded\n-- \n1.6.1.rc3.27.gf650d1\n"},{"id":"98416","messageId":"7v3agj1gvp.fsf@gitster.siamese.dyndns.org","threadId":"16798","inReplyTo":"200812191314.19302.markus.heidelberg@web.de","subject":"Re: [PATCH] Documentation: fix typos, grammar, asciidoc syntax","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-12-20T06:48:42Z","receivedAt":"2008-12-20T06:48:42Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Markus Heidelberg <markus.heidelberg@web.de> writes:\n\n> Signed-off-by: Markus Heidelberg <markus.heidelberg@web.de>\n> ---\n>  Documentation/diff-format.txt         |    2 +-\n>  Documentation/diff-generate-patch.txt |    6 +++---\n>  Documentation/git-commit.txt          |    2 +-\n>  Documentation/git-diff-tree.txt       |    4 ++--\n>  Documentation/git-mailinfo.txt        |    2 +-\n>  Documentation/git-receive-pack.txt    |    4 ++--\n>  Documentation/git-reflog.txt          |    4 ++--\n>  Documentation/git-show-branch.txt     |    4 ++--\n>  Documentation/git-submodule.txt       |    2 +-\n>  Documentation/git-update-index.txt    |    8 ++++----\n>  Documentation/gitcore-tutorial.txt    |    8 ++++----\n>  Documentation/gitk.txt                |    4 ++--\n>  Documentation/i18n.txt                |    4 ++--\n>  13 files changed, 27 insertions(+), 27 deletions(-)\n\nWhew, quite a lot of typos there are.\n\n> @@ -172,7 +172,7 @@ only the primary branches.  In addition, if you happen to be on\n>  your topic branch, it is shown as well.\n>  \n>  ------------\n> -$ git show-branch --reflog='10,1 hour ago' --list master\n> +$ git show-branch --reflog=\"10,1 hour ago\" --list master\n>  ------------\n\nIs this just a personal taste, or a correction to typography?\n\nOther than this one, I did not find anything else in your patch that\nlooked iffy.  Thanks for lending a good set of eyeballs.\n"},{"id":"98438","messageId":"200812201418.38707.markus.heidelberg@web.de","threadId":"16798","inReplyTo":"7v3agj1gvp.fsf@gitster.siamese.dyndns.org","subject":"Re: [PATCH] Documentation: fix typos, grammar, asciidoc syntax","fromName":"Markus Heidelberg","fromEmail":"markus.heidelberg@web.de","sentAt":"2008-12-20T13:18:38Z","receivedAt":"2008-12-20T13:18:38Z","isPatch":true,"sender":{"key":"markus.heidelberg@web.de","avatar":"https://avatars.githubusercontent.com/u/6334512?v=4"},"body":"Junio C Hamano, 20.12.2008:\n> Markus Heidelberg <markus.heidelberg@web.de> writes:\n> \n> > @@ -172,7 +172,7 @@ only the primary branches.  In addition, if you happen to be on\n> >  your topic branch, it is shown as well.\n> >  \n> >  ------------\n> > -$ git show-branch --reflog='10,1 hour ago' --list master\n> > +$ git show-branch --reflog=\"10,1 hour ago\" --list master\n> >  ------------\n> \n> Is this just a personal taste, or a correction to typography?\n\nWhen using single quotes, the manpage displayed backticks. I don't know\nhow to obtain single quotes in the manpage, if this is preferred. The\nHTML page worked though: single quotes were translated to single quotes,\ndouble quotes to double quotes.\n\n> Other than this one, I did not find anything else in your patch that\n> looked iffy.  Thanks for lending a good set of eyeballs.\n\nThanks, this happens when reading a lot of documentation :)\n"},{"id":"98447","messageId":"7v3agiy5gs.fsf@gitster.siamese.dyndns.org","threadId":"16798","inReplyTo":"200812201418.38707.markus.heidelberg@web.de","subject":"Re: [PATCH] Documentation: fix typos, grammar, asciidoc syntax","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-12-20T20:08:51Z","receivedAt":"2008-12-20T20:08:51Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Markus Heidelberg <markus.heidelberg@web.de> writes:\n\n> Junio C Hamano, 20.12.2008:\n>> Markus Heidelberg <markus.heidelberg@web.de> writes:\n>> \n>> > @@ -172,7 +172,7 @@ only the primary branches.  In addition, if you happen to be on\n>> >  your topic branch, it is shown as well.\n>> >  \n>> >  ------------\n>> > -$ git show-branch --reflog='10,1 hour ago' --list master\n>> > +$ git show-branch --reflog=\"10,1 hour ago\" --list master\n>> >  ------------\n>> \n>> Is this just a personal taste, or a correction to typography?\n>\n> When using single quotes, the manpage displayed backticks.\n\nIt does not seem to do that to me:\n\n    $ git help show-branch | grep 10,1 | od -bc\n    0000000 040 040 040 040 040 040 040 040 040 040 044 040 147 151 164 040\n                                                      $       g   i   t\n    0000020 163 150 157 167 055 142 162 141 156 143 150 040 055 055 162 145\n              s   h   o   w   -   b   r   a   n   c   h       -   -   r   e\n    0000040 146 154 157 147 075 342 200 231 061 060 054 061 040 150 157 165\n              f   l   o   g   = 342 200 231   1   0   ,   1       h   o   u\n    0000060 162 040 141 147 157 342 200 231 040 055 055 154 151 163 164 040\n              r       a   g   o 342 200 231       -   -   l   i   s   t\n    0000100 155 141 163 164 145 162 012\n              m   a   s   t   e   r  \\n\n\nIt does not use ASCII single quote ' (\\047) but the result still does\nrender well enough to keep anybody who are typing, following the printed\nexamples, from mistaking it from a backquote:\n\n    http://pics.livejournal.com/gitster/pic/00009pk0/g6\n\nBut in this particular case, because sq/dq does not make any difference to\nthe example, I am Ok to change it to dq.  But I suspect there are many\nother places that do need to use sq in examples, so...\n"},{"id":"98454","messageId":"87tz8yponl.fsf@iki.fi","threadId":"16798","inReplyTo":"7v3agiy5gs.fsf@gitster.siamese.dyndns.org","subject":"Re: [PATCH] Documentation: fix typos, grammar, asciidoc syntax","fromName":"Teemu Likonen","fromEmail":"tlikonen@iki.fi","sentAt":"2008-12-20T20:39:10Z","receivedAt":"2008-12-20T20:39:10Z","isPatch":true,"sender":{"key":"tlikonen@iki.fi","avatar":null},"body":"Junio C Hamano (2008-12-20 12:08 -0800) wrote:\n\n> Markus Heidelberg <markus.heidelberg@web.de> writes:\n>\n>> Junio C Hamano, 20.12.2008:\n>>> Markus Heidelberg <markus.heidelberg@web.de> writes:\n\n>>> > -$ git show-branch --reflog='10,1 hour ago' --list master\n>>> > +$ git show-branch --reflog=\"10,1 hour ago\" --list master\n\n>>> Is this just a personal taste, or a correction to typography?\n>>\n>> When using single quotes, the manpage displayed backticks.\n>\n> It does not seem to do that to me:\n\nThe single quote (') in asciidoc turns into \\' in the man page\ntypesetting language and its meaning is acute accent (´, U+00B4). In\nAscii-only environment \\' is displayed as a single quote but it is still\nlogically an acute accent. For example, my UTF-8 terminals as well as\nPostscript output (man -Tps) display \\' as acute accent.\n\nTo get the logical single quote the man page source should contain \\(aq\nor \\[aq] . Don't know how to make asciidoc do this.\n"},{"id":"98456","messageId":"200812202202.57159.markus.heidelberg@web.de","threadId":"16798","inReplyTo":"87tz8yponl.fsf@iki.fi","subject":"Re: [PATCH] Documentation: fix typos, grammar, asciidoc syntax","fromName":"Markus Heidelberg","fromEmail":"markus.heidelberg@web.de","sentAt":"2008-12-20T21:02:56Z","receivedAt":"2008-12-20T21:02:56Z","isPatch":true,"sender":{"key":"markus.heidelberg@web.de","avatar":"https://avatars.githubusercontent.com/u/6334512?v=4"},"body":"Teemu Likonen, 20.12.2008:\n> Junio C Hamano (2008-12-20 12:08 -0800) wrote:\n> \n> > Markus Heidelberg <markus.heidelberg@web.de> writes:\n> >\n> >> Junio C Hamano, 20.12.2008:\n> >>> Markus Heidelberg <markus.heidelberg@web.de> writes:\n> \n> >>> > -$ git show-branch --reflog='10,1 hour ago' --list master\n> >>> > +$ git show-branch --reflog=\"10,1 hour ago\" --list master\n> \n> >>> Is this just a personal taste, or a correction to typography?\n> >>\n> >> When using single quotes, the manpage displayed backticks.\n> >\n> > It does not seem to do that to me:\n> \n> The single quote (') in asciidoc turns into \\' in the man page\n> typesetting language and its meaning is acute accent (´, U+00B4).\n\nOh, right, it's not a backtick for me, but this acute accent. The other\ndirection downwards.\n"},{"id":"98457","messageId":"200812202213.45029.markus.heidelberg@web.de","threadId":"16798","inReplyTo":"7v3agiy5gs.fsf@gitster.siamese.dyndns.org","subject":"Re: [PATCH] Documentation: fix typos, grammar, asciidoc syntax","fromName":"Markus Heidelberg","fromEmail":"markus.heidelberg@web.de","sentAt":"2008-12-20T21:13:44Z","receivedAt":"2008-12-20T21:13:44Z","isPatch":true,"sender":{"key":"markus.heidelberg@web.de","avatar":"https://avatars.githubusercontent.com/u/6334512?v=4"},"body":"Junio C Hamano, 20.12.2008:\n> Markus Heidelberg <markus.heidelberg@web.de> writes:\n> \n> > Junio C Hamano, 20.12.2008:\n> >> Markus Heidelberg <markus.heidelberg@web.de> writes:\n> >> \n> >> > @@ -172,7 +172,7 @@ only the primary branches.  In addition, if you happen to be on\n> >> >  your topic branch, it is shown as well.\n> >> >  \n> >> >  ------------\n> >> > -$ git show-branch --reflog='10,1 hour ago' --list master\n> >> > +$ git show-branch --reflog=\"10,1 hour ago\" --list master\n> >> >  ------------\n> >> \n> >> Is this just a personal taste, or a correction to typography?\n> >\n> > When using single quotes, the manpage displayed backticks.\n> \n> It does not seem to do that to me:\n> \n>     $ git help show-branch | grep 10,1 | od -bc\n>     0000040 146 154 157 147 075 342 200 231 061 060 054 061 040 150 157 165\n>               f   l   o   g   = 342 200 231   1   0   ,   1       h   o   u\n\nI get this instead:\n      0000040 145 146 154 157 147 075 302 264 061 060 054 061 040 150 157 165\n                e   f   l   o   g   = 302 264   1   0   ,   1       h   o   u\n\n> It does not use ASCII single quote ' (\\047) but the result still does\n> render well enough to keep anybody who are typing, following the printed\n> examples, from mistaking it from a backquote:\n> \n>     http://pics.livejournal.com/gitster/pic/00009pk0/g6\n\nYes, I was wrong, it wasn't a backtick.\n"},{"id":"98458","messageId":"87d4fmpmte.fsf@iki.fi","threadId":"16798","inReplyTo":"87tz8yponl.fsf@iki.fi","subject":"Re: [PATCH] Documentation: fix typos, grammar, asciidoc syntax","fromName":"Teemu Likonen","fromEmail":"tlikonen@iki.fi","sentAt":"2008-12-20T21:18:53Z","receivedAt":"2008-12-20T21:18:53Z","isPatch":true,"sender":{"key":"tlikonen@iki.fi","avatar":null},"body":"Teemu Likonen (2008-12-20 22:39 +0200) wrote:\n\n> To get the logical single quote the man page source should contain \\(aq\n> or \\[aq] . Don't know how to make asciidoc do this.\n\nBut \\(aq seems to be groff-specific and not necessarily portable. Oh\nwell, quotation marks are really a mess in man pages. Some reference:\n\n    http://www.mail-archive.com/groff@gnu.org/msg04150.html\n\nBut char \" should be reliable anyway. It renders as Ascii double quote.\n"},{"id":"98459","messageId":"878wqaplyf.fsf@iki.fi","threadId":"16798","inReplyTo":"200812202213.45029.markus.heidelberg@web.de","subject":"Re: [PATCH] Documentation: fix typos, grammar, asciidoc syntax","fromName":"Teemu Likonen","fromEmail":"tlikonen@iki.fi","sentAt":"2008-12-20T21:37:28Z","receivedAt":"2008-12-20T21:37:28Z","isPatch":true,"sender":{"key":"tlikonen@iki.fi","avatar":null},"body":"Markus Heidelberg (2008-12-20 22:13 +0100) wrote:\n\n> Junio C Hamano, 20.12.2008:\n>>               f   l   o   g   = 342 200 231   1   0   ,   1       h   o   u\n                                   ^^^^^^^^^^^\n\nThis is $E2 $80 $99 in hex and it's the UTF-8 sequence for U+2019 RIGHT\nSINGLE QUOTATION MARK (’).\n\n> I get this instead:\n\n>                 e   f   l   o   g   = 302 264   1   0   ,   1       h   o   u\n                                        ^^^^^^^\n\nAnd this is $C2 $B4 in hex and it's U+00B4 ACUTE ACCENT (´) in UTF-8\nencoding. This is what I get too with groff, in terminal and PostScript.\nWeird that Junio is getting different output for \\' in the man page\nsource.\n\nBut this is nothing yet, Emacs' \"M-x woman\" renders them as _grave\naccents_ aka backticks (`, U+0060 GRAVE ACCENT). Nice.\n"}]}