Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Eiji Tanioka <tanioka404@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] Update Simplified Chinese translation
Date: Sat, 29 Feb 2020 16:54:03 +0800	[thread overview]
Message-ID: <CAHmME9q+8urTTq+HBknrhFq5B2YbK9GmcHWP6qOCuQUGh6tWKQ@mail.gmail.com> (raw)
In-Reply-To: <CAA2ss9HbDro5vgS0W8_cTQUetLFzjUCqXO1CHmsHprM7_Q+mXA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1446 bytes --]

I see no patch caught in the queue. Try again?

On Sat, Feb 29, 2020, 16:36 Eiji Tanioka <tanioka404@gmail.com> wrote:

> Hi Vasili!
>
> Did you send patch to ML?
> If so, I think that your patch is in the moderation queue. I had met
> same situation when sending my patch because of body size (over 40
> KB).
>
> I think it's okay if you wait.
>
> Regards,
>
> 2020年2月29日(土) 16:03 Vasili Pupkin <diggest@gmail.com>:
>
> >
> > On 26.02.2020 6:59, Samuel Holland wrote:
> > > On 2/25/20 9:44 PM, Vasili Pupkin wrote:
> > >> It seams that russian translation is very basic and not utilize
> > >> quantity="two"
> > >> and quantity="few" forms, without them some plurals reads odd. Do you
> need help
> > >> fixing it or it is done on purpose?
> > > I don't think it was done on purpose; likely the translator was
> unaware of the
> > > additional options for quantity in <item> tags. I am happy to merge
> patches
> > > improving the translation (which is really up to your judgement, since
> I don't
> > > speak any of these languages).
> >
> > Have you received the patch?
> > _______________________________________________
> > WireGuard mailing list
> > WireGuard@lists.zx2c4.com
> > https://lists.zx2c4.com/mailman/listinfo/wireguard
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>

[-- Attachment #1.2: Type: text/html, Size: 2346 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2020-02-29  8:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-23 11:12 srb12345
2020-02-25  0:56 ` Samuel Holland
2020-02-25  8:13   ` Eiji Tanioka
2020-02-26  2:56     ` Samuel Holland
2020-02-26  3:10       ` Eiji Tanioka
2020-02-26  3:44       ` Vasili Pupkin
2020-02-26  3:59         ` Samuel Holland
2020-02-29  7:00           ` Vasili Pupkin
2020-02-29  8:35             ` Eiji Tanioka
2020-02-29  8:54               ` Jason A. Donenfeld [this message]
     [not found]               ` <5428f486-49cd-0321-de5b-9ef6ca3e8dad@gmail.com>
2020-03-01  6:53                 ` Eiji Tanioka
2020-03-01  7:00                   ` Jason A. Donenfeld
2020-02-26  3:21 =?gb18030?B?TWF0c3VyaQ==?=
2020-03-12 11:40 srb12345
2020-03-12 11:47 ` Harsh Shandilya

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=CAHmME9q+8urTTq+HBknrhFq5B2YbK9GmcHWP6qOCuQUGh6tWKQ@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=tanioka404@gmail.com \
    --cc=wireguard@lists.zx2c4.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 NNTP newsgroup(s).