linux-kernel - Re: [PATCH v2 00/12] Fix and update HOWTO Korean translation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 7 Nov 2016 17:05:33 -0700
From:   Jonathan Corbet <corbet@....net>
To:     SeongJae Park <sj38.park@...il.com>
Cc:     minchan@...nel.org, mchehab@...pensource.com,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 00/12] Fix and update HOWTO Korean translation

On Tue,  1 Nov 2016 05:27:09 +0900
SeongJae Park <sj38.park@...il.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