Please enable European Portuguese (pt-PT) for missing Weblate components

Translations
1

Hi!

I’ve been actively working on reviewing and completing the European Portuguese (pt-PT) translations for AntennaPod.

I noticed that the pt-PT language is currently not initialized/missing from several components on Weblate (Documentation, General, App, Screenshot titles, Contribute).

Could an admin please add/enable the Portuguese (Portugal) (pt_PT) language for all the remaining components? This will allow me to continue translating and fully localize the project.

Thank you!

2

Hi!

Thanks for contributing. I’ve added some of the missing components for pt-PT. You’ll see that I didn’t add the biggest component, the app component. Could you help me with something before I add it?

The thing is: the app component has already been translated for pt, and I’m not sure if the person who did that translated it did so thinking in portuguese portuguese or brazilian portuguese (the app is translated to brazilian portuguese in the `pt-BR` language). Could you please take a quick look to see if there are any clues as to which variant was used on that language?

If the app is already translated to portuguese from portugal, we can try to move it over to `pt-PT`, as that is the biggest component for the project. Otherwise, I’ll just add the app component for you.

Thanks!

edit: I see that you translated and approved the translations for the website. Would you like for me to create a preview deployment so you can check the translations in context. That way, after you take a quick look, I can update the real website with those translations.

3

Hi @delthia,

I translated and approved everything in pt-PT, and now I’m going to translate the new components you added.

As for pt, I would remove it, because it doesn’t really make sense to keep it as a separate variant. Other countries that speak Portuguese generally use a form much closer to European Portuguese, while Brazil is the one with the major differences. So if pt continues to exist, it should be the same as pt-PT.

Regarding the preview deployment, there’s no need, because I was constantly checking the context directly on the website anyway.

Thanks for your help!

4

Exactly, but before deleting it, I’d like for someone to check it. The whole app is translated in pt, and if by taking a look, you determine that it is the European variant, we can try to move it to pt-PT and you’d only need to review it, instead of doing everything from scratch.

Otherwise I can just add the missing component to pt-PT

5

I checked the current app translation in pt, and it seems to be a mix of variants — mostly European Portuguese, but with some Brazilian Portuguese mixed in as well.

Because of that, I don’t think it would be a good idea to move pt directly to pt-PT as it is, since that would bring inconsistencies in terminology and spelling into the European Portuguese locale.

The cleanest option would be to remove the generic pt locale, or replace it with the current pt-PT, which is already correct, complete, and approved.

Thanks

6

Great, thanks for checking it out.

I’ve added the last component for you, so you can work on that.

Please let me know when the store screenshots are translated so I can generate them. That way, after the app is translated to Portuguese, the store screenshots will also match!

Thanks

1 Like
7

Hi @delthia,

I just want to correct my previous message. I had checked the wrong file by mistake.

The generic pt locale was the one being used for the app component, while the other components were already in pt-PT. Since then, I’ve fully translated and reviewed the app in pt-PT as well, and I also went through everything to make sure the terminology and wording are consistent across all components.

So at this point, I don’t think there’s any reason to keep the generic pt locale anymore. The pt-PT translation is now complete, fully reviewed, and ready to be the version kept going forward.

Because of that, I believe the best option now is to remove pt, rather than trying to reuse or migrate it.

Thanks again for your help and for enabling the missing components. I really appreciate it.

8

@smarquespt @BlackSpirits Does removing the PT translation (in favor of the PT-PT translation) sound reasonable to you? Removing one of them avoids duplicate work and inconsistency, so we have to remove one of them. The question is basically just which one, the new (duplicate) PT-PT or the original PT. Both are almost exactly the same now, and it seems to me that removing PT makes it a bit more clear which country variant we have.

2 Likes
9

Hi @ByteHamster and @delthia,

Yes, I agree — the generic pt locale should be removed, and only pt-PT and pt-BR should remain.

At this point, I have already translated and reviewed all the pt-PT files, and the European Portuguese translation is complete and ready to be kept as the proper locale going forward.

So from my side, you can safely:

  • remove pt

  • keep pt-PT and pt-BR

  • add/update the pt-PT translation on the website as well

Everything on the pt-PT side has already been translated and reviewed, so it should be ready to publish.

Thanks again!

10

That would be just fine for me. Altough, I do not have access to pt-PT translations, my permissions were revoked, I assume.

Thanks

ByteHamster <noreply@forum.antennapod.org> escreveu (quinta, 23/04/2026 à(s) 06:40):

11

Okay, PT translation deleted.

Hmm, I don’t think we have any permission requirements to start contributing. Maybe that’s because all are reviewed (which is not necessary at all, by the way)

12

If that’s the case, then I only have translator status and not review status, which I already had when in transifex.

Sérgio Marques

A sexta, 24/04/2026, 08:20, ByteHamster <noreply@forum.antennapod.org> escreveu: