Iago,

If you click the "Edit this page" link at the upper-right, it will take you to the correct repository for the page. In this case, it's the council-docs. I just pushed a commit to revert the change that appears to have caused it, which will be picked up in the next docs build.

OOF, you're right. It's not present in the English version but it is in the Spanish one. Thanks for pointing it out, Iago!

On Thu, 26 Aug 2021 at 13:27, Iago Rubio iago@iagorubio.com wrote:

I am not even sure it's docs responsability but I guess at least I may get help to report it to the correct team - websites, etc ... - so please bear with me.

I have found looking for a text covering "What is Fedora" on Google, the "About Fedora" link on https://getfedora.org - in my case it showed me the spanish link - points to the wiki page https://fedoraproject.org/wiki/Overview that redirects permanently to https://docs.fedoraproject.org/en-US/project/

At that page, some HTML gets escaped so the raw HTML is visible on the browser.

I tried to surf throught Pagure to see if I was able to find the correct repo, but was not successful.

I hope you can help me to report/fix this issue.

I'm happy to put time on it and submit a PR if it's on our repos, or to file a bug if it's not.

Regards.

• Iago -

---

docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

Docs are built every hours, but the translated version is only built once a day (near 23h utc), that's probably why you are not seeing the changes yet. I'm not sure why this is not affecting stg though... We might have some inconsistency between the two branches on the docs-fp-o repo or somewhere else.

On 2021-08-26 20:40, Ben Cotton wrote:

So it looks like this affects all (or at least most) non-English languages. Interestingly, I can't replicate this in the staging environment. It doesn't seem like an issue with the docs tooling, so I'll pass this along to the Localization team and see if they have any ideas.