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
Date: Fri, 21 Oct 2016 14:47:45 -0600 [thread overview]
Message-ID: <20161021144745.18e2e93c@lwn.net> (raw)
In-Reply-To: <20161021151957.8127-1-sj38.park@gmail.com>
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
next prev parent reply other threads:[~2016-10-21 20:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 15:19 [PATCH 00/12] Fix and update HOWTO Korean translation SeongJae Park
2016-10-21 15:19 ` [PATCH 01/12] Documentation/HOWTO: Mark subsection in rst format SeongJae Park
2016-10-21 15:45 ` Mauro Carvalho Chehab
2016-10-21 16:42 ` SeongJae Park
2016-10-21 17:25 ` Mauro Carvalho Chehab
2016-10-21 17:57 ` SeongJae Park
2016-10-21 15:19 ` [PATCH 02/12] ko_KR/HOWTO: Fix a typo: s/Linux Torvalds/Linus Torvalds SeongJae Park
2016-10-21 15:19 ` [PATCH 03/12] ko_KR/HOWTO: Fix subtitles style SeongJae Park
2016-10-21 15:19 ` [PATCH 04/12] ko_KR/HOWTO: Update obsolete link to bugzilla faq SeongJae Park
2016-10-21 15:19 ` [PATCH 05/12] ko_KR/HOWTO: Convert to ReST notation SeongJae Park
2016-10-21 15:19 ` [PATCH 06/12] ko_KR/HOWTO: Add cross-references to other documents SeongJae Park
2016-10-21 15:19 ` [PATCH 07/12] ko_KR/HOWTO: Update information about generating documentation SeongJae Park
2016-10-21 15:19 ` [PATCH 08/12] ko_KR/HOWTO: Improve some markups to make it visually better SeongJae Park
2016-10-21 15:19 ` [PATCH 09/12] ko_KR/HOWTO: Adjust external link references SeongJae Park
2016-10-21 15:19 ` [PATCH 10/12] ko_KR/HOWTO: Clean up bare :: lines SeongJae Park
2016-10-21 15:19 ` [PATCH 11/12] ko_KR/HOWTO: Add whitespace between URL and text SeongJae Park
2016-10-21 15:19 ` [PATCH 12/12] ko_KR/HOWTO: Mark subsection in rst format SeongJae Park
2016-10-21 20:47 ` Jonathan Corbet [this message]
2016-10-22 1:39 ` [PATCH 00/12] Fix and update HOWTO Korean translation SeongJae Park
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=20161021144745.18e2e93c@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@s-opensource.com \
--cc=minchan@kernel.org \
--cc=sj38.park@gmail.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