From: Sergio Zanchetta <primes2h@ubuntu.com>
To: Federico Bruni <fede@inventati.org>, carlos@redhat.com
Cc: Translation Project <tp@lists.linux.it>,
dforsi@gmail.com, libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Updating Italian libc translation for ESTALE in glibc
Date: Thu, 20 Apr 2023 18:13:23 +0200 [thread overview]
Message-ID: <CA+a_VgxdBHyh21F+eu4idysdC1eECbFfoGbEmv1DF-jBYhmTeA@mail.gmail.com> (raw)
In-Reply-To: <J2WBTR.AZ48S74504U13@inventati.org>
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
Il giorno mar 18 apr 2023 alle ore 22:43 Federico Bruni <fede@inventati.org>
ha scritto:
>
>
> Il giorno mar 18 apr 2023 alle 09:42:41 -0400, Carlos O'Donell
> <carlos@redhat.com> ha scritto:
>
> >
> > It would be great to get a translation for this for libc, since
> > ESTALE is
> > an important error return for filesystem access functions.
> >
> > Is there anything I can do to support adding a translation for
> > Italian?
> >
>
> The translation is managed by the Translation Project?
> This one?
> https://translationproject.org/domain/libc.html
>
> I see now that the assigned translator Sergio is here in Cc.
>
>
@Federico
I think that Carlos didn't get your reply so I added him in this one.
Hello all !
I agree about the first one too, "Riferimento obsoleto al file".
@Carlos
I'm a little bit busy right now but I try to do as much as I can to have
that string translated ASAP.
Let me know if there are any other strings you need translated in a short
time.
prev parent reply other threads:[~2023-04-20 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 17:48 Carlos O'Donell
2023-04-17 20:46 ` Daniele Forsi
2023-04-17 21:15 ` Federico Bruni
2023-04-18 13:42 ` Carlos O'Donell
2023-04-18 20:39 ` Federico Bruni
2023-04-20 16:13 ` Sergio Zanchetta [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=CA+a_VgxdBHyh21F+eu4idysdC1eECbFfoGbEmv1DF-jBYhmTeA@mail.gmail.com \
--to=primes2h@ubuntu.com \
--cc=carlos@redhat.com \
--cc=dforsi@gmail.com \
--cc=fede@inventati.org \
--cc=libc-alpha@sourceware.org \
--cc=tp@lists.linux.it \
/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).