Last modified: 2014-07-07 23:04:38 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 T68944, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 66944 - iOS App: bad unlocalized API message with {{PLURAL:}} shown to user
iOS App: bad unlocalized API message with {{PLURAL:}} shown to user
Status: NEW
Product: Wikipedia App
Classification: Unclassified
iOS App (Other open bugs)
Alpha
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
: i18n
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-22 06:57 UTC by Kunal Mehta (Legoktm)
Modified: 2014-07-07 23:04 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: iOS 7.x
Assignee Huggle Beta Tester: ---


Attachments
screenshot (98.63 KB, image/png)
2014-06-22 06:57 UTC, Kunal Mehta (Legoktm)
Details

Description Kunal Mehta (Legoktm) 2014-06-22 06:57:51 UTC
Created attachment 15697 [details]
screenshot

When creating an account and leaving the password fields empty, an unparsed PLURAL shows up. See screenshot.
Comment 1 Kunal Mehta (Legoktm) 2014-06-22 08:25:51 UTC
Hmm, this is actually the API returning the un-parsed PLURAL.

ApiCreateAccount calls dieStatus, which uses Message::plain() instead of Message::text().
Comment 2 Dan Garry 2014-06-23 20:11:41 UTC
(In reply to Kunal Mehta (Legoktm) from comment #1)
> Hmm, this is actually the API returning the un-parsed PLURAL.
> 
> ApiCreateAccount calls dieStatus, which uses Message::plain() instead of
> Message::text().

So this is a bug with the API then? Closing the app bug.
Comment 3 Kunal Mehta (Legoktm) 2014-06-23 21:23:23 UTC
Well, it's still a bug in the app, since users shouldn't ever see a raw {{PLURAL:}}. It might need to be fixed in the API, not really sure if the app can transform PLURAL messages on its own.
Comment 4 Kunal Mehta (Legoktm) 2014-07-05 10:29:43 UTC
Nope, this is definitely a bug in the app, but a different reason. The API will always return a message in English, meaning the user will not see a localized message. The app should store its own copy of the localized message to show to the user depending on the API response code.
Comment 5 Brion Vibber 2014-07-07 23:04:38 UTC
(updated summary)

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


Navigation
Links