That's the same route upon which I embarked, and I'm about 4/5
done with narrative docs. I have been working through the
Pyramid docs to proofread and correct minor things for the last
month across branches 'master', '1.6-branch', and '1.5-branch'.
I started on the master branch, on this file:
https://raw.githubusercontent.com/Pylons/pyramid/master/docs/index.rst
Which RTD renders here:
http://docs.pylonsproject.org/projects/pyramid/en/master/
You can either view the source of index.rst to get the next page
in order or, in the rendered docs click "next" to determine the
next page to translate.
You can fork the master branch into your GitHub account, then
clone it locally as a new project
pyramid-<language-country-string> for your language and country.
I would also strongly recommend that you set up an environment
where you can build the docs locally before publishing your changes.
More information on how to do so is here:
https://github.com/Pylons/pyramid/blob/master/HACKING.txt
--steve
On 11/4/15 at 4:47 PM, [email protected] (Winston Ferreira) pronounced:
Thank you for the feedback.
I agreed that it's a lot of work but every long journey has to start
somewhere and hopefully I will find help along the way.
I think that the best place to start is with the Narrative Documentation
and I believe it doesn't change much across new releases.
What do you think?
Em qua, 4 de nov de 2015 às 14:26, Steve Piercy <[email protected]>
escreveu:
AFAIK, there is no effort at this time. IIRC there were a
couple of efforts for Russian and Japanese. There's probably a
few experts in here who know more than I do, but here are a
couple of things I do know.
Read the Docs uses Transifex to facilitate the review process.
https://www.transifex.com/readthedocs/readthedocs/
RTD suggests to set up a separate project for each language.
http://docs.readthedocs.org/en/latest/localization.html#project-with-multiple-translations
You'd have to decide which git branch of Pyramid you would
translate. Master is the bleeding edge of development,
1.6-branch is the next release, and 1.5-branch is the latest
stable release. I'd suggest master and monitor the upstream
Pyramid master branch. There's also a lot of auto-documentation
of Pyramid's core through Sphinx directives, so you'd have to
update a lot of docstrings, too.
All that said, translation of hundreds of pages of technical
documentation is an enormous undertaking, I'd say in the order
of hundreds of hours of work. That does not include updates for
new releases.
--steve
On 11/4/15 at 7:25 AM, [email protected] (Winston Ferreira) pronounced:
Recently there has been a discussion on Python frameworks on
the Python-brasil forum and one of the main reasons people said
they don't adopt Pyramid is that it lacks documentation in portuguese.
And this got me thinking, is there any work being done on
translating the oficial documentation to other languages like
brazilian portuguese?
I would love to help (or start) translating the documentation.
------------------------
Steve Piercy, Soquel, CA
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.
------------------------
Steve Piercy, Soquel, CA
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.
