El dimecres, 8 d=E2=80=99abril de 2020, a les 1:55:18 CEST, Simon Depiets v=
a escriure:
> The languageToString function only takes one parameter, the Language enum.
> There is no function that returns a language name from a Language + Count=
ry
> combo.

Ah, then maybe you want to use KLanguageName::nameForCode

Cheers,
  Albert

>=20
> Le mer. 8 avr. 2020 =C3=A0 05:51, Albert Astals Cid <aacid@kde.org> a =C3=
=A9crit :
>=20
> > El dimarts, 7 d=E2=80=99abril de 2020, a les 16:12:28 CEST, Simon Depie=
ts va
> > escriure:
> > > Hello,
> > > The language is Automated by default and the values are based on a
> > QLocale
> > > enum which doesn't offer Brazilian Portuguese, nor British English for
> > > instance (although they offer Phoenician).
> > > https://doc.qt.io/qt-5/qlocale.html#Language-enum
> >
> > Yes it does, Portuguese for Language and Brazil for Country.
> >
> > Cheers,
> >   Albert
> >
> > >
> > > In recent versions of Lokalize you can override the Language-Team by
> > > project or for the whole application.
> > > Asking translators to update this value when onboarding them should be
> > > enough?
> > > Otherwise I can hard code the default value in Lokalize (mailing lists
> > are
> > > already hardcoded)
> > >
> > > Simon
> > >
> > > Le mar. 7 avr. 2020 =C3=A0 21:56, Luiz Fernando Ranghetti <
> > elchevive68@gmail.com>
> > > a =C3=A9crit :
> > >
> > > > Em seg., 6 de abr. de 2020 =C3=A0s 17:59, Albert Astals Cid <aacid@=
kde.org>
> > > > escreveu:
> > > > >
> > > > > El dilluns, 6 d=E2=80=99abril de 2020, a les 20:06:20 CEST, Luiz =
=46ernando
> > > > Ranghetti va escriure:
> > > > > > Hi guys,
> > > > > >
> > > > > > One of our (pt_BR) translators pointed to a wrong name of langu=
age
> > on
> > > > > > Language-Team field in .po headers made by Lokalize.
> > > > > >
> > > > > > It sets to:
> > > > > >
> > > > > > "Language-Team: Portuguese <kde-i18n-pt_BR@kde.org>\n"
> > > > > >
> > > > > > while it should be:
> > > > > >
> > > > > > "Language-Team: Brazilian Portuguese <kde-i18n-pt_BR@kde.org>\n"
> > > > > >
> > > > > > I know we can override it in Lokalize but I prefer a proper
> > solution
> > > > > > (if there is any).
> > > > >
> > > > > I really don't understand the problem you're having.
> > > > >
> > > > > Are you saying that Lokalize is "defaulting" to Portuguese instea=
d of
> > > > "Brazilian Portuguese"?
> > > >
> > > > Yes, thats the "problem"
> > > >
> > > > > Do you have your target language set as "Brazilian Portuguese" in=
 the
> > > > settings?
> > > >
> > > > No, only one translator of our team has (the one which raises this
> > > > issue to me), the other 3 ou 4 that occasionally translate also use
> > > > the default.
> > > >
> > > > What I'm asking is how can I or someone change the default to
> > > > "Brazilian Portuguese", where does it come from so we can change it
> > > > for all translators including the new ones on future.
> > > >
> > > > Regards,
> > > >
> > > > Luiz
> > > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
>=20
>=20