public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Takeshi Hamasaki <hmatrjp@users.sourceforge.jp>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: translation-team-ja@lists.sourceforge.net, yasuakit@gmail.com,
	 libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [Translation-team-ja] Updating Japanese libc translation for ESTALE in glibc
Date: Tue, 9 May 2023 08:31:54 +0900	[thread overview]
Message-ID: <CAPESJy4ZKPrQYKBX7Pqe0DHzi0bzOg-k1hhkPc6zkPXzPRh0+Q@mail.gmail.com> (raw)
In-Reply-To: <22b7bd22-24fd-d7b1-f343-2771b317edf2@redhat.com>


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

Dear Mr. Carlos O'Donell,

Thank you for your offer to update libc translation for Japanese.
As a Japanese Team coordinator I can incorporate the translation from
downstream.
Mr.Yasuaki Taniguchi, who is the assigned translator to libc is keeping
silent for a week,
I'm happy to do so on behalf of him.

Attached file is the candidate of revision. Please let me know whether you
have any corrections after seeing line 7 and 6152.
I'll send this to Translation Project tonight or tomorrow morning. (JST)

In fact, your mail was kept in the bounce folder for weeks before I found
it there,
since your address is not the registered member of the ML.
I'm sorry for the delay of the response for your kind contribution.

Regards,
Takeshi Hamasaki (Japanese Team coordinator, Translation Project)

2023年4月25日(火) 14:06 Carlos O'Donell <carlos@redhat.com>:

> Dear Japanese Translators,
>
> I was recently reviewing Japanese translations for error cases,
> in particularly the translation of the error string for the
> error number ESTALE.
>
> The translation for ESTALE appears to be out of date and I would
> like to get that updated. Error numbers are important things to
> translate.
>
> I have a Japanese translation for ESTALE that could be used.
> How can I help with that?
>
> The current POT file has:
> ~~~
> #. TRANS This indicates an internal confusion in the
> #. TRANS file system which is due to file system rearrangements on the
> server host
> #. TRANS for NFS file systems or corruption in other file systems.
> #. TRANS Repairing this condition usually requires unmounting, possibly
> repairing
> #. TRANS and remounting the file system.
> #: sysdeps/gnu/errlist.h:471
> msgid "Stale file handle"
> msgstr ""
> ~~~
>
> The current PO file is here for glibc 2.37 released 2023-02-01:
> https://translationproject.org/PO-files/ja/libc-2.36.9000.ja.po
> ~~~
> #. TRANS This indicates an internal confusion in the
> #. TRANS file system which is due to file system rearrangements on the
> server host
> #. TRANS for NFS file systems or corruption in other file systems.
> #. TRANS Repairing this condition usually requires unmounting, possibly
> repairing
> #. TRANS and remounting the file system.
> #: sysdeps/gnu/errlist.h:471
> #, fuzzy
> #| msgid "Stale NFS file handle"
> msgid "Stale file handle"
> msgstr "実効性のないNFSファイルハンドルです"
> ~~~
>
> We had a downstream translation in RHEL6 and RHEL7 for this:
> ~~~
> msgstr "古いファイルハンドルです"
> ~~~
>
> How can I help get the ESTALE translation updated for libc?
>
> Thank you very much for your help.
>
> --
> Cheers,
> Carlos.
>
>
>
> _______________________________________________
> Translation-team-ja mailing list
> Translation-team-ja@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/translation-team-ja
>

[-- Attachment #2: libc-2.36.9000.ja.po.gz --]
[-- Type: application/gzip, Size: 66681 bytes --]

  parent reply	other threads:[~2023-05-08 23:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 17:48 Carlos O'Donell
2023-05-08 23:23 ` [Translation-team-ja] " Takeshi Hamasaki
2023-05-08 23:31 ` Takeshi Hamasaki [this message]
2023-05-10  0:36   ` Takeshi Hamasaki
2023-07-07 15:44     ` Carlos O'Donell
2023-07-03  2:19 ` Carlos O'Donell
2023-07-07 15:42   ` Carlos O'Donell

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=CAPESJy4ZKPrQYKBX7Pqe0DHzi0bzOg-k1hhkPc6zkPXzPRh0+Q@mail.gmail.com \
    --to=hmatrjp@users.sourceforge.jp \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=translation-team-ja@lists.sourceforge.net \
    --cc=yasuakit@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).