I love this idea, Rodrigo.

As Axel pointed out, we need some sort of screenshot-string mapping.

Then, things like this will be trivial to implement:
https://www.dropbox.com/s/n89g0tn288geaz4/thumbnails.png?dl=0

-Matjaž

On Thu, Mar 3, 2016 at 10:35 PM, Axel Hecht <l...@mozilla.com> wrote:
> On 03/03/16 13:06, Rodrigo Waters wrote:
>>
>> Hi Stefan,
>>
>> Last week I had a similar idea,
>>
>> My idea was:
>>
>> - Create a page in the wiki (or any other service that is more correct)
>> - List all screens (iOS and Android)
>> - In each image there will be a link to potoon to translate that
>> specifically screen
>
>
> I'm not sure if pontoon offers links to particular entities. Let alone to a
> non-sequential list of them, which is what you'd likely see in real
> screenshots.
>
> That said, creating a mapping between screenshots and strings would be nice.
>
> Stefan, could one monkeypatch NSLocalizedString to keep track of which
> strings got retrieved? Also, is that the only way to get strings localized
> on iOS, or are there more?
>
> Wondering if one could amend the tests to watch those, and keep track of
> which strings got pulled from l10n and store that somewhere.
>
> Axel
>
>>
>> This would facilitate those who are not yet fully involved in the project,
>> or found the wrong string and do not know where to find
>>
>>
>> It would be a valid idea? Or my madness? :)
>>
>>
>> Att's
>> Rodrigo Waters
>>
>> 2016-03-02 23:52 GMT-03:00 Stefan Arentz <sare...@mozilla.com>:
>>
>>> Hello everyone,
>>>
>>> We’ve been working on automated screenshots for Firefox for iOS. You can
>>> see some initial progress here for a subset of our supported locales:
>>>
>>>     http://people.mozilla.org/~sarentz/fxios/screenshots/
>>>
>>> If you navigate to a specific locale and then open the screenshots.html
>>> file, you are presented with a image gallery that contains screenshots of
>>> the application for the iPhone 4S, 5S and 6S. These all have different
>>> screen sizes. You can navigate the images in the gallery with the arrow
>>> keys.
>>>
>>> By tomorrow (EST) all locales should have been processed and show up
>>> there. (It takes about 7 minutes per locale on my MacBook Pro). We will
>>> try
>>> to run this frequently during the Firefox for iOS localization period, so
>>> that you can see your work in action and catch rendering problems early.
>>>
>>> This is a big effort and we have only made a small start. There is a lot
>>> of work to do to get full coverage. We will have to work on this
>>> incrementally. If you want screenshots of a specific screen or scenario,
>>> please let us know and we will try to prioritize those.
>>>
>>>  S.
>>>
>>>
>>> _______________________________________________
>>> mobile-firefox-dev mailing list
>>> mobile-firefox-dev@mozilla.org
>>> https://mail.mozilla.org/listinfo/mobile-firefox-dev
>>>
>>>
>
> _______________________________________________
> dev-l10n mailing list
> dev-l...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n
_______________________________________________
mobile-firefox-dev mailing list
mobile-firefox-dev@mozilla.org
https://mail.mozilla.org/listinfo/mobile-firefox-dev

Reply via email to