netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Shan Wei <shanwei88@gmail.com>
Cc: David Miller <davem@davemloft.net>, <rdunlap@xenotime.net>,
	<willemb@google.com>, <benjamin.poirier@gmail.com>,
	<therbert@google.com>, <linux-doc@vger.kernel.org>,
	<netdev@vger.kernel.org>
Subject: Re: [Patch V2 ] net: doc: cleanup Documentation/networking/scaling.txt
Date: Thu, 8 Dec 2011 04:01:18 +0000	[thread overview]
Message-ID: <1323316878.18450.60.camel@deadeye> (raw)
In-Reply-To: <4EE01B0B.2050900@gmail.com>

On Thu, 2011-12-08 at 10:03 +0800, Shan Wei wrote:
> David Miller said, at 2011/12/8 2:40:
> 
> > I don't know if it's the encoding you use or something else but you
> > must fix this before submitting any more patches.
>  
> 
> Indeed, used default encoding of GB2312, now change it to UTF-8
> according to email-clients.txt and resubmit this patch.
> 
> 
> [PATCH v3] net: doc: cleanup Documentation/networking/scaling.txt
> 
> 1) Fix some typos.
> 2) Change mode of the punctuation from full to half, eg.’,“ .
>    So that the punctuation can be read at console.
[...]

UTF-8 is the standard character encoding under Linux and those quotes
will be displayed correctly on most Linux terminals today.  If you must
set your terminal to some other encoding you can use e.g.:

    recode UTF-8 < Documentation/networking/scaling.txt | less

(Be sure to use redirection, otherwise recode will modify the file.)

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.


  reply	other threads:[~2011-12-08  4:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 14:26 [Patch V2 ] net: doc: cleanup Documentation/networking/scaling.txt Shan Wei
2011-12-07 18:40 ` David Miller
2011-12-08  2:03   ` Shan Wei
2011-12-08  4:01     ` Ben Hutchings [this message]
2011-12-08  5:32       ` Shan Wei

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=1323316878.18450.60.camel@deadeye \
    --to=bhutchings@solarflare.com \
    --cc=benjamin.poirier@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=shanwei88@gmail.com \
    --cc=therbert@google.com \
    --cc=willemb@google.com \
    /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).