Closed
Bug 975982
Opened 11 years ago
Closed 11 years ago
Firefox OS devices page: improve consistency and fix errors in strings
Categories
(www.mozilla.org :: Pages & Content, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: flod, Assigned: jpetto)
Details
(Whiteboard: [kb=1282778] )
Attachments
(4 files, 1 obsolete file)
I've been reviewing the strings before l10n extraction. Not sure if all of them are actually needed besides the first one, but it would be useful to fix them before we expose strings to localizers.
* Don't use CSS to add : after "Find a device in:"
* Consistently use a space between number and unit of measurement (http://physics.nist.gov/cuu/Units/checklist.html)
There are still some issues I think:
* Alcatel: it says "SD memory card" in Features but it's actually MicroSD (correct in specifications). Specification: 25 MB of RAM is correct? Also, any reason for using "Memory & RAM" instead of just "Memory" like other phones at section title?
* LG: "Up to 8 h (2G), 8 h (3G)" doesn't sound right, first number should be higher than the second.
Reporter | ||
Comment 1•11 years ago
|
||
Updated•11 years ago
|
Whiteboard: [kb=1282778]
Comment 2•11 years ago
|
||
Commits pushed to master at https://github.com/mozilla/bedrock
https://github.com/mozilla/bedrock/commit/fff36cba0bc5dcd5b92556267a2157dc1c657b03
Bug 975982 - Improve strings in Firefox OS Devices page
https://github.com/mozilla/bedrock/commit/17262b4f55373ce04bafbe091a1dade71ab82a34
Merge pull request #1728 from flodolo/fxos_devices
Bug 975982 - Improve strings in Firefox OS Devices page
Assignee | ||
Comment 3•11 years ago
|
||
Just as a heads up, there are updates to the phone specs coming soon, so if you *were* going to localize the specs, I would hold off for now.
Reporter | ||
Comment 4•11 years ago
|
||
Yes, agibson pointed me to the two bugs and we already discussed with Pascal, so we're waiting for now.
I think we can close this bug now and discuss the other two issues in those bugs.
Assignee: nobody → francesco.lodolo
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 5•11 years ago
|
||
fixed on stage https://www.allizom.org/en-US/firefox/os/devices/
Comment 6•11 years ago
|
||
verified fixed https://www.mozilla.org/en-US/firefox/os/devices/
Status: RESOLVED → VERIFIED
Comment 7•11 years ago
|
||
add "Poland" to the list of countries
Comment 8•11 years ago
|
||
I wonder how useful the "Keyboard Virtual QWERTY " is. I suppose you can also use virtual AZERTY or other types (depending on the country). It seems to me it might be difficult to update and info not really relevant for end users.
Comment 9•11 years ago
|
||
standby time : use "days + hours" instead of hours
to make it more meaningful for end-users. (what do 176 h really represent ?)
Comment 10•11 years ago
|
||
MEMORY, MEMORY & RAM etc.
have a consistent feature for ALL devices.
I'd recommend : "MEMORY" as a title. Then RAM, ROM and Expansion slot.
add a comment for "ROM" that end-user memory can be less than total ROM (internal memory) depending on manufacturer/operator implementation.
Assignee | ||
Comment 11•11 years ago
|
||
Natalia: Would you like to re-open this bug, or are the above comments for discussion purposes only at this time?
Also, was there something more needed in terms of adding "Poland" to the list of countries for the Alcatel OneTouchFire?
Comment 12•11 years ago
|
||
Oh, yes, I thought it was open ! My comments are requests for fixing.
For the AlcatelOneTouchFire, only Poland to be added, thanks.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 13•11 years ago
|
||
Hey Natalia:
Can you confirm what the "Memory" section for each device should read? Currently, each one is slightly different, and I want to make sure the update makes sense.
I'll be removing the "Keyboard" section from all devices, and converting all standby hour values to "x days + y hours".
Poland is already in the list of countries for the OneTouchFire - was there anything else needed here?
Comment 14•11 years ago
|
||
Thanks for adding 'Poland'. J
Comment 15•11 years ago
|
||
Can we please keep 'hours' as this is how standby and talktime is reflected with all mobile phones, so from a consistency POV people can see immediately that Firefox OS performs better. J
Assignee | ||
Updated•11 years ago
|
Assignee: francesco.lodolo → jon
Assignee | ||
Comment 16•11 years ago
|
||
Natalia & John -
Any confirmation on these requests?
Comment 17•11 years ago
|
||
Jon,
Recommendations :
"MEMORY" as a title. Then RAM, ROM and Expansion slot.
Keep 'hours' as this is how standby and talktime is reflected with all mobile phones.
Remove 'keyboard'.
Thanks. J
Assignee | ||
Comment 18•11 years ago
|
||
Hi John and/or Natalia:
Can you please confirm the following "Memory" sections for each phone?
* Alcatel One Touch Fire:
-- current
Internal memory
160 MB, 512 MB ROM, 25 MB RAM
Card slot
MicroSD up to 32 GB, 2 GB included
-- proposed new
ROM
512 MB
RAM
25 MB
Expansion slot
MicroSD up to 32 GB, 2 GB included
What happens to the "160 MB" value in the current "Internal" heading?
* LG Fireweb
-- current
Internal
2 GB
Card slot
MicroSD card: up to 32 GB
-- proposed new
ROM
??
RAM
??
Expansion slot
MicroSD up to 32 GB, 2 GB included
What happens to the "2 GB" value in the current "Internal" heading?
* ZTE Open
-- current
Internal memory
512 MB NAND + 256 MB RAM
End user memory
130 MB
External storage
MicroSD card: up to 32 GB
-- proposed new
ROM
512 MB
RAM
256 MB
Expansion slot
MicroSD card: up to 32 GB
What happens to the "130 MB" value in the current "End user memory" heading?
Flags: needinfo?(jbernard)
Comment 20•11 years ago
|
||
Hi,
for all "internal memory" heading, please use the ROM size. If that's possible, we can add a footnote to "internal memory" and also to "ROM" explaining : "Available storage for user content varies depending on the version and is subject to change based on phone software updates and apps usage."
* Alcatel One Touch Fire (there was a typo for the RAM):
-- proposed new
ROM
512 MB
RAM
256 MB
Expansion slot
MicroSD up to 32 GB, 2 GB included
* LG Fireweb
-- proposed new
ROM
4 GB
RAM
512 MB
Expansion slot
MicroSD up to 32 GB
* ZTE Open
-- proposed new
ROM
512 MB
RAM
256 MB
Expansion slot
MicroSD card: up to 32 GB
* Huawei Y300
-- proposed new
ROM
512 MB
RAM
256 MB
Expansion slot
MicroSD card: up to 32 GB
Comment 21•11 years ago
|
||
Sorry press "save" too early...
For Huawei :
* Huawei Y300
-- proposed new
ROM
4 GB
RAM
256 MB
Expansion slot
MicroSD card: up to 32 GB
I've added Wayne in the bug as he can confirm the memory sizes for LG and Huawei devices.
Thanks.
Flags: needinfo?(wchang)
Comment 22•11 years ago
|
||
Hi,
LG Fireweb is now also available in Uruguay with Movistar so please also update this.
thanks a lot !
Comment 23•11 years ago
|
||
Both the Fireweb and Y300II (note the II) have 512/4GB config, so:
* LG Fireweb
-- proposed new
ROM
4 GB
RAM
512 MB
Expansion slot
MicroSD up to 32 GB
* Huawei Ascend Y300 II
-- proposed new
ROM
4 GB
RAM
512 MB
Expansion slot
MicroSD card: up to 32 GB
(In reply to Natalia Martinez-Winter from comment #20)
> for all "internal memory" heading, please use the ROM size. If that's
> possible, we can add a footnote to "internal memory" and also to "ROM"
> explaining : "Available storage for user content varies depending on the
> version and is subject to change based on phone software updates and apps
> usage."
>
Yes, do note the 4GB indicated is the total internal memory, some of which is used by the OS. It is not what's available for the user to see or use.
Flags: needinfo?(wchang)
Assignee | ||
Comment 24•11 years ago
|
||
I've got a pull request in (https://github.com/mozilla/bedrock/pull/1875) for the changes above. Should be live early next week. Attaching a screenshot of what the new memory section will look like (Huawei Y300II used as an example).
Assignee | ||
Comment 25•11 years ago
|
||
Comment 26•11 years ago
|
||
Hi Jon,
there are 2 things to update :
1) in the "features" tab of each device : please use the ROM size and call it' "Internal memory" and add the footnote.
2) in the "specifications" tab of each device : please ONLY use what we agreed before :
ROM, RAM and expansion slot. (with footnote after "ROM")
So, as an example, in the screenshot you attached, please remove "Internal memory" (it's redundant with ROM...).
thanks a lot.
Assignee | ||
Comment 27•11 years ago
|
||
Ah, that makes much more sense. I've updated the PR. Two new screenshots attached (again, using the Y300II as an example).
Assignee | ||
Comment 28•11 years ago
|
||
Attachment #8405424 -
Attachment is obsolete: true
Assignee | ||
Comment 29•11 years ago
|
||
Comment 30•11 years ago
|
||
yes !!!
thanks.
Please also don't forget comment 22 : add Uruguay for LG Fireweb.
Also : any chance we can improve the "availability" highlight once a country is selected ? or only list the ones that are actually available ? or change the order ?
Assignee | ||
Comment 31•11 years ago
|
||
(In reply to Natalia Martinez-Winter from comment #30)
> yes !!!
> thanks.
> Please also don't forget comment 22 : add Uruguay for LG Fireweb.
Yep, I've got Uruguay added for the LG Fireweb.
>
> Also : any chance we can improve the "availability" highlight once a country
> is selected ? or only list the ones that are actually available ? or change
> the order ?
We've got a page re-design/refresh in the pipeline already. I think it would be best get these copy updates out and add the above to the updated UI discussion.
Comment 32•11 years ago
|
||
Commits pushed to master at https://github.com/mozilla/bedrock
https://github.com/mozilla/bedrock/commit/126dc4c035710b514c27f41f02fa8e8effe6c96c
Standardize memory specs on fxos devices. Bug 975982.
- Remove keyboard section from specs.
- Add Uruguay to LG Fireweb available countries.
- Update Huawei phone name to Y300II.
https://github.com/mozilla/bedrock/commit/8b3852ceeb07798b328d847b40d09f278f544d55
Merge pull request #1875 from jpetto/bug-975982-fxosdevices-memory-updates
Standardize memory specs on fxos devices. Bug 975982.
Assignee | ||
Updated•11 years ago
|
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•