[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: debian-faq korean translation



Hi sebul,

sebul <sebuls@gmail.com> wrote (Thu, 7 Oct 2021 18:53:47 +0900):
> I added ko at Makefile to add a korean translation.
> I run make updatepo.
> I edited *.po files in the ko/ directory.
> I don't know why other files changed.
> Help me please.

Hmm, the changes to the en and debian directory are from commits, which 
happened in December of last year already, like:

-------------------------------------------------------------

commit 70398b06f25701a61cfe886aca0429bcb663db96
Author: Dr. Tobias Quathamer <toddy@debian.org>
Date:   Mon Dec 28 21:47:17 2020 +0100

    More preparations for the next upload


commit bcfde0383f044aecc000ae5dda29ddc1bf267927
Author: Dr. Tobias Quathamer <toddy@debian.org>
Date:   Mon Dec 28 21:37:40 2020 +0100

    Update Standards-Version to 4.5.1, no changes needed


commit 816be4d185aa1028b17f510e9a53bb7163ab758e
Author: Dr. Tobias Quathamer <toddy@debian.org>
Date:   Mon Dec 28 21:36:48 2020 +0100

    Use debhelper v13

-------------------------------------------------------------

Don't know, what happened, so that you got them into your merge request...
Probably some bad workflow with branch/creation of merge request.

To get that solved, I would propose the following:

Commit your lastest changings (if you have any) to the merge request, as you 
already did the last days.
Then we could cherry-pick the Korean po files from the MR and get them committed
into the master branch, and close the MR.
>From that point, you could use your po files from master branch, for l10n review
and more translation work.



Holger



-- 
Holger Wansing <hwansing@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076


Reply to: