9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] 'LEFT SINGLE QUOTATION MARK' in FQA
Date: Sun, 10 Jan 2016 18:14:02 -0500	[thread overview]
Message-ID: <04d4d9a3032e2051b0b6f87327b8bc1c@u2.attlocal.net> (raw)

> in the fqa, some command invocations have a 'LEFT SINGLE QUOTATION MARK'
> where i think a simple single quote (') would be more appropriate, for
> example in http://fqa.9front.org/fqa7.html#7.6.2. is there any
> particular reason to keep the strange unicode character?

Compare:

	/n/fqa/fqa7.ms:1200

with

	/n/fqa/fqa7.html:1398

The HTML is generated with htmlroff -u -ms -mhtml. I agree, when it
comes to displaying commands meant to be typed into the terminal
window, it would be better to keep the actual character used in the
input.

I will look into this when I get a chance.

sl


             reply	other threads:[~2016-01-10 23:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10 23:14 sl [this message]
2016-01-11  1:15 sl

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=04d4d9a3032e2051b0b6f87327b8bc1c@u2.attlocal.net \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.org \
    /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).