From: "Paul E. McKenney" <paulmck@kernel.org>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] FAQ: Update Korean translation progress
Date: Sun, 11 Feb 2024 11:01:08 -0800 [thread overview]
Message-ID: <c29f1387-50d3-4e73-91ae-69903341b70e@paulmck-laptop> (raw)
In-Reply-To: <20240211175355.4986-1-sj38.park@gmail.com>
On Sun, Feb 11, 2024 at 09:53:54AM -0800, SeongJae Park wrote:
> I started the translation of perfbook since October 2015. The
> translation was done by June 2017, and I continued wordsmithing, merging
> the upstream changes, and further translating. Following the upstream's
> fast speed of the change and keeping the translation consistent was
> quite challenging.
>
> In Mar 2021, I therefore decided to stop updating existing translation
> and start the translation of the 2nd edition from the scratch. Applying
> upstream changes were minimized to only simple fixes, usually what I
> fixed on my local repo first and sent patches upstream.
>
> After about three years, I just completed the Korean translation of the
> 2nd edition. Hence updating the Korean translation progress on FAQ.
>
> It was a very fun and informative journey. Huge appreciate to Paul and
> the community for making the great book and letting me get the fun.
>
> I have no plan for the future. I don't know if I will continue merging
> upstream changes and further translating it, or if I will restart the
> translation after the third edition is released. I sometimes feel
> translation is already an area that AI can do better than me. But I
> sure I would repeatedly read this book again and again, and some day, I
> might try to translate it again. But at the moment, I'd like to take a
> time to congrats myself :)
>
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Congratulations, thank you, and I have queued and pushed this patch.
(Only to github, not yet to kernel.org due to technical difficulties at
my end that should be resolved within a few days.)
Thanx, Paul
> ---
> FAQ.txt | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/FAQ.txt b/FAQ.txt
> index eb242a36..9e0021f9 100644
> --- a/FAQ.txt
> +++ b/FAQ.txt
> @@ -136,10 +136,15 @@
>
> https://sites.google.com/view/kandamotohiro2/perfbook
>
> - SeongJae Park has started work on a Korean translation:
> + SeongJae Park has Korean translations of the first two editions
> + of this book. The translation of the first edition contains
> + some of later-first edition changes, though[*]:
>
> https://github.com/sjp38/perfbook-ko_KR
>
> + [*] Refer to 'Translation Strategy and Editions' section of
> + https://github.com/sjp38/perfbook-ko_KR-pdf/blob/master/README
> +
> 7. I am working on a translation. What do I need to do to get my
> name of the list in #6 above?
>
> --
> 2.17.1
>
prev parent reply other threads:[~2024-02-11 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 17:53 [PATCH] FAQ: Update Korean translation progress SeongJae Park
2024-02-11 19:01 ` Paul E. McKenney [this message]
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=c29f1387-50d3-4e73-91ae-69903341b70e@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=perfbook@vger.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 read-only IMAP folder(s) and NNTP newsgroup(s).