Skip to content
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

Open
SilentJMA opened this issue Nov 25, 2019 · 60 comments
Open

Translate content to French #539

SilentJMA opened this issue Nov 25, 2019 · 60 comments

Comments

@SilentJMA
Copy link
Contributor

@SilentJMA SilentJMA commented Nov 25, 2019

These are the chapters to be translated, and they exist in the content directory:

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

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.


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

This comment has been minimized.

Copy link
Contributor

@bazzadp bazzadp commented Nov 25, 2019

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.

@bazzadp

This comment has been minimized.

Copy link
Contributor

@bazzadp bazzadp commented Nov 25, 2019

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

This comment has been minimized.

Copy link
Contributor Author

@SilentJMA SilentJMA commented Nov 25, 2019

@bazzadp i will use Gitlocalize

@bazzadp

This comment has been minimized.

Copy link
Contributor

@bazzadp bazzadp commented Nov 25, 2019

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

@rviscomi rviscomi added this to TODO in Web Almanac via automation Nov 25, 2019
@rviscomi rviscomi added this to the Après Ski milestone Nov 25, 2019
@SilentJMA

This comment has been minimized.

Copy link
Contributor Author

@SilentJMA SilentJMA commented Nov 25, 2019

@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

This comment has been minimized.

Copy link
Contributor

@bazzadp bazzadp commented Nov 25, 2019

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

This comment has been minimized.

Copy link
Contributor Author

@SilentJMA SilentJMA commented Nov 25, 2019

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

This comment has been minimized.

Copy link
Contributor Author

@SilentJMA SilentJMA commented Nov 26, 2019

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

This comment has been minimized.

Copy link
Contributor

@bazzadp bazzadp commented Nov 26, 2019

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

This comment has been minimized.

Copy link
Contributor Author

@SilentJMA SilentJMA commented Nov 26, 2019

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

This comment has been minimized.

Copy link
Contributor Author

@SilentJMA SilentJMA commented Nov 27, 2019

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

This comment has been minimized.

Copy link
Contributor

@bazzadp bazzadp commented Nov 27, 2019

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

@AymenLoukil

This comment has been minimized.

Copy link

@AymenLoukil AymenLoukil commented Nov 27, 2019

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

@SilentJMA

This comment has been minimized.

Copy link
Contributor Author

@SilentJMA SilentJMA commented Nov 27, 2019

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

This comment has been minimized.

Copy link
Contributor

@borisschapira borisschapira commented Nov 27, 2019

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

This comment has been minimized.

Copy link
Contributor

@bazzadp bazzadp commented Nov 27, 2019

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

This comment has been minimized.

Copy link
Contributor

@bazzadp bazzadp commented Nov 27, 2019

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

@borisschapira

This comment has been minimized.

Copy link
Contributor

@borisschapira borisschapira commented Nov 27, 2019

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

@bazzadp

This comment has been minimized.

Copy link
Contributor

@bazzadp bazzadp commented Nov 27, 2019

@borisschapira

This comment has been minimized.

Copy link
Contributor

@borisschapira borisschapira commented Nov 27, 2019

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

Capture

@allemas

This comment has been minimized.

Copy link

@allemas allemas commented Dec 2, 2019

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

@SilentJMA

This comment has been minimized.

Copy link
Contributor Author

@SilentJMA SilentJMA commented Dec 2, 2019

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

This comment has been minimized.

Copy link
Contributor Author

@SilentJMA SilentJMA commented Dec 2, 2019

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

This comment has been minimized.

Copy link

@nico3333fr nico3333fr commented Dec 2, 2019

@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

This comment has been minimized.

Copy link
Contributor

@bazzadp bazzadp commented Dec 2, 2019

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

This comment has been minimized.

Copy link

@allemas allemas commented Dec 2, 2019

Thanks, it's ok for me now :)

@SilentJMA

This comment has been minimized.

Copy link
Contributor Author

@SilentJMA SilentJMA commented Dec 3, 2019

Thanks, it's ok for me now :)

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

@borisschapira

This comment has been minimized.

Copy link
Contributor

@borisschapira borisschapira commented Dec 3, 2019

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

@borisschapira

This comment has been minimized.

Copy link
Contributor

@borisschapira borisschapira commented Dec 3, 2019

@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

This comment has been minimized.

Copy link

@allemas allemas commented Dec 3, 2019

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

This comment has been minimized.

Copy link
Contributor Author

@SilentJMA SilentJMA commented Dec 3, 2019

@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

This comment has been minimized.

Copy link
Contributor Author

@SilentJMA SilentJMA commented Dec 3, 2019

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

This comment has been minimized.

Copy link

@nico3333fr nico3333fr commented Dec 3, 2019

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

This comment has been minimized.

Copy link

@nico3333fr nico3333fr commented Dec 4, 2019

You may assign me the accessibility chapter @SilentJMA :)

@bazzadp

This comment has been minimized.

Copy link
Contributor

@bazzadp bazzadp commented Dec 4, 2019

You may assign me the accessibility chapter @SilentJMA :)

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

@nico3333fr

This comment has been minimized.

Copy link

@nico3333fr nico3333fr commented Dec 4, 2019

@bazzadp right, done, thanks :)

@bazzadp

This comment has been minimized.

Copy link
Contributor

@bazzadp bazzadp commented Dec 21, 2019

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

This comment has been minimized.

Copy link
Contributor

@borisschapira borisschapira commented Dec 21, 2019

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

This comment has been minimized.

Copy link
Contributor

@JustinyAhin JustinyAhin commented Dec 22, 2019

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

This comment has been minimized.

Copy link
Contributor

@bazzadp bazzadp commented Dec 22, 2019

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

This comment has been minimized.

Copy link

@nico3333fr nico3333fr commented Dec 23, 2019

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

@bazzadp

This comment has been minimized.

Copy link
Contributor

@bazzadp bazzadp commented Dec 23, 2019

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

This comment has been minimized.

Copy link
Member

@rviscomi rviscomi commented Jan 6, 2020

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.