Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Eiji Tanioka <tanioka404@gmail.com>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH 1/2 wireguard-windows] Add Japanese translation to resources.rc
Date: Wed, 26 Feb 2020 11:46:27 +0900	[thread overview]
Message-ID: <CAA2ss9Ed9e34Ca1+c4dLrEH7kczf1cmwauArH3byQqbj+1-Myg@mail.gmail.com> (raw)
In-Reply-To: <CAA2ss9HDT5+zU6Zz1Gt=zNRKqr+Dv8hc8z63=qJMJymhgRD=2Q@mail.gmail.com>


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

Oops! I missed mail from ML.

>The reason it is being held:
>    Message body is too big: 46986 bytes with a limit of 40 KB

2020年2月26日(水) 7:50 Eiji Tanioka <tanioka404@gmail.com>:

> Hmm...
> I had sent patch by 'git send-email', and CC to me was delivered,
> but it seems not delivered to ML.
>
> Is there any limitation about sending patch to ML?
> For example, maximum body line count.
> (messages.gotext.json patch have 1234 lines)
>
> Regards,
>
> 2020年2月26日(水) 6:28 Eiji Tanioka <tanioka404@gmail.com>:
>
>> Sorry, failed to send message.gotext.json.
>> I will send it.
>>
>> 2020年2月26日(水) 2:17 Simon Rozman <simon@rozman.si>:
>>
>>> Thank you very much. I have applied your patch to the sr/l18n branch.
>>>
>>> Looking forward to locales/ja/messages.gotext.json 😊
>>>
>>> Best regards,
>>> Simon
>>>
>>> > -----Original Message-----
>>> > From: WireGuard <wireguard-bounces@lists.zx2c4.com> On Behalf Of Eiji
>>> > Tanioka
>>> > Sent: Tuesday, February 25, 2020 4:44 PM
>>> > To: wireguard@lists.zx2c4.com
>>> > Subject: [PATCH 1/2 wireguard-windows] Add Japanese translation to
>>> > resources.rc
>>> >
>>> > Signed-off-by: Eiji Tanioka <tanioka404@gmail.com>
>>> > ---
>>> >  resources.rc | 7 +++++++
>>> >  1 file changed, 7 insertions(+)
>>> >
>>> > diff --git a/resources.rc b/resources.rc index 14c0ce0..b5b779a 100644
>>> > --- a/resources.rc
>>> > +++ b/resources.rc
>>> > @@ -56,6 +56,13 @@ VERSIONINFO_TEMPLATE(
>>> >    "https://www.wireguard.com/"
>>> >  )
>>> >
>>> > +LANGUAGE LANG_JAPANESE, SUBLANG_DEFAULT VERSIONINFO_TEMPLATE(
>>> > +  "041104b0", 0x411, 0x4b0,
>>> > +  "WireGuard: 高速で、現代的で、セキュアな VPN トンネル",
>>> > +  "https://www.wireguard.com/"
>>> > +)
>>> > +
>>> >  LANGUAGE LANG_SLOVENIAN, SUBLANG_DEFAULT  VERSIONINFO_TEMPLATE(
>>> >    "042404b0", 0x424, 0x4b0,
>>> > --
>>> > 2.25.0
>>> >
>>> > _______________________________________________
>>> > WireGuard mailing list
>>> > WireGuard@lists.zx2c4.com
>>> > https://lists.zx2c4.com/mailman/listinfo/wireguard
>>>
>>

[-- Attachment #1.2: Type: text/html, Size: 3759 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-26  2:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25 15:44 Eiji Tanioka
2020-02-25 17:16 ` Simon Rozman
2020-02-25 21:28   ` Eiji Tanioka
2020-02-25 22:50     ` Eiji Tanioka
2020-02-26  2:46       ` Eiji Tanioka [this message]
2020-02-26  9:20         ` Jason A. Donenfeld

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=CAA2ss9Ed9e34Ca1+c4dLrEH7kczf1cmwauArH3byQqbj+1-Myg@mail.gmail.com \
    --to=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).