Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upstandardize & improve language around inter-vm file transfers #1040
Comments
mfc
changed the title from
standard & improve word choice around inter-vm file transfers
to
standardize & improve word choice around inter-vm file transfers
Jun 29, 2015
mfc
changed the title from
standardize & improve word choice around inter-vm file transfers
to
standardize & improve language around inter-vm file transfers
Jun 29, 2015
marmarek
added
enhancement
C: templates
P: minor
labels
Sep 1, 2015
marmarek
added this to the Release 3.1 milestone
Sep 1, 2015
mfc
added
the
UX
label
Dec 1, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mfc
Jan 14, 2016
Member
i'm pretty sure this went in the wrong direction @adrelanos.
now whonix, debian, and fedora are all unified in language (yay!) but not ordering, and the language change is the wrong one, to:
- send to VM
- move to VM
As originally mentioned "send" is used semantically incorrectly here, it needs to be "copy":
- copy to VM
- move to VM
|
i'm pretty sure this went in the wrong direction @adrelanos. now whonix, debian, and fedora are all unified in language (yay!) but not ordering, and the language change is the wrong one, to:
As originally mentioned "send" is used semantically incorrectly here, it needs to be "copy":
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Michael Carbone:
Why me? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mfc
Jan 14, 2016
Member
Why me?
haha didn't mean for it to sound scary. the language in Whonix template-derived AppVMs changed from "Copy to Other VM..." to "Send to Other VM" and I figured you are responsible for Whonix template changes?
haha didn't mean for it to sound scary. the language in Whonix template-derived AppVMs changed from "Copy to Other VM..." to "Send to Other VM" and I figured you are responsible for Whonix template changes? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jan 14, 2016
Member
On Thu, Jan 14, 2016 at 03:01:14AM -0800, Michael Carbone wrote:
haha, didn't mean for it to sound scary. the language in Whonix template-derived AppVMs changed from "Copy to Other VM..." to "Send to Other VM" and I figured you are responsible for Whonix template changes?
This is just part of qubes packages installed there, the same as in
other templates. Visual differences are because Whonix uses dolphin as
file manager (right?), which is configured separately from Nautilus file
manager (used by default in Fedora templates).
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
On Thu, Jan 14, 2016 at 03:01:14AM -0800, Michael Carbone wrote:
This is just part of qubes packages installed there, the same as in Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mfc
Jan 14, 2016
Member
ah thanks for the clarification. I'm highlighting the differences in wording primarily (how "send" should be "copy"), rather than order which is a second issue -- ie the order of the options is different in dolphin and nautilus in Debian-based AppVMs for instance.
|
ah thanks for the clarification. I'm highlighting the differences in wording primarily (how "send" should be "copy"), rather than order which is a second issue -- ie the order of the options is different in dolphin and nautilus in Debian-based AppVMs for instance. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Jan 14, 2016
Member
Yes, but I wouldn't change these messages in Whonix only. Especially not
without discussing it in a ticket. These messages are defined by
packages provided by Qubes only.
|
Yes, but I wouldn't change these messages in Whonix only. Especially not |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Jan 14, 2016
Member
Marek Marczykowski-Górecki:
Visual differences are because Whonix uses dolphin as
file manager (right?)
Yes.
|
Marek Marczykowski-Górecki:
Yes. |
marmarek
modified the milestones:
Release 3.1,
Release 3.1 updates
Feb 8, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mfc
May 5, 2016
Member
right, so it sounds like it is Dolphin menu language (provided by Qubes) that need to be improved? Whether it is Dolphin in Debian, Whonix, Fedora, etc. That will ensure the user finds the same language (and ideally same order) as in Nautilus.
|
right, so it sounds like it is Dolphin menu language (provided by Qubes) that need to be improved? Whether it is Dolphin in Debian, Whonix, Fedora, etc. That will ensure the user finds the same language (and ideally same order) as in Nautilus. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Yes.
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mfc
Oct 5, 2016
Member
I think this is a pretty easy fix, we just need the Dolphin context menu text string to be the same as the Files/Nautilus language: both "Copy To VM" (rather than "Send To VM").
|
I think this is a pretty easy fix, we just need the Dolphin context menu text string to be the same as the Files/Nautilus language: both "Copy To VM" (rather than "Send To VM"). |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
@andrewdavidwong Confirmed issue still arises in 3.2 milestone |
mfc commentedJun 29, 2015
in Fedora templates, the Action Menu wording for inter-vm file transfers is a bit ambiguous and confusing:
"Send to" semantically suggests the original is not kept, which is not true.
In Whonix templates the Action Menu is clearer with "Copy to" being used instead of "Send to":
Note the different ordering as well.
I would recommend the implementation of the Whonix template practices in the other templates, both in wording (as they are clearer) and ordering (as isolating the Disposable VM option from the others makes sense).
And it may make sense to flatten the menu by removing the Action parent, as Whonix templates has done. That would make it faster for users to select the appropriate option.