If strings are en-only, we do not "wrap" them in a tag that means "translate this string." It's a low-tech solution that has worked well so far. Extracting strings for only a set of locales is something we aren't currently set up for, and I don't have an estimate on what kind of effort it would be to make that happen, though I suspect more than non-trivial.
Shane On Thu, Aug 8, 2019 at 6:03 PM Peiying Mo <[email protected]> wrote: > Thank you for sharing all the information. > > We want to do as much as we can help communities prioritize their loads, > including separating the ones that are US market only from the rest. Is > there a way in the code that can hide these strings from showing up in > Pontoon? Is it possible to create a separate file for en-US only if that's > easier to do? In the future, if we decide to open up the strings to Germany > or France for example, we can add more locales to the file(s). > > The communities are aware the importance of FxA product. If some of these > features will never roll out in their markets, it's a waste of their time > to translate them, not knowing which ones are required and which ones they > won't see on staging/production. Many of them don't look at string IDs to > know where they show up, unless they have questions with a particular > string, and they look for context. > > If we have not thought about separating strings for US only or a couple of > locales only, we should start thinking of a solution soon. > > > > On Wed, Aug 7, 2019 at 1:52 AM Shane Tomlinson <[email protected]> > wrote: > >> Unfortunately the changes within the "server.po" resource are all email >> title strings and are sent to all users. These need >> to be translated as broadly as possible to avoid people being sent emails >> with English titles. I'm not sure the l10n impact >> was considered when making these changes. >> >> Within the "client.po" resource, the following strings are available to >> everyone: >> >> - Logins and Passwords >> - Open Tabs >> - Credit Cards >> - By proceeding, you agree to the <a id=\"fxa-tos\" href=\" >> /legal/terms\" tabindex=\"-1\">Terms of Service</a> and <a id=\"fxa-pp >> \" href=\"/legal/privacy\" tabindex=\"-1\">Privacy Notice</a>. >> - You've connected your Firefox account to Mozilla products that keep >> you secure and productive on the web: >> - Please acknowledge that by deleting your account: >> - Any subscriptions you have will be cancelled >> - You may lose saved information and features within Mozilla products >> - Reactivating with this email may not restore your saved information >> >> >> Shane >> >> >> On Tue, Aug 6, 2019 at 7:36 PM pmo <[email protected]> wrote: >> >>> I was going to ask, is there a deadline for completing these strings? >>> Any high priority markets as must haves, and others are nice to have? We >>> are going to prepare an l10n monthly report, we will mention this and any >>> upcoming new content coming their way. >>> >>> >>> On 8/6/19 11:30 AM, Julie McCracken wrote: >>> >>> We're translating strings related to the SubPlat at this time, even >>> though we're targeting a US only market? >>> >>> On Mon, Aug 5, 2019 at 10:26 PM Shane Tomlinson <[email protected]> >>> wrote: >>> >>>> > 75% of the strings were for either Subscription Platform or for title >>>> casing the emails [1]. Ryan Feeley requested >>>> the title casing, Ryan is that in support of a particular project? >>>> >>>> Shane >>>> >>>> [1] - https://github.com/mozilla/fxa/issues/1684 >>>> >>>> On Tue, Aug 6, 2019 at 1:45 AM Julie McCracken <[email protected]> >>>> wrote: >>>> >>>>> Hi, Shane - which Skyline deliverable were you referring to in your >>>>> above message? >>>>> >>>>> On Mon, Aug 5, 2019 at 8:45 AM pmo <[email protected]> wrote: >>>>> >>>>>> Hi Shane, >>>>>> >>>>>> Always appreciate your update on these type of pushes. Is this >>>>>> Skyline >>>>>> related? Is this for FxA Toolbar menu? In the one pager, it said >>>>>> "L10n >>>>>> is done by 7/29": >>>>>> >>>>>> https://docs.google.com/document/d/1s1gBAfdcArMxDb27HCdgU1-JYEZF1IIXCOK_MvblyT0/edit. >>>>>> >>>>>> >>>>>> >>>>>> We are trying to figure out which delivery is for what feature so we >>>>>> can >>>>>> document all the requests. >>>>>> >>>>>> Thank you, >>>>>> >>>>>> Peiying >>>>>> >>>>>> >>>>>> >>>>>> On 8/5/19 5:22 AM, Shane Tomlinson wrote: >>>>>> > Hi Peiying, >>>>>> > >>>>>> > Ordinarily we extract FxA's strings on a bi-weekly basis and the >>>>>> l10n >>>>>> > crew manages to turn around translations pretty quickly. I didn't >>>>>> > realize this train was going to be *so* string heavy and wanted to >>>>>> let >>>>>> > you know before you hear it from the localizers. There are 68 new >>>>>> > strings comprised of 329 words. >>>>>> > >>>>>> > Next, the strings weren't extracted automatically on Friday because >>>>>> of >>>>>> > an error parsing the source code. I noticed the lack of new strings >>>>>> > today and was able to fix the parsing problem, but the strings are >>>>>> > extracted later than the normal Friday deadline. >>>>>> > >>>>>> > I'm sorry for both the count and the late extraction. >>>>>> > >>>>>> > Shane >>>>>> _______________________________________________ >>>>>> Dev-fxacct mailing list >>>>>> [email protected] >>>>>> https://mail.mozilla.org/listinfo/dev-fxacct >>>>>> >>>>>
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
