Translate content to French

[SilentJMA]

These are the core templates - without which we cannot release any translated chapters. They are in the language specific templates directory:

• base.html - @borisschapira
• base_chapter.html- @borisschapira
• error.html- @borisschapira

2024

• base.html -
• base.html - foreword
• contributors.html -
• index.html -
• table_of_contents.html -

2022

• base.html -
• contributors.html -
• index.html -
• table_of_contents.html -

2021

• base.html -
• base.html - foreword
• contributors.html -
• index.html -
• table_of_contents.html -

2020

• base.html - @borisschapira
• contributors.html - @borisschapira
• index.html - @borisschapira
• table_of_contents.html - @borisschapira

2019

• base.html - @borisschapira
• contributors.html - @borisschapira
• index.html - @borisschapira
• table_of_contents.html - @borisschapira

These are the chapters to be translated. They exist in the content directory:

2024

• javascript -
• markup -
• structured-data -
• fonts -
• media -
• third-parties -
• seo -
• accessibility -
• performance -
• privacy -
• security -
• cms -
• ecommerce -
• jamstack -
• sustainability -
• page-weight -
• cdn -
• http -
• cookies -

2022

• css -
• javascript -
• markup -
• structured-data -
• fonts -
• media -
• webassembly -
• third-parties -
• interoperability -
• seo -
• accessibility -
• performance -
• privacy -
• security -
• mobile-web -
• capabilities -
• pwa -
• cms -
• jamstack -
• sustainability -
• page-weight -
• cdn -
• http -

2021

• css -
• javascript -
• markup -
• structured-data -
• media -
• webassembly -
• third-parties -
• seo -
• accessibility -
• performance -
• privacy -
• security -
• mobile-web -
• capabilities -
• pwa -
• cms -
• ecommerce -
• jamstack -
• page-weight -
• compression -
• caching -
• cdn -
• resource-hints -
• http -

2020

• css - @nico3333fr
• javascript -
• seo - @borisschapira
• markup -
• accessibility - @nico3333fr
• cms -
• performance - @borisschapira
• security - @nico3333fr
• jamstack -
• fonts - @stephanebachelier
• mobile-web -
• pwa -
• http2 -
• capabilities -
• third-parties -
• page-weight -
• caching -
• resource-hints -
• privacy -
• compression -
• ecommerce -
• media -

2019

• javascript - @borisschapira
• css - @nico3333fr
• seo - @AymenLoukil
• performance -
• http2 -
• markup - @SilentJMA & @borisschapira
• third-parties - Partie Tiers @borisschapira
• fonts - @arigaud-ca
• accessibility - @nico3333fr
• pwa -
• cms - @JustinyAhin
• security - @nico3333fr
• media - @borisschapira
• mobile-web - @borisschapira
• cdn -
• ecommerce -
• page-weight -
• caching - @allemas
• compression - @allemas
• resource-hints - @borisschapira

Additionally the following pages need translated too in the language specific templates directory:

• 2021/methodology.html -
• 2019/methodology.html @borisschapira
• 2020/methodology.html - @tunetheweb - Add 2020 Methodology in French #1420
• accessibility_statement.html @nico3333fr
• accessibility_statement.html additional update -
• base_ebook.html -

There is no need to translate the chapters HTML pages are they are generated off the markdown combined with the above templates.

Please include "Makes progress on #539" in all pull requests so a link is created from the PR to this issue.

---

Common notes for writing consistency are here: https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Translators'-Guide. Feel free to edit that and/or add French-specific extras by editing this comment.

French specific extra advice:

• Web Almanac => keep it that way, even if it's in English. "The Web Almanac" => "Le Web Almanac". For other projects names, like HTTP Archive, do the same: don't translate.
• Gender-inclusive language whenever possibl. Limit the use of abbreviation, because it's not very accessible, but multiply nouns "les développeurs et développeuses". Be especially vigilant when "we" is used to talk about the people who make the Web Almanac, don't invisibleize women.
• "Products", when talking about a development tools => in French, "Solutions" (not "Produits", which is most often reserved in French for off-the-shelf products or licensed software).
• Links to French version of resources if available (I'm thinking about MDN or Wikipedia, for example)
• Microtypography (spaces, punctuation, apostrophes): if possible, apply basic rules (guillemets, spaces before ":" or "%") but not if it slows you down. We can always make a pass at the end to set everything up all at once (I know the regexes to apply).
• Web is spelled web in lowercase, and similarly internet is lower case as per our style guide.
• Third parties should be "tierce(s) partie(s)".

[tunetheweb]

Great stuff @SilentJMA - I've updated your first comment showing what needs to be done. Feel free to stick your name against an item, clone the repo, and submit pull requests (PRs) with your translations.

Note a lot of the visualisation graphics are due to change in #511 so might want to hold off for that for some of the chapters, but the JavaScript, Accessibility and HTTP/2 chapters are good to go now. (edit: since merged)

As I mentioned @AymenLoukil also wanted to help out with the French so if the two of you could review each others chapters that would be great. Unfortunately my French is pretty poor, but happy to give PRs a once over for other technical issues.

[tunetheweb]

I've tagged you against the Accessibility chapter @SilentJMA as an example. Feel free to edit the issue to remove yourself and/or tag against another chapter if one takes your fancy more initially.

[SilentJMA]

@tunetheweb i will use Gitlocalize

[tunetheweb]

@tunetheweb i will use Gitlocalize

As per #38 (in case you didn't see this, or for others coming here late) they've just been submitting manual PRs for this instead of using Gitlocalize. Sorry not familiar enough with it gitlocalise to advise any better so probably best you do that too then.

[SilentJMA]

@tunetheweb i will use Gitlocalize

As per #38 (in case you didn't see this, or for others coming here late) they've just been submitting manual PRs for this instead of using Gitlocalize. Sorry not familiar enough with it gitlocalise to advise any better so probably best you do that too then.

i'm working on markup maybe i could finish it tonight so i can added it

[tunetheweb]

Could you also check you have the latest markdown down for the markup chapter (man that's confusing to type). We just pushed a big fix to all the chapter visuals as per #542.

Changes are here: 8470bed#diff-2f5abb57ff92adb7644369369d209f1e

[SilentJMA]

Could you also check you have the latest markdown down for the markup chapter (man that's confusing to type). We just pushed a big fix to all the chapter visuals as per #542.

Changes are here: 8470bed#diff-2f5abb57ff92adb7644369369d209f1e

when i will finish the markup file i will go back and edited the change

[SilentJMA]

Could you also check you have the latest markdown down for the markup chapter (man that's confusing to type). We just pushed a big fix to all the chapter visuals as per #542.
Changes are here: 8470bed#diff-2f5abb57ff92adb7644369369d209f1e

when i will finish the markup file i will go back and edited the change

is it okay to add the file not finished to edit the change ?