Date: Fri, 21 Oct 2016 14:47:45 -0600
From: Jonathan Corbet <corbet@lwn.net>
To: SeongJae Park <sj38.park@gmail.com>
Cc: minchan@kernel.org, mchehab@s-opensource.com,
        linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/12] Fix and update HOWTO Korean translation
Message-ID: <20161021144745.18e2e93c@lwn.net>
In-Reply-To: <20161021151957.8127-1-sj38.park@gmail.com>
References: <20161021151957.8127-1-sj38.park@gmail.com>
Organization: LWN.net
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1331
Lines: 32

On Sat, 22 Oct 2016 00:19:45 +0900
SeongJae Park <sj38.park@gmail.com> wrote:

> This patchset applies ReST conversion effort for HOWTO document to its Korean
> translation.  It also contains fixup of trivial nitpicks in the document and
> the translation.

Thanks for doing these; let's definitely get this work in soon.  I have
just a few comments:

- I think that bringing the (English) HOWTO into line with our posted
  conventions makes sense, I'm happy to take patches to do that.  Let's
  do that separately from the translation changes, though, and let's
  think in terms of building on Mauro's work.  Either send me a patch
  after his stuff is in, or send one for him to collect and send with the
  rest, whatever works best for everybody else.

- You do the ReST conversion, but don't take the final step and actually
  bring the document into the Sphinx world.

I've been thinking that it would be good to make a translations/
top-level directory and move the various translated documents underneath
that.  Then we could maybe make a translations/index.rst and create a
special subbook for those documents.  Make sense?

If at all possible, I'd like an ack from somebody else who understands
Korean.  Minchan, I see you on the CC, can you help out? :)  With that, I
see no reason not to apply parts 2-12.

Thanks,

jon