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

PY4E Book | Filipino Translation #443

Open
engramar opened this issue May 12, 2024 · 2 comments
Open

PY4E Book | Filipino Translation #443

engramar opened this issue May 12, 2024 · 2 comments

Comments

@engramar
Copy link

Hello Prof. Chuck (@csev),

Hope all is well. Is there a quick guide to start translating PY4E in Filipino? I think I can spare some weekend time for this project. I tried installing mactext on my mac but can't seem to get my head around it. =)

I cloned the repo in my local machine and can see the mkd's under book3 folder. Is there a way to just do the actual translation without doing the documentation tech stuff? =) I am happy to just work on an editable PDF if that is available.

Looking forward to contribute. Thanks in advance.

Regards,
Engramar

@csev
Copy link
Owner

csev commented May 19, 2024

The instructions for doing a translation are here:

https://github.com/csev/py4e/blob/master/TRANSLATION.md

The best way to translate is to fork a copy of the git repo and translate the markdown and figures from there.

But if setting all that up is too difficult there is a Word version of the book with no table of contents and no index here:

http://do1.dr-chuck.com/pythonlearn/EN_us/pythonlearn.docx

Ad the translation documentation states, you can publish the resulting translation any way you like - even selling a printed version with the proper attribution like the other translations.

When you are done, I would like a copy of the resulting work to archive and point to on www.py4e.com - Word or PDF is fine.

Your work will need proper acknowledgements as per Creative Commons - that is easy and I am happy to help.

@engramar
Copy link
Author

Thanks for responding Prof. Chuck (@csev). I think I will just use your Word doc =), a lot easier for me and will be handy to edit anywhere, anytime. Will share any progress here. Thanks again. Have a great week ahead!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants