From: Federico Bruni <fede@inventati.org>
To: Translation Project <tp@lists.linux.it>
Cc: libc-alpha <libc-alpha@sourceware.org>,
primes2h@ubuntu.com, dforsi@gmail.com,
Carlos O'Donell <carlos@redhat.com>
Subject: Re: Updating Italian libc translation for ESTALE in glibc
Date: Mon, 17 Apr 2023 23:15:18 +0200 [thread overview]
Message-ID: <I13ATR.KD7RBK7L8A4F2@inventati.org> (raw)
In-Reply-To: <CAN_we7N=nq4TgWWK2ntsNCLSf0WP4nRkd999Zd1kpyqD75VEeA@mail.gmail.com>
Il giorno lun 17 apr 2023 alle 22:46:35 +0200, Daniele Forsi
<dforsi@gmail.com> ha scritto:
> Hello Carlos,
>
>> I have an Italian translation for ESTALE that could be used.
>
> the translations that you quoted are wrong because they are
> translating "handle" as "handling"
>> msgstr "Gestione del file NFS interrotta"
>> msgstr "Gestione file obsoleti"
>
>
> the word "handle" is difficult to translate in this context and I
> don't know a translation for "stale" in this context better than the
> one in RHEL6 and RHEL7, however I would use a singular form, so I
> suggest:
> msgid "Stale file handle"
> msgstr "Handle di file obsoleto"
>
> I found some hits on search engines for "handle di file" but none for
> "handle di file obsoleto"
>
I think "handle" should be translated.
There's no Italian translation in Wikipedia:
https://en.wikipedia.org/wiki/Handle_(computing)
As it's described as an abstract reference to a resource (a file), I
would use the translation of reference, that is:
"Riferimento obsoleto al file"
"Riferimento al file obsoleto"
Which one sounds better?
The handle is stale (not the file), right?
next prev parent reply other threads:[~2023-04-17 21:19 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 [this message]
2023-04-18 13:42 ` Carlos O'Donell
2023-04-18 20:39 ` Federico Bruni
2023-04-20 16:13 ` Sergio Zanchetta
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=I13ATR.KD7RBK7L8A4F2@inventati.org \
--to=fede@inventati.org \
--cc=carlos@redhat.com \
--cc=dforsi@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=primes2h@ubuntu.com \
--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).