ruby-dev (Japanese) list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "hsbt (Hiroshi SHIBATA)" <noreply@ruby-lang.org>
To: ruby-dev@ruby-lang.org
Subject: [ruby-dev:51112] [Ruby master Misc#12911] Translate docs
Date: Wed, 24 Nov 2021 04:52:24 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-94848.20211124045224.129@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-12911.20161108160400.129@ruby-lang.org>

Issue #12911 has been updated by hsbt (Hiroshi SHIBATA).

Assignee deleted (sho-h (Sho Hashimoto))

----------------------------------------
Misc #12911: Translate docs
https://bugs.ruby-lang.org/issues/12911#change-94848

* Author: sho-h (Sho Hashimoto)
* Status: Assigned
* Priority: Normal
----------------------------------------
translate doc/*.ja.rdoc

c.f. [ruby-dev:47319]



-- 
https://bugs.ruby-lang.org/

           reply	other threads:[~2021-11-24  4:52 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <redmine.issue-12911.20161108160400.129@ruby-lang.org>]

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=redmine.journal-94848.20211124045224.129@ruby-lang.org \
    --to=noreply@ruby-lang.org \
    --cc=ruby-dev@ruby-lang.org \
    /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).