Re: [l10n-web] Reminder: Brand names remain unchanged

Noting that there are conversations happening around both "Firefox
Account" and "Sync", and the policy might change, at the moment
they're both considered localizable.

"Firefox Account": account is localizable, Firefox needs to remain unchanged.

"Sync" is localizable. Note that the confusion between "Sync as a
verb" and "Sync as a feature" should not be possible in Fluent
strings, since the latter is always represented by a term. For that
reason, please DO NOT replace the term with a localized term.

feature: Sign in to { -sync-brand-short-name }
verb: Sync bookmarks now…

All FTL files have clear localization comments
https://hg.mozilla.org/l10n/gecko-strings/file/default/browser/branding/official/brand.ftl
https://hg.mozilla.org/l10n/gecko-strings/file/default/browser/browser/branding/sync-brand.ftl
https://hg.mozilla.org/l10n/gecko-strings/file/default/browser/browser/branding/brandings.ftl

Francesco

Il giorno ven 23 ago 2019 alle ore 08:10 Artem Polivanchuk
<[email protected]> ha scritto:
>
> Hello Everyone,
>
> Since Pontoon currently doesn't support glossary, which could be one of the solutions for keeping brand names consistent across projects, the locale managers should take care of it.
> At the moment I would suggest having a link to the mentioned list of brand names in the Pontoon's Team Info tab like this:
> https://pontoon.mozilla.org/uk/firefox/team-info/
>
> By the way, Firefox Sync is not presented in the list. In my locale, this term is always translated, otherwise, it might be not clear for all users.
> The same is for Firefox Account.
>
> Best regards,
> Artem
>
> пт, 23 серп. 2019 о 00:33 Jeff Beatty <[email protected]<mailto:[email protected]>> пише:
> On Thu, Aug 22, 2019 at 3:17 PM Michael Bauer <[email protected]<mailto:[email protected]>> wrote:
>
> > You don't have to be fluent in 150 language to know that there are
> > languages that stick bits on other words. Even if you had no knowledge
> > of how languages work, the obvious thing would be to *ask* the
> > translators at your disposal if approach X works and if not, why not.
> > Between Finnish, Estonian, Hungarian, Basque, Czech and Russian being
> > long established locales, surely someone would have pointed out the
> > obvious.
> >
> > Reading between the lines of my last message, this is the point I'm
> making: who am I to tell you how to adhere to the policy when I don't know
> your language? I trust everyone here can make recommendations for how
> they'd like to proceed to handle these cases and work with us to make sure
> those recommendations adhere to the policy and produce a reasonable
> localization.
>
> > So you implemented a policy without considering what a language like
> > Basque for example where <of> or <'s> is expressed by sticking <en> or
> > <aren> on the end of the noun is supposed to do when it has to say
> > something like "Mozilla's browser"?
> >
> > Wow. Just wow.
> >
> >
> Let's not assume that the l10n team blindly made recommendations to the
> Brand team of how to craft the policy. I wouldn't categorize our
> involvement as wholly blind, ignorant, or hasty.  A certain level of
> assumed expertise, competence, and professionalism would be helpful here.
>
> > Does the brand team realize this is more restrictive that even
> > Microsoft's policy? Microsoft localization allows suffixes as long as
> > you don't change the letters of the product name itself, such as
> >
> > Hae kuvia Microsoftin ClipArt-kokoelmasta. (Finnish)
> > Microsoft Storen laitesovellus (Finnish)
> > Wordi automatiseerimisteenused (Estonian)
> > Skypové jméno (Czech)
> >
> > We spent a full year advising Branding on how to treat the brand in other
> languages. We pulled in examples like these to justify our position and
> represent the past requests from localizers like you to have more
> flexibility, with many localizers alongside us in meetings with the Brand
> team. Ultimately, it's not the l10n team's call to make, but to make
> informed recommendations to Brand and inform Brand of the trade-offs
> associated with a more strict policy versus a more flexible one. We've done
> what we can by leveraging examples from Microsoft, Google, and others.
>
> > and in some cases, even the root may be modified:
> > Na Skypu (Czech)
> > Do Chortana (Gaelic)
> >
> > M
> >
> > Sgrìobh Jeff Beatty na leanas 22/08/2019 aig 21:57:
> > > Not being an expert in the intricacies of all languages (who is?), I
> > can't
> > > speak to what options everyone has at their disposal. I know that the
> > Brand
> > > team is firm on this policy and despite our multiple attempts to convince
> > > them otherwise, there's no wiggle room, unfortunately.
> >
> > _______________________________________________
> > dev-l10n mailing list
> > [email protected]<mailto:[email protected]>
> > https://lists.mozilla.org/listinfo/dev-l10n
> >
> _______________________________________________
> dev-l10n mailing list
> [email protected]<mailto:[email protected]>
> https://lists.mozilla.org/listinfo/dev-l10n
> _______________________________________________
> dev-l10n mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-l10n
_______________________________________________
dev-l10n mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-l10n