All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] manual: use one-line titles instead of two-line titles (trivial)
Date: Fri, 02 May 2014 10:31:58 +0200	[thread overview]
Message-ID: <87siospon5.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <0f7edee196f1f7a6643f.1399009650@argentina> (Thomas De Schampheleire's message of "Fri, 02 May 2014 07:47:30 +0200")

>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:

 > Asciidoc supports two syntaxes for section titles: two-line titles (title
 > plus underline consisting of a particular symbol), and one-line titles
 > (title prefixed with a specific number of = signs).

 > The two-line title underlines are:
 > Level 0 (top level):     ======================
 > Level 1:                 ----------------------
 > Level 2:                 ~~~~~~~~~~~~~~~~~~~~~~
 > Level 3:                 ^^^^^^^^^^^^^^^^^^^^^^
 > Level 4 (bottom level):  ++++++++++++++++++++++

 > and the one-line title prefixes:
 > = Document Title (level 0) =
 > == Section title (level 1) ==
 > === Section title (level 2) ===
 > ==== Section title (level 3) ====
 > ===== Section title (level 4) =====

 > The buildroot manual is currenly using the two-line titles, but this has
 > multiple disadvantages:

 > - asciidoc also uses some of the underline symbols for other purposes (like
 >   preformatted code, example blocks, ...), which makes it difficult to do
 >   mass replacements, such as a planned follow-up patch that needs to move
 >   all sections one level down.

 > - it is difficult to remember which level a given underline symbol (=-~^+)
 >   corresponds to, while counting = signs is easy.

 > This patch changes all two-level titles to one-level titles in the manual.
 > The bulk of the change was done with the following Python script, except for
 > the level 1 titles (-----) as these underlines are also used for literal
 > code blocks.
 > This patch only changes the titles, no other changes. In
 > adding-packages-directory.txt, I did add missing newlines between some
 > titles and their content.

 > ----------------------------------------------------------------------------
 > #!/usr/bin/env python

 > import sys
 > import mmap
 > import re

 > for input in sys.argv[1:]:

 >     f = open(input, 'r+')
 >     f.flush()
 >     s = mmap.mmap(f.fileno(), 0)

 >     # Level 0 (top level):     ======================   =
 >     # Level 1:                 ----------------------   ==
 >     # Level 2:                 ~~~~~~~~~~~~~~~~~~~~~~   ===
 >     # Level 3:                 ^^^^^^^^^^^^^^^^^^^^^^   ====
 >     # Level 4 (bottom level):  ++++++++++++++++++++++   =====

 >     def replace_title(s, symbol, replacement):
 >         pattern = re.compile(r'(.+\n)\%s{2,}\n' % symbol, re.MULTILINE)
 >         return pattern.sub(r'%s \1' % replacement, s)

 >     new = s
 >     new = replace_title(new, '=', '=')
 >     new = replace_title(new, '+', '=====')
 >     new = replace_title(new, '^', '====')
 >     new = replace_title(new, '~', '===')
 >     #new = replace_title(new, '-', '==')

 >     s.seek(0)
 >     s.write(new)
 >     s.resize(s.tell())
 >     s.close()
 >     f.close()

 > ----------------------------------------------------------------------------

 > Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>

Committed, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2014-05-02  8:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02  5:47 [Buildroot] [PATCH] manual: use one-line titles instead of two-line titles (trivial) Thomas De Schampheleire
2014-05-02  8:31 ` Peter Korsgaard [this message]
2014-05-02 10:43 ` Yann E. MORIN
2014-05-02 11:25   ` Thomas De Schampheleire

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=87siospon5.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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.