♿(frontend) inject language attribute to pdf export

[Ovgodd]

Purpose

This PR improves the accessibility of exported PDF documents by explicitly setting the document language to fr-FR as suggested in the issue 1133

This ensures proper pronunciation by screen readers (e.g. VoiceOver, NVDA), especially for homographs like “mobile” that differ between French and English.

Proposal

• Inject language="fr-FR" into the element returned by toReactPDFDocument() using cloneElement()
• Add inline comment explaining the purpose (screen reader compatibility)

External contributions

Thank you for your contribution! 🎉

Please ensure the following items are checked before submitting your pull request:

• I have read and followed the contributing guidelines
• I have read and agreed to the Code of Conduct
• I have signed off my commits with git commit --signoff (DCO compliance)
• I have signed my commits with my SSH or GPG key (git commit -S)
• My commit messages follow the required format: <gitmoji>(type) title description
• I have added a changelog entry under ## [Unreleased] section (if noticeable change)
• I have added corresponding tests for new features or bug fixes (if applicable)

[AntoLC]

It is a bit hard to know if this dev is working, can you add a test e2e about it ?

Tests about export are located here: https://github.com/suitenumerique/docs/blob/main/src/frontend/apps/e2e/__tests__/app-impress/doc-export.spec.ts

If you do that you can see somewhere the informations:

const pdfBuffer = await cs.toBuffer(await download.createReadStream()); const pdfString = pdfBuffer.toString('latin1'); console.log("pdfString", pdfString);

---

I am wondering if we should not do the same about docx export, WDYT ?

[Ovgodd]

It is a bit hard to know if this dev is working, can you add a test e2e about it ?

Tests about export are located here: https://github.com/suitenumerique/docs/blob/main/src/frontend/apps/e2e/__tests__/app-impress/doc-export.spec.ts

If you do that you can see somewhere the informations:

const pdfBuffer = await cs.toBuffer(await download.createReadStream()); const pdfString = pdfBuffer.toString('latin1'); console.log("pdfString", pdfString);

I am wondering if we should not do the same about docx export, WDYT ?

I agree yes, I am on it for the e2e, and for the doc export I think it is a good idea yes to make sure it also works properly and isn’t missing anything !

[Ovgodd]

@AntoLC the e2e test for language injection has been added. Would you like me to create the other test for the DOCX export in this PR as well ?

[AntoLC]

@AntoLC the e2e test for language injection has been added. Would you like me to create the other test for the DOCX export in this PR as well ?

If this PR is ready, let's do it in another PR for DOCX.

[Ovgodd]

@AntoLC the e2e test for language injection has been added. Would you like me to create the other test for the DOCX export in this PR as well ?

If this PR is ready, let's do it in another PR for DOCX.

Yes this PR is ready, Ok I will do an another one, the goal is to test Injection language in DOCX export right ?

[Erwan-le-Gall]

Thank you Cyril! @Ovgodd
to check if language is set you can use Acrobat Reader menu File / Properties / Advanced tab