Simulator Issues w/r/t l10n?

[Alex Keybl]

For 1.2, we want to ensure that localizers who want to use the simulator (https://addons.mozilla.org/en-US/firefox/addon/firefox-os-simulator/) for l10n verification can.

Through the grapevine, we're currently aware of:

* Differing truncated strings - screen size or DPI differences between simulator and devices
* Some hardware features being untestable - MMS, etc.

Any other issues that impact the simulator for l10n work? Thanks in advance!

-Alex

[Francesco Lodolo [:flod]]

2013/9/5 Alex Keybl <ake...@mozilla.com>

> For 1.2, we want to ensure that localizers who want to use the simulator (
> https://addons.mozilla.org/en-US/firefox/addon/firefox-os-simulator/) for
> l10n verification can.

> Any other issues that impact the simulator for l10n work? Thanks in
> advance!
>

I'd say the main problem is that the simulator does not contain languages
other than en-US, and for testing purposes the version on AMO is not
updated frequently enough.

There's currently a "l10n version" of the simulator but it's maintained
manually, without automatic updates (which reminds me it's been a while
from the last update...)
http://r2d2b2g.flod.org/

Francesco

[Michael Bauer]

Hiya

Font coverage probably? For our locale, I'm not sure for example if 204A
is covered.

That's the only one that springs to my mind.

Michael

05/09/2013 16:51, sgrìobh Alex Keybl:

> For 1.2, we want to ensure that localizers who want to use the simulator (https://addons.mozilla.org/en-US/firefox/addon/firefox-os-simulator/) for l10n verification can.
>
> Through the grapevine, we're currently aware of:
>
> * Differing truncated strings - screen size or DPI differences between simulator and devices
> * Some hardware features being untestable - MMS, etc.
>

> Any other issues that impact the simulator for l10n work? Thanks in advance!
>

> -Alex

[Archaeopteryx]

Hi,

thank you for asking for our input.

- Testing of strings: Testing a string or a string change could be
improved, e.g. like editing the text of a web page in desktop Firefox.
- Updates: At the current update interval of the simulator and with
likely scarce time frames for localization due to external constraints
(partners), it's a worse choice than the desktop emulators in
ftp://ftp.mozilla.org/pub/b2g/nightly/latest-mozilla-b2g18/ (but the
Windows one need extra love, see
https://bugzilla.mozilla.org/show_bug.cgi?id=832396#c3 )
- Branding: E.g. the browser in the simulator is unbranded. This is okay
as long as we aren't told to take screenshots in our language which will
be used outside Mozilla, e.g. for marketing-
- No minimum screen size? I don't know FxOS specs, but we are testing
with that fixed screen resolution. So I hope that nobody releases a
phone where the available space (relative to font size) is inferior than
in the simulator.

A few comments to the issues you already mentioned:
- Differing truncated strings - screen size or DPI differences between
simulator and devices: This can also be an issue if the vertical space
is limited (seen once in the first time tutorial where the last line on
a screen got significantly cropped in the simulator, but not on the phone).
- Some hardware features being untestable - MMS, etc.
These are spread over many apps and make verification of translation a
pain, but that's more a general gaia l10n issue.

Archaeopteryx / Sebastian

[Myk Melez]

On 2013/09/05 08:51, Alex Keybl wrote:
> For 1.2, we want to ensure that localizers who want to use the simulator (https://addons.mozilla.org/en-US/firefox/addon/firefox-os-simulator/) for l10n verification can.
>
> Through the grapevine, we're currently aware of:
>

> * Differing truncated strings - screen size or DPI differences between simulator and devices
We have two issues on screen size and DPI configurability:

* 272: Cannot set screen resolution of simulator
<https://github.com/mozilla/r2d2b2g/issues/272>
* 359: simulate DPI <https://github.com/mozilla/r2d2b2g/issues/359>


> * Some hardware features being untestable - MMS, etc.
I don't think we have an issue filed on MMS simulation yet. Please file
issues <https://github.com/mozilla/r2d2b2g/issues/new> on that one and
any others that are important for l10n! Note that some will be difficult
(like Bluetooth, which is currently impossible
<https://github.com/mozilla/r2d2b2g/issues/393>), although others will
be straightforward.

> Any other issues that impact the simulator for l10n work? Thanks in advance!

cc: ochameau so he's aware of this thread.

ochameau: Here's the archive of the conversation to date
<https://groups.google.com/d/topic/mozilla.dev.l10n/AtJGtdNy2mo/discussion>.

-myk

[Myk Melez]

On 2013/09/05 09:08, Francesco Lodolo [:flod] wrote:
> 2013/9/5 Alex Keybl <ake...@mozilla.com <mailto:ake...@mozilla.com>>

>
> For 1.2, we want to ensure that localizers who want to use the
> simulator
> (https://addons.mozilla.org/en-US/firefox/addon/firefox-os-simulator/)
> for l10n verification can.

> Any other issues that impact the simulator for l10n work? Thanks
> in advance!
>
>

> I'd say the main problem is that the simulator does not contain
> languages other than en-US, and for testing purposes the version on
> AMO is not updated frequently enough.
>
> There's currently a "l10n version" of the simulator but it's
> maintained manually, without automatic updates (which reminds me it's
> been a while from the last update...)
> http://r2d2b2g.flod.org/

I'm in discussions with joduinn to have RelEng take on build & release
responsibilities for the Simulator. RelEng produces both regular and
"localizer" nightly builds of B2G Desktop, so it seems like they should
be able to do the same for the Simulator.

cc: joduinn so he's aware of this issue.

joduinn: Here's the archive of the conversation to date
<https://groups.google.com/d/topic/mozilla.dev.l10n/AtJGtdNy2mo/discussion>.

-myk

[Myk Melez]

Hi Michael,

Support for native B2G fonts is issue 353
<https://github.com/mozilla/r2d2b2g/issues/353>, for which jryans
suggested he would have a fix.

cc: jryans so he's aware of this request.

jryans: Here's the archive of the conversation to date
<https://groups.google.com/d/topic/mozilla.dev.l10n/AtJGtdNy2mo/discussion>.

-myk

On 2013/09/05 10:05, Michael Bauer wrote:
> Hiya
>
> Font coverage probably? For our locale, I'm not sure for example if
> 204A is covered.
>
> That's the only one that springs to my mind.
>
> Michael
>
> 05/09/2013 16:51, sgrìobh Alex Keybl:

>> For 1.2, we want to ensure that localizers who want to use the
>> simulator
>> (https://addons.mozilla.org/en-US/firefox/addon/firefox-os-simulator/) for
>> l10n verification can.
>>

>> Through the grapevine, we're currently aware of:
>>
>> * Differing truncated strings - screen size or DPI differences
>> between simulator and devices

>> * Some hardware features being untestable - MMS, etc.
>>

>> Any other issues that impact the simulator for l10n work? Thanks in
>> advance!
>>

>> -Alex
>
> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n

[Myk Melez]

On 2013/09/05 10:36, Archaeopteryx wrote:
> - Branding: E.g. the browser in the simulator is unbranded. This is okay
> as long as we aren't told to take screenshots in our language which will
> be used outside Mozilla, e.g. for marketing-

I talked to Grace Jimenez in Product Marketing about using the Simulator
to create marketing videos a couple months ago, but we concluded that it
isn't feasible, even though it's relatively easy to produce a branded
version of the Simulator, because the Simulator doesn't support some of
the user activities we would want to highlight in such videos, like
placing a phone call.

I think Marketing ended up using real devices to shoot those videos, and
I expect they'll continue to do so.

-myk