almanac.httparchive.org
almanac.httparchive.org copied to clipboard
HTTPArchive
Translate content to French
These are the core templates - without which we cannot release any translated chapters. They are in the language specific templates directory:
- [x] base.html - @borisschapira
- [x] base_chapter.html- @borisschapira
- [x] error.html- @borisschapira
2022
- [x] base.html -
- [x] contributors.html -
- [x] index.html -
- [x] table_of_contents.html -
2021
- [x] base.html -
- [ ] base.html - foreword
- [x] contributors.html -
- [x] index.html -
- [x] table_of_contents.html -
2020
- [x] base.html - @borisschapira
- [x] contributors.html - @borisschapira
- [x] index.html - @borisschapira
- [x] table_of_contents.html - @borisschapira
2019
- [x] base.html - @borisschapira
- [x] contributors.html - @borisschapira
- [x] index.html - @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:
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 -
- [x] performance - @borisschapira
- [ ] security - @nico3333fr
- [ ] jamstack -
- [ ] fonts - @stephanebachelier
- [ ] mobile-web -
- [ ] pwa -
- [ ] http2 -
- [ ] capabilities -
- [ ] third-parties -
- [ ] page-weight -
- [ ] caching -
- [ ] resource-hints -
- [ ] privacy -
- [ ] compression -
- [ ] ecommerce -
- [ ] media -
2019
- [x] javascript - @borisschapira
- [x] css - @nico3333fr
- [x] seo - @AymenLoukil
- [ ] performance -
- [ ] http2 -
- [x] markup - @SilentJMA & @borisschapira
- [x] third-parties - Partie Tiers @borisschapira
- [x] 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:
- [ ] 2021/methodology.html -
- [x] 2019/methodology.html @borisschapira
- [x] 2020/methodology.html - @tunetheweb - #1420
- [x] 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)".
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.
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.
@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.
@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
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
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
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 ?
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.
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
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
Cool open a pull request for that and then @AymenLoukil can review when he gets a chance.
Yes. Please ping me when PR is open. I also added my name in front of some chapters.
Yes. Please ping me when PR is open. I also added my name in front of some chapters.
@AymenLoukil & @tunetheweb You can check please its really hard to translate to FR
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.
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!!
Also see if you can request to join the Translator team: https://github.com/orgs/HTTPArchive/teams/translators/members
@tunetheweb I can't access this page, so I guess I can't request to join.
Ah man. Same with this one? https://github.com/orgs/HTTPArchive/teams/almanac-contributors/members
@tunetheweb Yes. I don't even see the "Teams" tab, not being in a team.
@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.
@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.
@SilentJMA @tunetheweb @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
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).
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.
@borisschapira @AymenLoukil you can join me on a team on Gitlocalize so we can work on it
@borisschapira I assigned the rest of the non-chapter pages to yourself since you stormed through the first set.
@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
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?