Last modified: 2013-09-20 05:18:42 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T42035, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 40035 - VisualEditor: Edit summary length counter confusing when in bytes
VisualEditor: Edit summary length counter confusing when in bytes
Status: RESOLVED FIXED
Product: VisualEditor
Classification: Unclassified
Editing Tools (Other open bugs)
unspecified
All All
: Unprioritized normal
: VE-deploy-2012-09-17
Assigned To: Rob Moen
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-06 00:49 UTC by Krinkle
Modified: 2013-09-20 05:18 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Krinkle 2012-09-06 00:49:10 UTC
Assuming we implement bug 39558. That means the counter in the corner of the save dialog will be decreasing more than 1 per character on average.

English users will likely not notice it as quickly, but € (EURO SYMBOL) for instance is 3 bytes. And in foreign languages it will be more common entirely.

Right now the counter has no unit, which would be confusing (the natural expectation is to assume character count). We can add a unit word "# bytes" instead. But I'm not sure that is an improvement, do we want to face users with that?
Comment 1 Church of emacs 2012-09-06 08:20:04 UTC
Note that this is a consequence of bug 4715. Right now we just cut off the comment if it is too long; adding a confusing, but correct counter helps a lot.

Now to the question: I think adding the word "bytes" would help, since (a) some people know what a byte is and (b) even those who don't and see that the counter differs from a character counter may realize that "bytes" can mean something else. They probably don't assume it is a character counter if there is an unknown term behind the number and so they have less expectation and get less confused if the counter differs from their expectation.
Comment 2 James Forrester 2012-09-06 16:38:50 UTC
Appending " bytes" seems like a reasonable compromise here (though the i18n will be fun).
Comment 3 Rob Moen 2012-09-11 19:36:19 UTC
Went with bytes for the time being.  Will change when core bug fixed.
Patched in https://gerrit.wikimedia.org/r/23451
Comment 4 Siebrand Mazeland 2012-09-11 19:48:27 UTC
(In reply to comment #2)
> Appending " bytes" seems like a reasonable compromise here (though the i18n
> will be fun).

I've -1-ed the patch mentioned in comment 3 for not being understandable to users. We should provide them with a reasonable indication of how many more characters they can insert.

Is it possible to do something with the average number of bytes per character for what's already been typed, and give an indication like "~n characters remaining"?

P.s. issue should be closed when patch is merged, not when it's submitted.
Comment 5 James Forrester 2012-09-17 16:56:24 UTC
Merged and to be deployed in wmf12 train.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links