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 v2 00/12] Fix and update HOWTO Korean translation
Date: Mon, 7 Nov 2016 17:05:33 -0700 [thread overview]
Message-ID: <20161107170533.29796868@lwn.net> (raw)
In-Reply-To: <20161031202721.8068-1-sj38.park@gmail.com>
On Tue, 1 Nov 2016 05:27:09 +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.
OK, to the extent that I can understand them, these changes all seem
reasonable to me, and I'll be happy to apply them. Indeed, I have just
done so.
They stop short of the final step, though: actually hooking the
ReST-formatted file into the build system. I would envision something
like this:
- Create a new directory Documentation/translations (or something like
"trans" if we want to be shorter, but I think it makes sense to spell
it out).
- Move ja_JP, ko_KR, and zh_CN into that directory
- Rename .../ko_KR/HOWTO to HOWTO.rst
- Create an overall index.rst for Korean translations. It could include
information on how the translations are done, who to contact, and pull
in the translated HOWTO document.
- Add that index.rst to the top-level build. (We could consider putting
an index file in translations/ as well, but that can come later).
Make sense? I may do this in the not-too-near future if nobody else beats
me to it, but I'd welcome patches.
Thanks,
jon
next prev parent reply other threads:[~2016-11-08 0:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 20:27 [PATCH v2 00/12] Fix and update HOWTO Korean translation SeongJae Park
2016-10-31 20:27 ` [PATCH v2 01/12] Documentation/process/howto: Mark subsection in suggested format SeongJae Park
2016-10-31 20:27 ` [PATCH v2 02/12] ko_KR/HOWTO: Fix a typo: s/Linux Torvalds/Linus Torvalds SeongJae Park
2016-10-31 20:27 ` [PATCH v2 03/12] ko_KR/HOWTO: Fix subtitles style SeongJae Park
2016-10-31 20:27 ` [PATCH v2 04/12] ko_KR/HOWTO: Update obsolete link to bugzilla faq SeongJae Park
2016-10-31 20:27 ` [PATCH v2 05/12] ko_KR/HOWTO: Convert to ReST notation SeongJae Park
2016-10-31 20:27 ` [PATCH v2 06/12] ko_KR/HOWTO: Add cross-references to other documents SeongJae Park
2016-10-31 20:27 ` [PATCH v2 07/12] ko_KR/HOWTO: Update information about generating documentation SeongJae Park
2016-10-31 20:27 ` [PATCH v2 08/12] ko_KR/HOWTO: Improve some markups to make it visually better SeongJae Park
2016-10-31 20:27 ` [PATCH v2 09/12] ko_KR/HOWTO: Adjust external link references SeongJae Park
2016-10-31 20:27 ` [PATCH v2 10/12] ko_KR/HOWTO: Clean up bare :: lines SeongJae Park
2016-10-31 20:27 ` [PATCH v2 11/12] ko_KR/HOWTO: Add whitespace between URL and text SeongJae Park
2016-10-31 20:27 ` [PATCH v2 12/12] ko_KR/HOWTO: Mark subsection in suggested format SeongJae Park
2016-11-06 18:21 ` [PATCH v2 00/12] Fix and update HOWTO Korean translation SeongJae Park
2016-11-06 20:45 ` Jonathan Corbet
2016-11-08 0:05 ` Jonathan Corbet [this message]
2016-11-08 1:30 ` 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=20161107170533.29796868@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;
as well as URLs for NNTP newsgroup(s).