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] [day] [month] [year] [list]
Message-ID: <CAEjAshrvvx=rs_gZ5z9=OW38F-xygb6EC0o6e--JOzC-17S3QQ@mail.gmail.com>
Date:   Sat, 22 Oct 2016 10:39:38 +0900
From:   SeongJae Park <sj38.park@...il.com>
To:     Jonathan Corbet <corbet@....net>
Cc:     Minchan Kim <minchan@...nel.org>,
        Mauro Carvalho Chehab <mchehab@...pensource.com>,
        linux-doc <linux-doc@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/12] Fix and update HOWTO Korean translation

On Sat, Oct 22, 2016 at 5:47 AM, Jonathan Corbet <corbet@....net> wrote:
> On Sat, 22 Oct 2016 00:19:45 +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.
>
> Thanks for doing these; let's definitely get this work in soon.  I have
> just a few comments:

Thanks for your opinion! :)


>
> - 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.

Agree.  I will send you the patch again after Mauro's work be merged.


>
> - 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?

Yes, it makes sense to me.  I will send patches for that soon.


Thanks,
SeongJae Park

>
> 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ