Re: Ch. Ruby-3.4.5: use double quotes to delimit the test-suite-message

"Xi Ruoyao" ([email protected] via blfs-dev Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.beyond.devel
Message-ID <[email protected]>
On Tue, 2025-07-22 at 09:08 -0500, Bruce Dubbs wrote:
> On 7/22/25 7:41 AM, Xi Ruoyao ([email protected] via blfs-dev Mailing List) wrote:
> > On Tue, 2025-07-22 at 12:34 +0200, Rainer Fiebig wrote:
> > > In order to improve readability, I think that double quotes should be
> > > used to delimit the test-suite-message in this sentence:
> > > 
> > > [...] will bail out early with messages like net/ftp is not found.
> > > 
> > > This would be better (IMO):
> > > 
> > > [...] will bail out early with messages like "net/ftp is not found".
> > 
> > The problem with quote here is per the American English grammar the
> > punctuation should be inside the quote, but the computer doesn't
> > actually output a punctuation.
> > 
> > So here we use <computeroutput> which should be rendered in a different
> > style than the normal texts.  If your browser fails to render them in
> > different styles it's either buggy or misconfigured.  Even Lynx uses
> > different colors.
> 
> That's true.  In Firefox, it renders as monospace, but perhaps we could do more by 
> changing the color with css.  The html has
> 
> <code class="computeroutput">net/ftp is not found</code>.
> 
> The css has
> 
> /* Monospaced elements */
> tt, code, kbd, pre, .command {
>    font-family: monospace;
> }
> 
> code.systemitem {
>    font-weight: bold;
> =========
> Perhaps instead of double quotes we could add something like:
> 
> code.computeroutput {
>    color: blue;
> }
> 
> What do you think?

No objection as long as we mention this convention in "Conventions Used
in this Book."

And maybe we'd do the same to LFS.

-- 
Xi Ruoyao <[email protected]>

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.