[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160413063805.GA14197@gmail.com>
Date: Wed, 13 Apr 2016 08:38:05 +0200
From: Ingo Molnar <mingo@...nel.org>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, jiangshanlai@...il.com,
dipankar@...ibm.com, akpm@...ux-foundation.org,
mathieu.desnoyers@...icios.com, josh@...htriplett.org,
tglx@...utronix.de, peterz@...radead.org, rostedt@...dmis.org,
dhowells@...hat.com, edumazet@...gle.com, dvhart@...ux.intel.com,
fweisbec@...il.com, oleg@...hat.com, bobby.prani@...il.com,
SeongJae Park <sj38.park@...il.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH memory-barriers.txt 6/7] documentation: Add Korean
translation
* Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote:
> From: SeongJae Park <sj38.park@...il.com>
>
> This commit adds Korean version of memory-barriers.txt document. The
> header is refered to HOWTO Korean version.
>
> Signed-off-by: SeongJae Park <sj38.park@...il.com>
> Acked-by: David Howells <dhowells@...hat.com>
> Signed-off-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> Acked-by: Minchan Kim <minchan@...nel.org>
> ---
> Documentation/ko_KR/memory-barriers.txt | 3048 +++++++++++++++++++++++++++++++
> 1 file changed, 3048 insertions(+)
> create mode 100644 Documentation/ko_KR/memory-barriers.txt
So we seem to have little precedent for such big translations, so I'd like to have
higher level buy-in first, before applying such changes.
We do have some ko_KR material upstream already:
triton:~/tip> ls -l Documentation/ko_KR/
total 52
-rw-rw-r-- 1 mingo mingo 35017 Apr 6 09:02 HOWTO
-rw-rw-r-- 1 mingo mingo 12741 Apr 6 09:02 stable_api_nonsense.txt
... but that's introductory level material.
Fundamentally English is the language of the Linux kernel, all in-code comments
are in English. Furthermore, people who know English and don't speak Korean won't
be able to fix the ko_KR side of the documentation - so most of the time there's
going to be some lag. It's also going to be harder by maintainers to review
patches to these files, especially if they don't speak Korean.
Thanks,
Ingo
Powered by blists - more mailing lists