From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: 35287@debbugs.gnu.org, "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Subject: bug#35287: dired-do-copy English beef-up
Date: Thu, 18 Apr 2019 23:59:19 +0300 [thread overview]
Message-ID: <87h8avhvx4.fsf@mail.linkov.net> (raw)
In-Reply-To: <bd2d36cd-2da0-4f7f-8230-889a45f90a60@default> (Drew Adams's message of "Wed, 17 Apr 2019 15:53:40 -0700 (PDT)")
>> >> > Copy: 11 files
>> >> > Actually "Copied 11 files" is proper English and doesn't leave us
>> >> > somewhat worrying...
>> >>
>> >> Other messages that use the same operation name:
>> >>
>> >> "Copy: 2 of 3 files skipped"
>> >> "Copy failed for 2 of 3 files"
>> >>
>> >> Shouldn't the latter be "Copying failed"?
>> >> So for every operation three verb forms are needed:
>> >> "Copy", "Copying", "Copied", correct?
>> >
>> > My own advice is to leave it alone.
>>
>> This is important in light of our efforts for i18n.
>
> You could perhaps use this:
>
> Copy * [2 files] to: ~/foobar/
> Copy: 2 files done
Then a complete set of messages:
Copy: 3 files done
Copy: 2 of 3 files skipped
Copy: 2 of 3 files failed
Copy: 2 files in 3 requests failed
next prev parent reply other threads:[~2019-04-18 20:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 11:49 bug#35287: dired-do-copy English beef-up 積丹尼 Dan Jacobson
2019-04-16 20:35 ` Juri Linkov
2019-04-16 21:57 ` Drew Adams
2019-04-17 19:04 ` 積丹尼 Dan Jacobson
2019-04-17 19:58 ` Juri Linkov
2019-04-17 22:53 ` Drew Adams
2019-04-18 10:28 ` 積丹尼 Dan Jacobson
2019-04-18 20:59 ` Juri Linkov [this message]
2019-04-18 21:10 ` Drew Adams
2019-04-19 2:08 ` 積丹尼 Dan Jacobson
2019-04-19 4:33 ` Drew Adams
2019-04-19 13:48 ` 積丹尼 Dan Jacobson
2019-04-19 14:28 ` Drew Adams
2019-04-19 15:03 ` Eli Zaretskii
2019-04-19 15:11 ` Drew Adams
2019-04-19 15:14 ` 積丹尼 Dan Jacobson
2019-04-24 20:15 ` Juri Linkov
2019-05-05 19:43 ` Juri Linkov
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=87h8avhvx4.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=35287@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=jidanni@jidanni.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.