LaTeX Build Failure

[StanFromIreland]

/home/runner/work/python-docs-pl/python-docs-pl/Doc/library/asyncio.rst:34: WARNING: inconsistent term references in translated message. original: [':ref:`run Python coroutines <coroutine>`'], translated: [] [i18n.inconsistent_references]
/home/runner/work/python-docs-pl/python-docs-pl/Doc/library/email.rst:15: WARNING: inconsistent term references in translated message. original: [':mod:`email`', ':mod:`smtplib`', ':mod:`nntplib`', ':mod:`email`'], translated: [':mod:`email`', ':mod:`smtplib`', ':mod:`nntplib`'] [i18n.inconsistent_references]

I don't see how the issue has been generated, no strings have been translated or touched in aysncio or email.

The -fail-on-warning flag is quite annoying in this case.

[StanFromIreland]

This commit updated the titles of the files removing a link. I presume this is the source of the issue though it is 8 months old.

[StanFromIreland]

@rffontenelle I presume this is similar to the current fails in pt-Br actions?

[rffontenelle]

Not the same scenario. The linked action fail was caused by a translation error -- an unprintable character nearby a role.

Your situation is interesting: if I read correctly, the string is not translated and yet it fails because the expected role is missing in the translation.

Does this happen only in latex build or in html (default) as well?

Can you reproduce this fail building locally?

Also, consider adding fail-fast: false to run other versions and find errors in other as well.

[StanFromIreland]

Ah I see.

You read correctly.

I opened a PR to add fail-fast: false but I can't merge it to find out :(

Locally I cannot test LaTeX (We just don't get along) but HTML seems to be fine.

[StanFromIreland]

I compared to pt-Br's version and for email.rst we have a string that is different:

pt-br: msgid ":mod:`!email` --- An email and MIME handling package"
pl:    msgid ":mod:`email` --- An email and MIME handling package"

It seems our .po files have to be regenerated which did not happen automatically here?

Also I like the comments for each line referring to their location in the .rst. What do you think @m-aciek about add them to pl on future updates?

[rffontenelle]

The PO file doesn't have to be regenerated because is done already when updating Transifex strings on every Friday. Pulling translations from Transifex should bring the PO file updated.

Actually, the make gettext part wouldn't be necessary if we didn't need to always keep the .tx/config up to date.

[rffontenelle]

I think the library/email.po is out-of-date because there was no translation to it. See how the Project-Id-Version says 3.11.

[m-aciek]

This issue causes fails for both html and latex builds, I saw it in some previous action run.

The location comments generate very large diffs, that are hard to navigate with, at least from my experience. I think they are of value in source strings, but they change too often to include them in translations. I was inspired by Django translation workflow to exclude them.

[StanFromIreland]

Good point, I agree now with not including them.

Any ideas as to the source of the issue?

[m-aciek]

I've added new translation strings to both failing modules in 3.12. Let's see if it helps.

[rffontenelle]

Can you please approve the workflow run in #62 ? I enabled pull_request event trigger and updated the PO files to see if anything changes.

[StanFromIreland]

So it is just 3.12 that is affected.

[StanFromIreland]

Found it!

Kamil Broniowski translated them yesterday. I was checking 3.13 and not 3.12

[StanFromIreland]

Fixed them! Other was a missing backtick. Do you have contact with Kamil? Maybe you could recommend the main branch for translating? (Also watch out for spaces and backticks)