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

Update README.fr.rst (fix typos, pygame => pygame-ce ...) #2228

Merged
merged 23 commits into from
Aug 27, 2023
Merged

Update README.fr.rst (fix typos, pygame => pygame-ce ...) #2228

merged 23 commits into from
Aug 27, 2023

Conversation

bilhox
Copy link
Contributor

@bilhox bilhox commented Jun 4, 2023

Hi,

Again, I propose a PR to fix some typos, some pygame got updated to pygame-ce, and finally, some sentences got a bit changed to look more natural.

Should be reviewed by @Grimmys

@bilhox bilhox requested a review from a team as a code owner June 4, 2023 18:09
docs/readmes/README.fr.rst Outdated Show resolved Hide resolved
docs/readmes/README.fr.rst Outdated Show resolved Hide resolved
docs/readmes/README.fr.rst Show resolved Hide resolved
docs/readmes/README.fr.rst Outdated Show resolved Hide resolved
docs/readmes/README.fr.rst Outdated Show resolved Hide resolved
docs/readmes/README.fr.rst Outdated Show resolved Hide resolved
@Grimmys
Copy link

Grimmys commented Jun 4, 2023

No blocker on my side, just suggestions.

@@ -198,7 +198,8 @@ Voir les docs/licences pour les licences des dépendances.
.. |BlackFormatBadge| image:: https://img.shields.io/badge/code%20style-black-000000.svg
:target: https://github.com/psf/black

.. _pygame: https://pyga.me
.. _pygame: https://www.pygame.org/docs/
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we linking to the original docs?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's for the thanks:

"[...] et ajoutant du nouveau contenu dans le wiki de pygame_ et sur pygame-ce_. "

Meaning:

"[...] and thanks to the people adding new content in pygame and pygame-ce wikis", with links to them.

If we don't want to link to the original docs, then should we remove the thanks for pygame as well?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's fair, and I'm fine with it. However, I want to be careful about slight content changes between the versions of the readmes as well. I'm fine with it, as long as all versions of the readme stay consistent with each other

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I definitely agree with you, I was starting to think about this issue as well.

But then, what should be the process?
We should always have the English original version in sight next to the translation changes when reviewing them, and if we want to suggest change meaningful for both versions, it should first be applied to the English one?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The more translations we have, the harder this will be to manage. I'm not sure what the best approach would be. Ideally, they'd all be changed at the same time so they're all always in sync, but that's just not feasible

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we should deviate from the original source too much.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay then should I make the same changes to the english readme ? (replacing specific pygame to pygame-ce, and make pygame(-ce) links redirecting to the docs instead of main page)

@bilhox
Copy link
Contributor Author

bilhox commented Jun 6, 2023

I added a warning about french README content.
Is there anything left to do ?

@yunline yunline added the docs label Jun 12, 2023
@Starbuck5
Copy link
Member

Here's the policy I envision for updating the READMEs.

  • Non-English READMEs are just trying to follow the English README's content.
  • Whoever updates the English README has the responsibility to mark all other READMEs as out of date (in English)
  • Translators see the README is out of date and update and update it (they can check the git history on the English README to find what changed). Or they don't, and maybe after a view years of that the Non-English README will be removed for lack of maintenance.

So you want to make a content change to the README?
You need to make it to the English README, then mark all other READMEs as out of date.

In your case, you can make the update to the English README and the French README then mark all other READMEs as out of date.

@Starbuck5
Copy link
Member

@bilhox lets move this forward.

Content changes you've made to the French README should be added to the English README, and you should mark each other translation as out of date.

@bilhox
Copy link
Contributor Author

bilhox commented Jul 11, 2023

Hello,

Okay (I forgot about this PR sorry 😅), shall I also add the policy you envisaged in your last message, directly in the readme ?

@Starbuck5
Copy link
Member

I don't think it's necessary to explain the README update policy in the README. We could have a README-README for that 😄

Don't worry about it in this PR.

@bilhox
Copy link
Contributor Author

bilhox commented Jul 11, 2023

Okay, I added what you wanted. I updated the english README, and warned people ni the french readme that it could be out of date. For the korean (I guess ?) and persian readme, @yolowex and @yunline shall update them.

@yolowex
Copy link
Contributor

yolowex commented Jul 11, 2023

Okay, I added what you wanted. I updated the english README, and warned people ni the french readme that it could be out of date. For the korean (I guess ?) and persian readme, @yolowex and @yunline shall update them.

Sure thing, thanks for the tag

Comment on lines 12 to 13
**Des différences de contenus peuvent être présentes entre le README français, et anglais. Prenez donc bien soin de vérifier les informations de ce README avec le README anglais.**
---------------------------------------------------------------------------------------------------
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why mark this README out of date? Did you make different changes to the English one and the French one?

If you change the English source and also the French translation, it's every other README that's out of date.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it is not saying that this README is out of date, but that it might be at any point in time.

It's more like a safeguard, warning people that they should not 100% trust the content of translation README files.

I think it's the policy you were talking about and then said it should not be added in the README file itself, maybe they just mixed up what you explained.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why mark this README out of date? Did you make different changes to the English one and the French one?

If you change the English source and also the French translation, it's every other README that's out of date.

I updated also the English README (just added some web-links as I did in the French README).
As he said grimmys, the message says it could be out dated" (maybe I'll make it smaller).
Concerning other READMEs, yunline and yolowex got pinned in a message I sent a couple days ago, so they can change their README.

Copy link
Member

@Starbuck5 Starbuck5 Jul 16, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the point of having translated READMEs if we just put generic disclosures that they could be out of date at the top?
Especially since we actually know it's not out of date right now.

If this PR goes through the other READMEs actually will be out of date, so they should get some sort of warning or notice for translators.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So basically, the best I can do is removing this text in the French README, and mark each other README translation as out of date ?

@bilhox
Copy link
Contributor Author

bilhox commented Aug 3, 2023

Ready for reviews

README.rst Outdated Show resolved Hide resolved
README.rst Outdated Show resolved Hide resolved
Copy link
Member

@MyreMylar MyreMylar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall these changes seem fine to me.

I suggest removing the links to both the old and new pygame wikis at the top of the links list as both are targeted more towards in-depth developers of pygame rather than average pygame enjoyers and we already have a link to the compilation part of the most recent wiki.

README.rst Outdated Show resolved Hide resolved
README.rst Outdated Show resolved Hide resolved
docs/readmes/README.fr.rst Outdated Show resolved Hide resolved
Copy link
Member

@Starbuck5 Starbuck5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still doesn't have the warning message in the other readmes to tell translators to update, but at this point I just want to merge this in to resolve the conversation.

@Starbuck5 Starbuck5 merged commit d1fa34f into pygame-community:main Aug 27, 2023
2 checks passed
@Starbuck5 Starbuck5 added this to the 2.4.0 milestone Aug 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants