Lang pt-BR must set polyglossia-lang.name to brazil instead of brazilian

[edusantana]

As I understand from #2174 we should set the lang attribute, and it would map to values appropriated for babel and polyglossia.

When I use pt-BR it sets polyglossia-lang.name to brazilian (this is acceptable according to polyglossia documentation), but I get this error:

Package polyglossia Warning: File gloss-brazilian.ldf does not exist!
(polyglossia)                I will nevertheless try to use hyphenation pattern
s for brazilian. on input line 34.

This file doesn't exist, but gloss-brazil.ldf does! So I manually change the polyglossia-lang.name to brazil, and it works:

polyglossia-lang: 
    name: brazil

So, when use set lang: pt-BR it must set polyglossia-lang.name to brazil instead of brazilian.

[edusantana]

You can see that with pt-BR it doesn't translate the "chapter" word:

But when setting to polyglossia-lang.name to brazil:

[mb21]

From the documentation, both brazil and brazilian should work for polyglossia and babel... so if brazil works on more systems, we could make the change on this line...

[edusantana]

Thanks! It was on Ubuntu 16.04 64-bit.

[jgm]

See https://groups.google.com/d/msgid/pandoc-discuss/69070e2d-a24c-4dce-bd05-e315ec109602n%40googlegroups.com. Is it possible that support for brazil has now been dropped, and that we must use brazilian?

[p3palazzo]

Copying the background reference over here for easier access: when using MacTeX 2020, these are the cases:

• pdflatex accepts both brazil and brazilian;
• xelatex only accepts brazilian.

[jgm]

I am confident about recent versions. The question is whether versions that only accept brazil are still in wide enough circulation to worry about.

[jgm]

@edusantana Since you submitted the original issue, maybe you could let us know if brazil is still needed on your system, or if brazilian now works?

[jgm]

I've pushed a change; now it gives you

\ifxetex
  % Load polyglossia as late as possible: uses bidi with RTL langages (e.g. Hebrew, Arabic)
  \usepackage{polyglossia}
  \setmainlanguage[variant=brazilian]{portuguese}
\else
  \usepackage[shorthands=off,main=brazilian]{babel}
\fi

Is that what it should be? You can test with the nightly that will be built tonight.

[p3palazzo]

My BasicTeX 2020 implementation of xelatex isn't happy with the [variant=brazilian] clause. I get this error:

! Undefined control sequence.
\adddialect ...####1####2####3####4{}\fi }\bbl@cs
                                                  {languages}\endgroup
l.67 ...ainlanguage[variant=brazilian]{portuguese}

Not sure if there's something wrong with my installation. I compiled from source using today's master branch.

[jgm]

Just pushed a release with the change before seeing this.

I'm not sure what is going on with this, but it would be nice to get feedback from others.
This worked okay for me, and it's in the polyglossia documentation.

[mb21]

Does polyglossia have a mailing list? someone wants to ask there?
Or maybe @adunning knows? :)

[p3palazzo]

Just pushed a release with the change before seeing this.

I'm not sure what is going on with this, but it would be nice to get feedback from others.
This worked okay for me, and it's in the polyglossia documentation.

Then I guess it must be some problem with my TeX installation. I’ll assume your code is correct and will look into what’s wrong on my side. I generated a *.tex file using yesterday’s master branch and, upon inspecting it, I thought it should work indeed.

[tarleb]

I can confirm that the current solution works with TeXLive 2021, but not with TL 2019 (Ubuntu 20.04).

[jgm]

I think this can be closed now that we use babel instead of polyglossia.