The last export from this week has not yet landed in Pootle. I'm hoping Dwayne will speak to this when he's able.
Jeff El jul. 9, 2015 6:46 PM, "Stefan Arentz" <[email protected]> escribió: > Hi Martin, the strings you mention, the quickstart, should be in the last > export. Do they not show up in Pootle for you? > > Can you be more specific about the menu items? If we missed something then > I'd like to open a bug for it. > > S. > > On Thu, Jul 9, 2015 at 6:29 PM, Martin Jernberg <[email protected] > > > wrote: > > > Will continue to translate after the freeze any date when its over and we > > can start to translate for build 23, also strings for the quickstart > guide > > and some menu items need to be added into Pootle for Swedish L10n > > ________________________________________ > > From: mobile-firefox-dev [[email protected]] On > > Behalf Of Stefan Arentz [[email protected]] > > Sent: 08 July 2015 16:03 > > To: Brian Nicholson > > Cc: dev-l10n; mobile-firefox-dev > > Subject: Re: [iOS] String freeze this week > > > > On Tue, Jul 7, 2015 at 4:34 PM, Brian Nicholson <[email protected] > > <mailto:[email protected]>> wrote: > > Can someone summarize where we are now with the string freeze, and > > what the freeze covers? > > > > I think we are pretty much string complete for non-a11ly strings. > > > > The export that I did yesterday included the last extra feature that was > > in flight, the View Later action extension. > > > > If anyone is aware of other functionality that needs to land, this is the > > time to let us know. > > > > > > Namely, are a11y strings included in the freeze? If so, I think our > > a11y strings are far from complete -- we continue to get PRs from > > dusek (our awesome a11y contributor) that contain NSLocalizedString > > additions. > > > > So I did not take a11y into account. Well, I sort of did, but as you are > > saying more patches are coming in. I kind of assumed that 'we will take > > whatever we can get'. But if that does not work with a11y then maybe we > > need to land those patches later so that we can land them fully > localized? > > We can always do small incremental updates after our v1 with a11y > > improvements. > > > > Also, I expect that we'll be adding/updating a11y labels as > > we continue to refine our UI tests since KIF and a11y strings are > > tightly coupled. > > > > Emily ran into an issue where labels are sometimes unpredictable. Like > > when they are dynamic. I wonder if we should start using accessibility > > identifiers more consistently instead. AFAIK those are not end-user > facing > > and can be used to pinpoint specific elements without relying on strings > or > > localized strings. What do you think? > > > > S. > > > > > _______________________________________________ > dev-l10n mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-l10n >
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
