linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Peter Wu <peter@lekensteyn.nl>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Documentation: fix broken conversion
Date: Tue, 6 Jan 2015 09:14:38 +0800	[thread overview]
Message-ID: <54AB36FE.60508@cn.fujitsu.com> (raw)
In-Reply-To: <1420467009-11738-1-git-send-email-peter@lekensteyn.nl>


-------- Original Message --------
Subject: [PATCH] Documentation: fix broken conversion
From: Peter Wu <peter@lekensteyn.nl>
To: <linux-btrfs@vger.kernel.org>
Date: 2015年01月05日 22:10
> Fixes various formatting issues:
>
> Fixes quoting issues in various manpages. Before/After excerpts for
> mkfs.btrfs(8), btrfs-qgroup(8):
>
>      mkfs.btrfs [-A|--alloc-start '<alloc-start>']
>      mkfs.btrfs [-A|--alloc-start <alloc-start>]
>      id 0/<subvolume id>''
>      id 0/<subvolume id>
>      If multiple '<attr>'s is given, use comma to separate.
>      If multiple <attr>s is given, use comma to separate.
>
> The one that is most apparent is the removal of text in
> btrfs-subvolume(8) and others. Before/After:
>
>      list [options] [-G <value>] [-C <value>] [--sort=rootid,gen,ogen,path] <path>
>      list [options] [-G [+|-]<value>] [-C [+|-]<value>] [--sort=rootid,gen,ogen,path] <path>
>      create [-i <qgroupid>] <name>
>      create [-i <qgroupid>] [<dest>]<name>
Nice catch!
>
> This happens because `<foo>` was replaced by `'<foo>'` in the sed
> expression, which is then treated as a constrained quote. As a result,
> the `[...]` before the string gets interpreted as "quoted text
> attributes".
>
> In this patch, the sed expression is dropped and asciidoc is configured
> to recognize `<...>` as a unconstrained quoted string (such that
> `<attr>s` is correctly emphasized) and to avoid adding quotes in
> contexts where it is not needed.
>
> A remaining problem is that some texts (the one between brackets) do not
> add the emphasis for `<...>`.
IMHO, current implement in this patch is already good enough, although 
it is still not perfect,
but much much better than previous one and such missing of emphasize is 
acceptable.
> While this could be solved by replacing
> `[` and `]` with `&#91;` and `&#93;` using sed, it introduces formatting
> problems in btrfs-zero-log(8) because the context is ignored.
>
> Signed-off-by: Peter Wu <peter@lekensteyn.nl>
> ---
>   Documentation/Makefile      | 8 +++-----
>   Documentation/asciidoc.conf | 6 ++++++
>   2 files changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/Makefile b/Documentation/Makefile
> index ef4f1bd..72ab77b 100644
> --- a/Documentation/Makefile
> +++ b/Documentation/Makefile
> @@ -113,10 +113,8 @@ clean:
>   	$(XMLTO) -m $(MANPAGE_XSL) $(XMLTO_EXTRA) man $<
>   
>   %.xml : %.txt asciidoc.conf
> -	$(QUIET_ASCIIDOC)$(RM) $@.tmp[12] $@ && \
> -	sed -e "s/\(<[^>]\+>\)/'\1'/g" < $< > $@.tmp1 && \
> +	$(QUIET_ASCIIDOC)$(RM) $@+ $@ && \
>   	$(ASCIIDOC) -b docbook -d manpage -f asciidoc.conf \
>   		$(ASCIIDOC_EXTRA) -abtrfs_version=$(BTRFS_VERSION) \
> -		-o $@.tmp2 $@.tmp1 && \
> -	mv $@.tmp2 $@ && \
> -	rm -f -- $@.tmp1
> +		-o $@+ $< && \
> +	mv $@+ $@
> diff --git a/Documentation/asciidoc.conf b/Documentation/asciidoc.conf
> index 313f185..1ea7459 100644
> --- a/Documentation/asciidoc.conf
> +++ b/Documentation/asciidoc.conf
> @@ -10,6 +10,12 @@
>   [macros]
>   (?su)[\\]?(?P<name>linkbtrfs):(?P<target>\S*?)\[(?P<attrlist>.*?)\]=
>   
> +[tags]
> +bracket-emphasis={1?[{1}]}<emphasis>&lt;|&gt;</emphasis>
> +
> +[quotes]
> +&lt;|&gt;=#bracket-emphasis
> +
This method is more elegant than the original sed method.

Thanks a lot.
Qu
>   [attributes]
>   asterisk=&#42;
>   plus=&#43;


  reply	other threads:[~2015-01-06  1:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 14:10 [PATCH] Documentation: fix broken conversion Peter Wu
2015-01-06  1:14 ` Qu Wenruo [this message]
2015-01-09 17:41 ` David Sterba

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=54AB36FE.60508@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=peter@lekensteyn.nl \
    /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 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 NNTP newsgroup(s).