Closed
Bug 1215569
Opened 9 years ago
Closed 7 years ago
Some BuddyUp strings have poor grammar.
Categories
(support.mozilla.org :: BuddyUp, defect)
support.mozilla.org
BuddyUp
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Tonnes, Unassigned)
References
Details
When selecting a locale using the locale list in "Recent revisions" on the KB dashboard, the "Any" item at the top is not localized. Please add that to the db. Also, a few new string were added recently that may need to be reviewed/changed. - "Unable to login with provided credentials." -> As "login" is a noun, this should probably be "to log in". - "A user with that email address already exists." - "A user with that username exists" -> Not sure if the second needs a trailing period as well, or neither of them do instead. - "Usernames may only be letters, numbers, "." and "-". -> I think "contain" would be better than "be", like elsewhere. If those changes need a separate bug, please let me know.
Comment 2•9 years ago
|
||
It is best not to conflate issues in Bugzilla. It seems you found the "Any" string through the UI, and that you found the BuddyUp strings by looking at the strings file. In particular, one of the issues here is that one string is not in the localization system at all, and the other issue is that the some strings have grammar problems. Those are very different problems. If you're confident that the various changes are very very closely related, having one bug is fine, but in this case, this should have been two bugs. Generally, it is probably better to err on the side of filing more bugs. To that goal, I've split the smaller issue of your bug, the "Any" string, into bug 1215660
Updated•9 years ago
|
Summary: Make "Any" in Recent revisions list localizable → Some BuddyUp strings have poor grammar.
Comment 3•7 years ago
|
||
SUMO has moved to Lithium and this bug is for a SUMO project that isn't around anymore. Given that, I'm closing as WONTFIX.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•