Almanac.httparchive.org: 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:

• [x] base.html + authors bio - @borisschapira
• [x] base_chapter.html - @borisschapira
• [x] contributors.html - @borisschapira
• [x] contributors.html 2020 - @borisschapira
• [x] error.html - @borisschapira
• [x] index.html - @borisschapira
• [x] index.html 2020 - @borisschapira
• [x] table_of_contents.html @borisschapira

These are the chapters to be translated, in rough order of popularity. They exist in the content directory:

2020

• [ ] capabilities

2019

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

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

• [x] methodology.html 2019 @borisschapira
• [x] methodology.html 2020 - @bazzadp - #1420
• [x] accessibility_statement.html @nico3333fr
• [ ] base_ebook.htm -

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)".

[bazzadp]

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 https://github.com/HTTPArchive/almanac.httparchive.org/pull/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.

[bazzadp]

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]

@bazzadp i will use Gitlocalize

[bazzadp]

@bazzadp 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]

@bazzadp 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

[bazzadp]

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: https://github.com/HTTPArchive/almanac.httparchive.org/commit/8470bed51a02201781176954f56b6103ac392f6c#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 ?

[bazzadp]

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

Sorry not sure what you mean? You want to submit the file partially translated? Or with the old chapter visuals? If so, then yes it's possible, but personally I would do all or nothing if possible. One less thing to track!

You can do several commits, and push to your local branch, if you're worried about losing local commits.

But let me know what you're thinking and can maybe advise better.

[SilentJMA]

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

Sorry not sure what you mean? You want to submit the file partially translated? Or with the old chapter visuals? If so, then yes it's possible, but personally I would do all or nothing if possible. One less thing to track!

You can do several commits, and push to your local branch, if you're worried about losing local commits.

But let me know what you're thinking and can maybe advise better.

because i translated the file its still just the party that got changes but its okay i will go back to you in a few minutes

[SilentJMA]

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

Sorry not sure what you mean? You want to submit the file partially translated? Or with the old chapter visuals? If so, then yes it's possible, but personally I would do all or nothing if possible. One less thing to track!

You can do several commits, and push to your local branch, if you're worried about losing local commits.

But let me know what you're thinking and can maybe advise better.

markup file finished

[bazzadp]

Cool open a pull request for that and then @AymenLoukil can review when he gets a chance.

[AymenLoukil]

Yes. Please ping me when PR is open.
I also added my name in front of some chapters.

[SilentJMA]

Yes. Please ping me when PR is open.
I also added my name in front of some chapters.

@AymenLoukil & @bazzadp You can check please its really hard to translate to FR

[borisschapira]

Hi y'all. If I can help translating, I'm available. Feel free to give me a chapter and I'll PR a french translation / or I can help readproof/validate existing translations.

[bazzadp]

Excellent!

At this rate the French translation might be the first to finish - even though it only started last. Is that a challenge!?!? 😜

550 is waiting on a review from someone with much more French than me.

Also the non-chapter template files haven’t been assigned out so can start on those if you fancy while waiting for the other two to give up some of their greedily grabbed chapters 😉 Those are good ones to get going anyway as they allow the site to be run up in development to actually see the content in a real browser!!

[bazzadp]

Also see if you can request to join the Translator team: https://github.com/orgs/HTTPArchive/teams/translators/members

[borisschapira]

@bazzadp I can't access this page, so I guess I can't request to join.

[bazzadp]

Ah man. Same with this one? https://github.com/orgs/HTTPArchive/teams/almanac-contributors/members

[borisschapira]

@bazzadp Yes. I don't even see the "Teams" tab, not being in a team.

[borisschapira]

@SilentJMA You can assign to me the pages of the language specific templates directory, I can help by translating what needs to be translated there.

[bazzadp]

@SilentJMA You can assign to me the pages of the language specific templates directory, I can help by translating what needs to be translated there.

Assigned the first 3 to you there. Some of them are very small and may not even have anything to translate in them, but they are the ones necessary to run the chapter pages in French (once we have at least one of them).

Feel free to comment to grab the rest of those templates once those are done.

Presume you can’t edit the first comment even though you’re assigned to it? Hopefully @rviscomi can get your access sorted soon.

[borisschapira]

@SilentJMA @bazzadp @AymenLoukil In addition, I think we need common rules for translation. Some proposals:

• 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, don't translate
• Gender-inclusive language whenever possible (limit the use of abbreviation, because it's not very accessible)
• "Products", when talking about a development tools => "Solutions" (not "Produits", which is most often reserved in French for off-the-shelf products or licensed software).
• Links to French version of resource if available (I'm thinking about MDN, for example)
• Microtypography (spaces, punctuation): 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).

Feel free to add things, so that we can translate in a consistent way

[borisschapira]

French translators, FYI: if you need/want to execute the project locally to visualize the changes you're contributing, here's what you need to change (then follow ./src/README.md python instructions).

[bazzadp]

Yup. Feel free to submit that first one (to add French as a Language) as part of your PR when doing the templates.

The second one (to turn on French) we’ll hold off until we have it all done. Though we have talked about making it easier to release chapter by chapter at some point.

[SilentJMA]

@borisschapira @AymenLoukil you can join me on a team on Gitlocalize so we can work on it

[bazzadp]

@borisschapira I assigned the rest of the non-chapter pages to yourself since you stormed through the first set.

[SilentJMA]

@borisschapira I assigned the rest of the non-chapter pages to yourself since you stormed through the first set.

I add you also @borisschapira there in GitLocalize chose whatever you want and work

[borisschapira]

I add you also @borisschapira there in GitLocalize chose whatever you want and work

Perfect! I'll focus on the remaining templates pages tonight, and then I'll contribute.

[borisschapira]

Ok I have PR'ed all the templates that have been affected to me. Feel free to "give" me some chapters and I'll translate them as well. @SilentJMA @AymenLoukil: do you want to unburden yourself of a few chapters?

[nico3333fr]

I may help to proofread in french, just tell me which part I have to correct :)

[AymenLoukil]

I add you also @borisschapira there in GitLocalize chose whatever you want and work

Perfect! I'll focus on the remaining templates pages tonight, and then I'll contribute.

Ok I have PR'ed all the templates that have been affected to me. Feel free to "give" me some chapters and I'll translate them as well. @SilentJMA @AymenLoukil: do you want to unburden yourself of a few chapters?

I unassigned myself to some chapters.

[allemas]

Hi! Hi!
I can help you to translate too! let me know if I can help you and which part to translate :)

[borisschapira]

@allemas @nico3333fr Welcome!

@nico3333fr: there are 2 PR waiting for a review, do you want to readproof? In each case, you'll need to compare the FR template to its EN source if you want to check that the translation is accurate.

@allemas look at the very first post of this thread, is there one of the chapters that interests you more than the others and that you would like to translate? If so, feel free to tell us. Next step: fork master on you own repo, copy the markdown file of the chapter you want to translate from the source folder into the equivalent fr folder and here you go.
If you need help, feel free to use GitLocalize on your repo:branch.

[SilentJMA]

I add you also @borisschapira there in GitLocalize chose whatever you want and work

Perfect! I'll focus on the remaining templates pages tonight, and then I'll contribute.

Ok I have PR'ed all the templates that have been affected to me. Feel free to "give" me some chapters and I'll translate them as well. @SilentJMA @AymenLoukil: do you want to unburden yourself of a few chapters?

I unassigned myself to some chapters.

yes i did and i'm working now on Gitlocalize

[bazzadp]

Yes, welcome @allemas and @nico3333fr ! Great to have your help!

yes i did and i'm working now on Gitlocalize

I'm still struggling with Gitlocalize.

Is it best for everyone to work from @SilentJMA 's GitLocalize for French? In which case can you give everyone edit access @SilentJMA ?

Or should you all work on your own forks? And potentially have your own GitLocalize there if you want?

Sorry but not familair with it to know...

[SilentJMA]

Yes, welcome @allemas and @nico3333fr ! Great to have your help!

yes i did and i'm working now on Gitlocalize

I'm still struggling with Gitlocalize.

Is it best for everyone to work from @SilentJMA 's GitLocalize for French? In which case can you give everyone edit access @SilentJMA ?

Or should you all work on your own forks? And potentially have your own GitLocalize there if you want?

Sorry but not familair with it to know...

We can work on my RP so we can keep track on each other

Yes, welcome @allemas and @nico3333fr ! Great to have your help!

yes i did and i'm working now on Gitlocalize

I'm still struggling with Gitlocalize.

Is it best for everyone to work from @SilentJMA 's GitLocalize for French? In which case can you give everyone edit access @SilentJMA ?

Or should you all work on your own forks? And potentially have your own GitLocalize there if you want?

Sorry but not familair with it to know...

We can work on my RP so we can keep track on each other

[allemas]

thanks to all of you!
I forked the repo and I'd start with caching. Is it ok @borisschapira ? :)

[SilentJMA]

thanks to all of you!
I forked the repo and I'd start with caching. Is it ok @borisschapira ? :)

i will add you to gitlocalize and work on it there

[SilentJMA]

thanks to all of you!
I forked the repo and I'd start with caching. Is it ok @borisschapira ? :)
i will add you to gitlocalize and work on it there so we can keep track of each other

create your account there by signing in to https://gitlocalize.com/ using you github credentials

[nico3333fr]

@nico3333fr: there are 2 PR waiting for a review, do you want to readproof? In each case, you'll need to compare the FR template to its EN source if you want to check that the translation is accurate.

Yes, will jump on it asap @borisschapira :)

[bazzadp]

Hey @allemas / @nico3333fr I've just sent you an invite to the project so we can assign tasks to you. Let me know once accepted (or if you didn't get the invite!)

[allemas]

Thanks, it's ok for me now :)

[SilentJMA]

Thanks, it's ok for me now :)

@allemas did you join gitlocalize so i can add you to the team ?

[borisschapira]

Note: I added "Common notes for writing consistency:" to the top post of this thread.

[borisschapira]

@SilentJMA I see that you've kept the "third-parties" chapter. Please note some I translated the introduction because it's featured on the index template. If you want to modify something (because it's more consistent with the way you write), please also modify the featured extract.

[allemas]

Thanks, it's ok for me now :)

@allemas did you join gitlocalize so i can add you to the team ?

Yes i did, what is the next step ?

[SilentJMA]

@SilentJMA I see that you've kept the "third-parties" chapter. Please note some I translated the introduction because it's featured on the index template. If you want to modify something (because it's more consistent with the way you write), please also modify the featured extract.

i will let you get it and i will get something else

[SilentJMA]

Thanks, it's ok for me now :)

@allemas did you join gitlocalize so i can add you to the team ?

Yes i did, what is the next step ?

done

[nico3333fr]

Hey @allemas / @nico3333fr I've just sent you an invite to the project so we can assign tasks to you. Let me know once accepted (or if you didn't get the invite!)

Done, accepted :)

[nico3333fr]

You may assign me the accessibility chapter @SilentJMA :)

[bazzadp]

You may assign me the accessibility chapter @SilentJMA :)

You should now have permission to edit the first comment to assign it yourself @nico3333fr

[nico3333fr]

@bazzadp right, done, thanks :)

[bazzadp]

How are we getting on guys?

I just checked our GitLocalize and see three chapters in review for a couple of weeks. Are any of them ready to be submitted as pull requests yet or still working through them?

[borisschapira]

I've been pretty busy for the last three weeks, but here I am again. I PR'ed a chapter and now I'll move on to the review of @SilentJMA's work.

[JustinyAhin]

Hi ✋.

I found about this year Web Almanac a few days ago, and saw today on a tweet of @borisschapira that it is possible to contribute with translation.

I'll start translating the CMS chapter. So, how does it works? Does it needs to be assigned to me?

Also, I'm a native French speaker, so I'll be happy to review PRs :)

[bazzadp]

Hi @JustinyAhin , welcome onboard!

I've assigned you the CMS chapter by editing the first comment. I've also sent you invites to the team so you'll be able to edit this comment in future.

The way it works is you grab one of the unassigned chapters like above, clone the repo, and then submit a PR with the translated chapter. The chapters are in markdown format in the content directory and you should copy the en version to the fr folder (the fr folder doesn't exist at the time of writing but should soon if #595 is approved). There are also some conventions to use in the translations in the first comment.

Ideally you should also do an npm install from the src directory, and then use npm run generate to generate the HTML from the translated markdown and include both the markdown chapter file and HTML chapter file in the PR, but we can help with this step if you're less familiar with npm.

Then we need one of the other French speakers to review and approve the PR. Myself, or one of the other core members, will also give it a review for technical correctness (but our French is not good enough to review the language) and once we have the two reviews, we'll merge it to master. Please keep the markdown as similar to English version in terms of line spacing and formatting as possible to assist with this technical review and any future changes we need to do.

So before you start on that CMS chapter, it would be good for you to review the translation that @borisschapira has done in #595, to get a feel for how to translate. It's primarily the markdown file that needs review, and not the HTML. Have a read and make any suggestions directly on the PR where @borisschapira can either accept your suggestion or not. If you have no suggestions and think the translation is good, then approve the PR and say that in the comment and then we can merge it.

@SilentJMA also is using GitLocalize and am sure he will add you to his repo there if you prefer to use that. Just sign up to GitLocalize with your GitHub username and drop him a note here. Or you can just submit manual PRs like @borisschapira did for #595.

And one more thing - add yourself to the 2019.json file in the Translators team once you've made your first contribution as you'll officially be part of the team and then will appear on the contributors page in the next release. Example PR for that.

Hopefully that all makes sense but if not then feel free to ask any questions. We're a friendly bunch here and appreciative of the time you all are giving to help with this project so don't be afraid to ask anything at all!

[nico3333fr]

I was also very busy, but next week, I'll probably be available :)

[bazzadp]

Not a problem all. Appreciate this can be a busy time of year and this is being done on a volunteer basis. Hope you all enjoy the holiday season and don't worry about getting to this when you should be taking time off - I was just checking we hadn't missed a PR that was ready to land!

[rviscomi]

Just wanted to pop in and say that I'm super impressed to see all of the support for getting the content translated to French. Thank you to everyone who's stepping up!

[bazzadp]

@nico3333fr I added you to the Contributors page in https://github.com/HTTPArchive/almanac.httparchive.org/commit/42c710325f4cf6568ad220b69dd4b0cc13d4bd3f. Hope that’s OK and feel free to submit a PR to correct or add any more details.

[nico3333fr]

@bazzadp yes, thanks a lot, sorry, with lock-down, I didn't have the time to answer earlier.

[bazzadp]

Hey all, I know there’s a lot going on in the world right now and some of you may not have the time to look at this right now, but we were making great progress on this previously, so thought no harm in reaching out with a friendly ping! Don’t worry if you can’t spare the time right now - totally understandable.

[borisschapira]

Hey @bazzadp, hope you're well. As you guessed, everything's crazy right now, but I didn't forget my involvement. As soon as I have some time alone, I'll come back to it.

[nico3333fr]

Hey :)
Same for me, lockdown was complicated (hard to do the teacher, the work, cook, etc.) at the same time, but I hope to send a PR for accessibility soon ^^

[AymenLoukil]

Hello,
Hope you are fine.

I'm working on a new chapter translation. I faced an issue on GitLocalize on a big section saying : Something's wrong! Please check the translation that you added and try again.
when i hit the submit button.. any idea why it is behavving like this ?

Thanks

[borisschapira]

@AymenLoukil tbh I tried GitLocalize when working on @SilentJMA's fork but I switched to pure git/github manipulations after many errors I could not explain. If you're working on a single chapter, could you remove yourself from the other ones on this thread first post, so that we keep track on who's working on what?

[nico3333fr]

Here you go dear FR proofreaders => https://github.com/HTTPArchive/almanac.httparchive.org/pull/759 ;)

[nico3333fr]

May I be assigned to the translation of Security one ? :)

[borisschapira]

@AymenLoukil Where are you on the Performance chapter? Can I help?

[bazzadp]

May I be assigned to the translation of Security one ? :)

Done.

@rviscomi any way to give the team edit access back to issues? Otherwise big dependency on you and me. And I might eventually get bored of this 😋

[rviscomi]

Sorry for the trouble. I've reverted the change which should make issues self-assignable again. Instead, I've applied a branch-specific access rule so that only Barry or myself can merge PRs into master. Let me know if this becomes too restrictive.

[bazzadp]

Thanks @rviscomi !

[borisschapira]

I start to translate the Mobile Web chapter.

[nico3333fr]

I'll take also the accessibility statement, might be less difficult to translate :)

[bazzadp]

I'll take also the accessibility statement, might be less difficult to translate :)

First time I wrote one of those, so let me know if you have suggestions for it!

[borisschapira]

I start to translate the Mobile Web chapter.

PR proposed! #838

@AymenLoukil Up on the Performance chapter? I'd really like to continue with this one, if you're not doing it.

[AymenLoukil]

I start to translate the Mobile Web chapter.

PR proposed! #838

@AymenLoukil Up on the Performance chapter? I'd really like to continue with this one, if you're not doing it.

@borisschapira Yes it is in progress.

[bazzadp]

I'll take also the accessibility statement, might be less difficult to translate :)

FYI @nico3333fr I just added to that in #832 for the accessible PDF version of the almanac.

[allemas]

Hi everyone ,
I start to translate the Compression chapter .

[bazzadp]

Bonjour team!

We seem to have lost some momentum here. Would love to get this finished out well before 2020 edition is published as after that the chances of getting it finished plummets even further!

Do any of you have any more time to work on this?

@AymenLoukil / @SilentJMA - you've quite a few chapters tagged against your name but haven't been around lately. Can you let us know if you're still planning on doing all of them? If I don't hear back then will remove your name so others can grab them if they want. I know from above, that @borisschapira was keen to tackle the performance chapter so @AymenLoukil do let us know if you made a start on that, or could hand it over to him if you don't have the time to work on it?

I know it isn't easy but with a little bit of effort am sure we could get a good few more chapters translated, and ideally them all!

[nico3333fr]

One more, done quickly :) https://github.com/HTTPArchive/almanac.httparchive.org/pull/1196 ;)

[nico3333fr]

I hope to be able to jump into security one soon.

[borisschapira]

I'll try to translate "Media" in the next few days.

[rviscomi]

Great work everyone! I think the JS and CSS chapters would be good to translate soon as those got the most page views. Should we unassign those chapters to make sure they're not blocked/stale?

[borisschapira]

I think we can, and we should. If I take JS and @nico3333fr takes CSS, they would be ready before the end of the month.

[nico3333fr]

Please update the issue and assign CSS to me ;)

[bazzadp]

Please update the issue and assign CSS to me ;)

You should be able to edit the issue yourself. Let me know if that is not the case.

[nico3333fr]

Yes, you're right, done :)

[bazzadp]

OK if this isn’t incentive to get the translation finished then I don’t know what is!
https://twitter.com/httparchive/status/1294286600059396097?s=21

[borisschapira]

I've started the translation of the JS chapter

[borisschapira]

I'm starting the Media chapter.

[arigaud-ca]

Hi, following our discussions on Twitter with @nico3333fr and @borisschapira I would be glad to join the team.
I saw that PWA, Page Weight or Fonts are still to translate. Do you have a preference as far as priorities are concerned?

[borisschapira]

👋 welcome @arigaud-ca !

I think I remmember there's some kind of stats page to see the chapters that are the more visited, but I can't find the URL. @rviscomi, @bazzadp would you know?

[bazzadp]

Hi @arigaud-ca - welcome on board. I've sent you invite to the team.

The chapters in the first comment are in rough order of popularity so go with that. Fonts is the most read out of those three chapters if particularly interested in those subjects. Once you accept that team invite you'll be able to edit the first comment and "claim" a chapter so people know you are working on it.

BTW, these pages are worth a look to get up to speed on our process:

• Translator's Guide
• Git Guide, if new to Git or need a refresher

I think I remmember there's some kind of stats page to see the chapters that are the more visited, but I can't find the URL. @rviscomi, @bazzadp would you know?

Presume you mean this one? https://datastudio.google.com/reporting/1c89f8c3-7e11-4376-8815-39966e13180e/page/1M?s=izbpWSqPUmA ?

@borisschapira looks like Performance has freed up and know you were eyeing that one!

[arigaud-ca]

Thanks @bazzadp I will spend some times to go through the documentation first.

[bazzadp]

Another gentle nudge team. Just 9 chapters to go and would love to get this closed out before 2020 chapters come along as think chances of it getting done after that will drop drastically! If you each could do one more chapter each we'd have it pretty much done!

[rviscomi]

+1 to echo @bazzadp I would love to see the 2019 Web Almanac fully supported in French! I really appreciate everyone's time and effort here so I understand if this is a lot to ask. I wish we had more translators to spread the load, or better yet, a budget to compensate you for your time.

[arigaud-ca]

Hello, I have to finish the chapter on fonts. Things have been really crazy this month, I wish October will give me a little more time.

[borisschapira]

Still have to finish the media chapter, you're right. I'll speed it up. But I don't think I'll translate another chapter for 2019, I think I'm getting a little tired of doing this, I'll take a break before 2020 chapters are published.

[nico3333fr]

This is also crazy for me (divorce, lot of work, etc.), but be sure I'll take some time to end CSS chapter!

[bazzadp]

Ah feel bad for pushing guys. Know it's a lot of effort and we all have personal lives too. No rush, and whenever you get time to work on it is entirely up to you! Thanks again for efforts so far.

[arigaud-ca]

Hi. As far as Font chapter is concerned, I have 2 last steps : check if links in the article also exists in French and check some terms to have unity between the articles.
As far as the Git process is concerned I am trying to figure out what I should do next.

[bazzadp]

Hey @arigaud-ca , once you fix those two items for Fonts, you can open a Pull Request for that to be reviewed and then merged in.

After that you can resync your main back to upstream, then create a new branch and work on the next free chapter.

Looks like from the first comment above, that performance is next free but know @AymenLoukil was working on it and @borisschapira expressed an interest in this too if he wasn't able to complete it, so maybe http2 is better one to go for (only a slight bias from me on that one! 😁). Either way just edit the first comment above to mark your name next to a free chapter that takes your fancy so others know you've "claimed" that one and then comes the hard work of the translation, and then submit a new PR for that!

That make sense? Any questions let me know.

[bazzadp]

Or do you mean you don't know how to open a pull request? Should be as simple as going to the Pull Requests tab at the top of this page and GitHub should be clever enough to see you worked on something in your fork and suggest opening a pull request for that work. Again, let me know if you need any Git help and happy to guide.

[nico3333fr]

I did some progress on CSS chapter... it is really long ^^

[bazzadp]

I did some progress on CSS chapter... it is really long ^^

It certianly is! Look how @rviscomi felt after editing it and adding the many, many figures: https://github.com/HTTPArchive/almanac.httparchive.org/pull/441

[nico3333fr]

I just noticed a bug on some FR translations

Is it something that can be fixed to be displayed properly or do we have to remove &nbsp, ? ex. https://almanac.httparchive.org/fr/2019/third-parties

[bazzadp]

Fixed in #1518 . Will see when we can release the fix.

[nico3333fr]

Fine, I won't have to fix in in future PR... :)

[bazzadp]

Though it did confuse me as not set to   in the markdown and looks like a space. I presume it's not a real space but a non-braking space?

Question for you all, should we use those in future or prefer   as more obvious?

[nico3333fr]

Yes, this is a non-breaking space. Personaly, I like it like that.

🎁 => CSS in french https://github.com/HTTPArchive/almanac.httparchive.org/pull/1519

[bazzadp]

Fix was released btw:

Thanks for reporting!

[nico3333fr]

BTW @bazzadp do you know when CSS in french will be deployed?

[bazzadp]

Just did a quick deploy there now: https://almanac.httparchive.org/fr/2019/css