-
-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Translate content to French #539
Comments
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.
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. |
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: 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 ? |
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 |
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. |
@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. |
Thought you might 😀 |
I'll translate the 2020 accessibility chapter :D |
BTW @tunetheweb : we do agree that all 2020 chapters referenced in this issue are the ones we can go, they are finalised, right? |
Correct! Though am sure there are still typos to be found. But translators are extra good at spotting them 😁 |
Oh and still some discussion on Privacy in #1760 so it might change, so will remove that one. |
When the CSS 2020 chapter is translated to French, I'm happy to review it. I'm not a native speaker but lived there for many years and have a good level in reading French. |
Noted! Thanks @svgeesus |
I'll probably translate it, as I did for the CSS chapter of 2019 :) |
Would any of the French translators be able to translate the 2020 Forward from |
@tunetheweb I'm on it. |
I propose to translate the Jamstack chapter in French as a first contribution. |
Hi @stephanebachelier , there's going to be some changes to this chapter (see #1736 ) so this chapter is not ready for translation yet, which is why it's not listed in the first comment on this issue. That one is next on my list to sort, so hoping to look at it tomorrow or this weekend. In the meantime, I've invited you to the team so if you want you can grab one of the other chapters and put your name against it in the first comment to "claim" it? I'll update here once Jamstack chapter is ready for translation. |
Hi @tunetheweb . I'll translate the fonts chapter. I've claimed it as you said. |
@stephanebachelier If you need help, feel free to ask here or in my Twitter DMs (@borisschapira). And if you don't, I'll be happy to review your translation once you have made your PR. |
Oh that reminds me. The changes to the Jamstack chapter have now been merged. So if you’ve not started fonts yet and still want to do that one, then it’s available now. |
Nice! I'm interested but I'll let @stephanebachelier translate it if he wants. I start the SEO chapter instead. |
Final two chapters (privacy and caching) have PRs open for them which should be merged in next week. After that we’ve all the chapters available for you all to choose from! |
Welcome @excellenseo! If you want to wait for the 2021 content, so be it, but if you'd like to start with some content from 2019 or 2020 to translate in French, we'll be happy to onboard you! |
Thanks @borisschapira. If there is still 2019 and 2020 content to translate, wherever I can help, I will. Just let me know. |
The first post in this thread is a summary of our current situation. Each box that is not checked is a chapter to be translated. When there is a name on the right, someone is more or less actively working on it (if you want to participate, you can ask them). When there is none, then the chapter is open for translation. |
We added a small note to our Accessibility Statement about colour contrast issues: almanac.httparchive.org/src/templates/fr/accessibility_statement.html Lines 69 to 71 in 14f8512
Would be great if someone could translate this (nudge, nudge @borisschapira since I know you're very keen on Accessibility!) |
These are the core templates - without which we cannot release any translated chapters. They are in the language specific templates directory:
2024
2022
2021
2020
2019
These are the chapters to be translated. They exist in the content directory:
2024
2022
2021
2020
2019
Additionally the following pages need translated too in the language specific templates directory:
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:
The text was updated successfully, but these errors were encountered: