|
List Info Thread: user barrier - ambiguity about "content" vs "upload content from file"
[1-3]
|
||||||||||||||||||||||||||||
|
about | contact Other archives ( Real Estate discussion Medical topics ) |
||||||||||||||||||||||||||||
user barrier - ambiguity about "content" vs "upload content from file" |
|
List Info Thread: user barrier - ambiguity about "content" vs "upload content from file"
[1-3]
|
||||||||||||||||||||||||||||
|
about | contact Other archives ( Real Estate discussion Medical topics ) |
||||||||||||||||||||||||||||
also had problems is the following.
When the user would like to publish a non-text media item,
s/he
clicks on publish and then looks for the place where a
non-text item
should go.
S/he sees:
"Content:" - a box for text
Below this, "Upload content from file:"
His/her natural interpretation, based on the idealised
logical axiom
that A==A, or "content" == "content", is
that the box for uploading a
file is intending for uploading *text* from a file.
Since s/he wishes to upload an image and not text, s/he
thinks that this
is clearly not the right place and that uploading images,
audio, video
probably doesn't work/hasn't been installed, whatever.
Of course, the two usages of the word "content"
have different contexts,
the first is something like content.is_text? and the
second something
liek content AND !content.is_text? (probably wrong ruby
syntax, sorry).
To the programmer, this is OK. To the user, this is
discouraging.
IMHO we must change this to something where the risk of the
user
misinterpreting the text string is minimised.
The source of the question is here:
/lib/samizdat/engine/message.rb
538: [:label, 'file', _('Upload content from
file')],
SUGGESTIONS:
(1) "Upload multimedia from file:"
(2) "Upload multimedia content from file:"
(3) "Upload image (or other non-text medium) from
file:"
(4) "Upload image (audio, video, ...):"
(5) "Upload image/audio/video:"
ARGUMENTS FOR/AGAINST:
(1) "Upload multimedia from file:"
FOR: fashionable
AGAINST: fashionable; literally wrong (image or audio is a
monomedium)
(2) "Upload multimedia content from file:"
FOR: fashionable, shorter than (1)
AGAINST: fashionable; literally wrong (image or audio is a
monomedium)
(3) "Upload image (or other non-text medium) from
file:"
FOR:
AGAINST: long; many people don't know that (en) "1
medium + 1 medium = 2 media"
(4) "Upload image (audio, video, ...):"
FOR: probably my favourite
AGAINST:
(5) "Upload image/audio/video:"
FOR:
AGAINST: hardwired (might be other types of media in
future?)
i don't have strong opinions between these 5 or similar
options,
but i think the present text string is a problem.
ALTERNATIVE SOLUTION:
"Content:" becomes "Text content:"
"Upload content from file:"
becomes
"Upload other content from file:" or
"Upload non-text content from file:"
Literally speaking, this would be correct.
Argument against: "Text content" is a more complex
expression than
"Content".
cheers
boud
_______________________________________________
samizdat-devel mailing list
samizdat-devel
nongnu.org
(...)
> His/her natural interpretation, based on the idealised
logical axiom
> that A==A, or "content" ==
"content", is that the box for uploading a
> file is intending for uploading *text* from a file.
And they might be right: it used to be possible to upload
texts, too.
I just tried that and found that it no longer works due to a
bug that
I'll try to fix.
One other thing that used to confuse people here was that
they assumed
that upload was in addition to the text, not in place of it.
Whatever
text we choose, we need to make sure we don't reintroduce
this
confusion.
How about something like this:
"Alternatively, upload a file (formats supported:
%s)", where %s is
formed from config['format'].
--
Dmitry Borodaenko
_______________________________________________
samizdat-devel mailing list
samizdat-devel