[SciPy-Dev] Translating Documentation into Spanish

[Ralf Gommers]

On Fri, Jun 19, 2020 at 7:25 PM Juan Luis Cano <juanlu001 at gmail.com> wrote:

> You might want to checkout what CPython is doing for their docs, using
> gettext and plain pull requests (i.e. no Transifex):
>

Spyder has just moved from such an approach to Crowdin, and are way happier
with the latter. I think PRs for translations is a bad idea in 2020, both
because translators should have a UI that works for them rather than a
dev-centric workflow, and because it's less effort with integration for the
maintainers.

We have found the same with doc/tutorial writing - Sphinx + PRs is
terrible, tech writers much prefer something like a notebook.

Thanks for the suggestion though Juan Luis.

Cheers,
Ralf



> https://github.com/python/python-docs-es
>
> On 6/19/20, Ralf Gommers <ralf.gommers at gmail.com> wrote:
> > On Fri, Jun 19, 2020 at 6:45 PM Ralf Gommers <ralf.gommers at gmail.com>
> > wrote:
> >
> >> Hi Luis, welcome
> >>
> >>
> >> On Thu, Jun 18, 2020 at 6:47 PM Matt Haberland <mhaberla at calpoly.edu>
> >> wrote:
> >>
> >>> These are just my thoughts; someone who has been around longer will
> >>> likely know more, but it might take longer to get that response.
> >>>
> >>> It looks like Sphinx (our documentation system) supports
> >>> internationalization
> >>> <
> https://www.sphinx-doc.org/en/master/usage/advanced/intl.html#using-transifex-service-for-team-translation
> >
> >>> and
> >>> there are services (e.g. Transifex <https://www.transifex.com/>) that
> >>> make crowdsourcing easier. The difficult part is probably building a
> >>> team
> >>> that will review one another's work and maintain the translations as
> the
> >>> English documentation changes. I imagine that users of the
> documentation
> >>> might also want to file bug reports in Spanish, but that might be more
> >>> difficult to support.
> >>>
> >>> > Is there a project already that is translating the documentation into
> >>> Spanish so that I can join?
> >>> I don't know of existing projects, but others might have a better idea
> >>> of
> >>> the history.
> >>>
> >>> > What kind of qualifications do I need? (I have already translated
> some
> >>> technical books for my own learning and entertainment.)
> >>> Probably the ones you have, then. Anyone can contribute to the English
> >>> documentation, and changes are reviewed for quality by maintainers
> >>> before
> >>> inclusion in SciPy. I suppose that the same would be true of Spanish
> >>> translations, except there would need to be a team of translation
> >>> maintainers.
> >>>
> >>> > How do I start? Do I just start translating? If so, when I have
> >>> something finished who do I send it to?
> >>> Unless there is an existing project, someone will need to research how
> >>> to
> >>> manage this sort of project before actual translations could be used.
> >>> I'd suggest contributing to SciPy's English documentation
> >>> <
> https://github.com/scipy/scipy/issues?q=is%3Aopen+is%3Aissue+label%3ADocumentation
> >
> >>> first, and meanwhile, maybe contribute to the Sphinx documentation
> >>> translation <https://www.transifex.com/sphinx-doc/sphinx-doc/> to see
> >>> how that process works. Then I would suggest writing up your thoughts
> on
> >>> how a SciPy documentation translation project might be organized and
> how
> >>> it
> >>> could work technically in order to produce and maintain high-quality
> >>> translations.
> >>>
> >>
> >> I think translating the SciPy docs isn't the best place to start,
> because
> >> it's an enormous task. Here is what I wrote for the NumPy website, which
> >> I
> >> think is a good place to start and needs both working out a few kinks in
> >> the workflow and doing the translation in some of the most-used
> languages
> >> (including Spanish):
> >>
> >
> > Sorry, sent too early.
> >
> >
> https://numpy.org/neps/nep-0028-website-redesign.html#translation-multilingual-i18n
> > https://github.com/numpy/numpy.org/issues/55
> >
> > Now that that website is launched, translations can be tackled.
> >
> > For SciPy, we should do something similar after that (assuming for NumPy
> > it's successful) - start with the most high-level content.
> >
> > Cheers,
> > Ralf
> >
> >
> >
> >>
> >>> On Wed, Jun 17, 2020 at 3:56 PM Luis Lozano <luis9699 at live.com.mx>
> >>> wrote:
> >>>
> >>>> Hello, My name is Luis E. Lozano Marrujo.
> >>>>
> >>>>
> >>>>
> >>>> I am a native Spanish speaker who is interested in helping to
> translate
> >>>> some (most of that which I can translate) of the documentation into
> >>>> Spanish. And I have some doubts:
> >>>>
> >>>>
> >>>>
> >>>> Is there a project already that is translating the documentation into
> >>>> Spanish so that I can join?
> >>>>
> >>>> What kind of qualifications do I need? (I have already translated some
> >>>> technical books for my own learning and entertainment.)
> >>>>
> >>>> How do I start? Do I just start translating? If so, when I have
> >>>> something finished who do I send it to?
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> Thanks for the attention and help. Also much thanks to all the people
> >>>> who develop this stuff!
> >>>>
> >>>> _______________________________________________
> >>>> SciPy-Dev mailing list
> >>>> SciPy-Dev at python.org
> >>>> https://mail.python.org/mailman/listinfo/scipy-dev
> >>>>
> >>>
> >>>
> >>> --
> >>> Matt Haberland
> >>> Assistant Professor
> >>> BioResource and Agricultural Engineering
> >>> 08A-3K, Cal Poly
> >>> _______________________________________________
> >>> SciPy-Dev mailing list
> >>> SciPy-Dev at python.org
> >>> https://mail.python.org/mailman/listinfo/scipy-dev
> >>>
> >>
> >
>
>
> --
> Juan Luis Cano
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at python.org
> https://mail.python.org/mailman/listinfo/scipy-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20200619/0ea01a98/attachment-0001.html>