From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: 35287@debbugs.gnu.org, "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Subject: bug#35287: dired-do-copy English beef-up
Date: Wed, 17 Apr 2019 15:53:40 -0700 (PDT) [thread overview]
Message-ID: <bd2d36cd-2da0-4f7f-8230-889a45f90a60@default> (raw)
In-Reply-To: <87d0lktp84.fsf@mail.linkov.net>
> >> > 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.
>
> > If you want, for "Copy" read "Copy operation" or
> > "Operation Copy".
>
> "Operation Copy" is a catchy name.
If you want to play with this then perhaps try to
keep the operation name as is (e.g. "copy") - don't
conjugate it or try to make a sentence/phrase.
What we have traditionally done with messages is this:
Copying...
Copying...done
But the `dired-do-*' framework really calls always for
an operation name (e.g. "copy", not "copying"). You
could perhaps use this:
Copy * [2 files] to: ~/foobar/
Copy: 2 files done
And in case of a failure, what we have now is fine:
Copy: 1 of 2
Copy ‘d:/foo/a.el’ to ‘d:/foo/b.el’ failed:
(file-already-exists File already exists d:/foo/a.el)
Yes, the first line can be confusing on its own, but it's
OK with the second line. And we definitely don't want
to say "Copy: 1 of 2 done" - the entire attempt to copy
is done, not just the attempt of one file. We could
alternatively say "Copy: 1 of 2 succeeded".
IOW, just add "done" or "failed" or whatever to the
operation name to make clear: (1) that the operation
attempt is finished and (2) what the status of the
attempt is.
The point is to stick with "copy". Dunno what that
would mean for translation, e.g. using the (translated)
operation name and trying to tack on a (translated)
status word like "succeeded"/"failed".
I really wouldn't mess with the `dired-do-*' framework.
And I wouldn't worry too much about translation here.
I do agree with Dan that the way it is now (without a
"done" or "succeeded") it might be a bit confusing.
But I don't think the answer is to try using "Copying"
- conjugating etc.
Keep it simple and standard (in the sense of what Emacs
has long used). Try to fix any real ambiguity that
could be harmful, but don't go beyond that.
Just one opinion.
next prev parent reply other threads:[~2019-04-17 22:53 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 [this message]
2019-04-18 10:28 ` 積丹尼 Dan Jacobson
2019-04-18 20:59 ` Juri Linkov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bd2d36cd-2da0-4f7f-8230-889a45f90a60@default \
--to=drew.adams@oracle.com \
--cc=35287@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=juri@linkov.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).