[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <07e0949f-fa9f-e4f8-2891-aaf9f84ede7c@gmail.com>
Date: Sun, 6 Nov 2022 21:04:10 +0900
From: Akira Yokosawa <akiyks@...il.com>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: alexandre.ghiti@...onical.com, aou@...s.berkeley.edu,
corbet@....net, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
palmer@...belt.com, paul.walmsley@...ive.com,
Akira Yokosawa <akiyks@...il.com>
Subject: Re: [PATCH] Documentation: riscv: tableize memory layout
Hi Bagas,
On Sun, 6 Nov 2022 17:02:40 +0700, Bagas Sanjaya wrote:
> The memory layout is written as table but it is inside literal code
> block, which renders as preformatted text. Write the layout in reST
> grid table instead.
What's the purpose of this change?
The tables in html/pdf output after this change are almost unreadable
to my eyes due to the proportional font and random wrapping inside
table columns.
I think in this particular case, "literal block" is the right
choice at least for html output, as can be seen at:
https://www.kernel.org/doc/html/latest/riscv/vm-layout.html
https://www.kernel.org/doc/html/next/riscv/vm-layout.html
Yes, these very wide tables need horizontal scrolling in the alabaster
theme (in next), but they look much nicer than your version.
In pdf output, wide literal blocks are force-wrapped and don't look good.
Using some smaller font size for latex might help, but most people don't
care much of pdf outputs anyway, I guess.
Thanks, Akira
>
> Signed-off-by: Bagas Sanjaya <bagasdotme@...il.com>
> ---
> Documentation/riscv/vm-layout.rst | 120 +++++++++++++++---------------
> 1 file changed, 58 insertions(+), 62 deletions(-)
Powered by blists - more mailing lists