linux-kernel - Re: [PATCH v3 16/16] docs: RCU: replace some characters

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <57bb2653-8754-707f-6d54-9a64dccd3c50@gmail.com>
Date:   Mon, 17 May 2021 19:53:00 +0900
From:   Akira Yokosawa <akiyks@...il.com>
To:     mchehab+huawei@...nel.org
Cc:     bigeasy@...utronix.de, corbet@....net, jiangshanlai@...il.com,
        joel@...lfernandes.org, josh@...htriplett.org,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        mathieu.desnoyers@...icios.com, nfraprado@...tonmail.com,
        paulmck@...nel.org, rcu@...r.kernel.org, rdunlap@...radead.org,
        rostedt@...dmis.org, tiwai@...e.de, will@...nel.org,
        Akira Yokosawa <akiyks@...il.com>
Subject: Re: [PATCH v3 16/16] docs: RCU: replace some characters

On Sun, 16 May 2021 12:18:33 +0200, Mauro Carvalho Chehab wrote:
> The conversion tools used during DocBook/LaTeX/html/Markdown->ReST
> conversion and some cut-and-pasted text contain some characters that
> aren't easily reachable on standard keyboards and/or could cause
> troubles when parsed by the documentation build system.
> 
> Replace the occurences of the following characters:
> 
> 	- U+00a0 (' '): NO-BREAK SPACE
> 	  as it can cause lines being truncated on PDF output

These NO-BREAK SPACEs originate from "&nbsp;"s in html docs converted by
commit ccc9971e2147 ("docs: rcu: convert some articles from html to ReST").

I think the patterns found in these files ("~" denotes NO-BREAK SPACE):

    CPU~0
    Tasks~T1, T2, and~T3
    line~n
    lines~m and~n
    ...

are quite appropriate and nice-to-have contextual markers.

Despite the claim above, I don't believe these NO-BREAK SPACEs can cause
any truncation in the PDF output, because they combine short numbers or
symbols with terms such as "CPU", "Task", and "line". 

So I'd like you all to keep these NO-BREAK SPACEs.

If there ever emerges such truncations, they can be taken care of
case-by-case bases.

        Thanks, Akira

> 
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
> ---
>  .../Data-Structures/Data-Structures.rst       | 46 ++++++------
>  .../Expedited-Grace-Periods.rst               | 36 +++++-----
>  .../Tree-RCU-Memory-Ordering.rst              |  2 +-
>  .../RCU/Design/Requirements/Requirements.rst  | 70 +++++++++----------
>  4 files changed, 77 insertions(+), 77 deletions(-)