From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752291AbcKHAFi (ORCPT ); Mon, 7 Nov 2016 19:05:38 -0500 Received: from tex.lwn.net ([70.33.254.29]:32809 "EHLO vena.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750809AbcKHAFf (ORCPT ); Mon, 7 Nov 2016 19:05:35 -0500 Date: Mon, 7 Nov 2016 17:05:33 -0700 From: Jonathan Corbet To: SeongJae Park 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 Message-ID: <20161107170533.29796868@lwn.net> In-Reply-To: <20161031202721.8068-1-sj38.park@gmail.com> References: <20161031202721.8068-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 List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 1 Nov 2016 05:27:09 +0900 SeongJae Park 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