Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Eiji Tanioka <tanioka404@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	me@msfjarvis.dev
Cc: Simon Rozman <simon@rozman.si>, Roopesh Chander S <roop@roopc.net>
Subject: Re: Question about Crowdin operation
Date: Sun, 19 Apr 2020 14:21:00 +0900	[thread overview]
Message-ID: <CAA2ss9E0UnqPdj0uHF6rfLD0TdkAB5s=L=OXf6dH+1T20-TBAA@mail.gmail.com> (raw)
In-Reply-To: <59f5a401d768dfad8b60a0ed3f59a5b6@msfjarvis.dev>

Harsh, Jason,
Thank you for quick response!

> The second option is perfectly fine, though you'll have better luck if you
> mention me or Jason since that will ensure Crowdin does not swallow up the
> notifications.

> AFAICT, the "issue" flag sends us an email notification, which is a
> good thing if you need an answer.

I understood.
When I use comments is when I need a response, so I will try to use
the mention or issue flag.

2020年4月19日(日) 5:24 Harsh Shandilya <me@msfjarvis.dev>:
>
> April 19, 2020 1:38 AM, "Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>
> > On Sat, Apr 18, 2020 at 9:56 AM Eiji Tanioka <tanioka404@gmail.com> wrote:
> >
> >> Hi,
> >>
> >> I'm translating WireGuard apps into Japanese.
> >> I have a question about operation in Crowdin.
> >>
> >> When translate, we translators need to clarify about original string's
> >> context or meaning. In that situation, which option is preferred?
> >>
> >> - send ML about question.
> >> - in Crowdin, use comment.
> >> - in Crowdin, use comment and flag "Issue".
> >> - in Crowdin, use Discussion.
> >>
> >> # I had used second option, but never mention to anyone.
> >> # Should I had to mention to ?
> >>
> >> Kind regards,
> >> Eiji Tanioka
> >
> > Hey Eiji,
> >
> > CC'ing Harsh, Simon, and Roopesh, as they might have different
> > opinions on what they prefer.
> >
> > From my end, any form of communication is fine, whether its on Crowdin
> > or on the mailing list, because lowering the barrier for people to
> > volunteer their hours translating strings for us seems like a good
> > thing.
>
> Same goes for me, I'll take whatever's the easiest route for translators
> and work with it.
>
> > I suppose one advantage of Crowdin is that the discussions are placed
> > beside the translations, which makes it easy for future people to
> > correlate the two, and most discussions tend to be clarifications on
> > particular strings, rather than interesting technical conversation
> > that would benefit from the archiving afforded by mailing lists.
> >
> > AFAICT, the "issue" flag sends us an email notification, which is a
> > good thing if you need an answer.
> >
> > Jason
>
>
> Harsh Shandilya

      reply	other threads:[~2020-04-19  5:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-18 15:55 Eiji Tanioka
2020-04-18 16:58 ` Harsh Shandilya
2020-04-18 20:08 ` Jason A. Donenfeld
2020-04-18 20:24 ` Harsh Shandilya
2020-04-19  5:21   ` Eiji Tanioka [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='CAA2ss9E0UnqPdj0uHF6rfLD0TdkAB5s=L=OXf6dH+1T20-TBAA@mail.gmail.com' \
    --to=tanioka404@gmail.com \
    --cc=Jason@zx2c4.com \
    --cc=me@msfjarvis.dev \
    --cc=roop@roopc.net \
    --cc=simon@rozman.si \
    --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).