Skip to content

Guide to migrate to Python 3.8 documentation#60

Closed
humitos wants to merge 11 commits into
3.7from
3.8
Closed

Guide to migrate to Python 3.8 documentation#60
humitos wants to merge 11 commits into
3.7from
3.8

Conversation

@humitos
Copy link
Copy Markdown
Collaborator

@humitos humitos commented May 4, 2020

⚠️ DO NOT MERGE! ⚠️

I took a look at this process and I was able to update our translation files with the new sources in 3.8 without breaking anything.

I described the process in a document at: https://python-docs-es--60.org.readthedocs.build/es/60/upgrade-python-version.html

The diff of all the files that I checked makes sense.

Requires https://github.com/PyCampES/python-docs-es/pull/59/files#diff-fb0d0d7ff27f33697ba3b787ec894677R24 to show 3.8 in the index.

Examples

When it found that the original is similar, it marks it as fuzzy. In this particular case, then only missing things are the ticks and the _ to make it a link --but the translation is correct.

-#: ../Doc/bugs.rst:28
-msgid "`Documentation bugs`_ on the Python issue tracker"
+#: ../Doc/bugs.rst:30
+#, fuzzy
+msgid "`Documentation bugs`_"
+msgstr "Documentación de errores"

Another example of fuzzy (they change list by iterable, but it kept the translation marking it as fuzzy) 👍

-#: ../Doc/tutorial/controlflow.rst:163
+#: ../Doc/tutorial/controlflow.rst:169
+#, fuzzy
 msgid ""
 "Loop statements may have an :keyword:`!else` clause; it is executed when the "
-"loop terminates through exhaustion of the list (with :keyword:`for`) or when "
-"the condition becomes false (with :keyword:`while`), but not when the loop "
-"is terminated by a :keyword:`break` statement.  This is exemplified by the "
-"following loop, which searches for prime numbers::"
+"loop terminates through exhaustion of the iterable (with :keyword:`for`) or "
+"when the condition becomes false (with :keyword:`while`), but not when the "
+"loop is terminated by a :keyword:`break` statement.  This is exemplified by "
+"the following loop, which searches for prime numbers::"
 msgstr ""
 "Las sentencias de lazo pueden tener una cláusula`!else` que es ejecutada "
 "cuando el lazo termina, luego de agotar la lista (con :keyword:`for`) o "

New paragraph are just added with no translations at all

+msgid "`Issue Tracking <https://devguide.python.org/tracker/>`_"
+msgstr ""
+
+#: ../Doc/bugs.rst:33
+msgid ""
+"Overview of the process involved in reporting an improvement on the tracker."
+msgstr ""
+
+#: ../Doc/bugs.rst:35
+msgid ""
+"`Helping with Documentation <https://devguide.python.org/docquality/#helping-"
+"with-documentation>`_"
+msgstr ""
+
+#: ../Doc/bugs.rst:36
+msgid ""
+"Comprehensive guide for individuals that are interested in contributing to "
+"Python documentation."
+msgstr ""
+

Line numbers are updated

 "Una vez dentro, puedes enviar el error. Selecciona el enlace \"Create New\" "
 "en la barra lateral para abrir el formulario del informe de errores."
 
-#: ../Doc/bugs.rst:54
+#: ../Doc/bugs.rst:62
 msgid ""
 "The submission form has a number of fields.  For the \"Title\" field, enter "
 "a *very* short description of the problem; less than ten words is good.  In "

Remove translation that change a lot

 #: ../Doc/tutorial/stdlib.rst:75
 msgid ""
-"The :mod:`getopt` module processes *sys.argv* using the conventions of the "
-"Unix :func:`getopt` function.  More powerful and flexible command line "
-"processing is provided by the :mod:`argparse` module."
+"The :mod:`argparse` module provides a more sophisticated mechanism to "
+"process command line arguments.  The following script extracts one or more "
+"filenames and an optional number of lines to be displayed::"
 msgstr ""
-"El módulo :mod:`getopt` procesa *sys.argv* usando las convenciones de la "
-"función de Unix :func:`getopt`.  El módulo :mod:`argparse` provee un "
-"procesamiento más flexible de la linea de órdenes."

I didn't find too much more different examples. There is a lot like these and they are all 💯 to me! I'm super happy understanding a little more about this process --doesn't seem to be super complicated to keep it up to date.

Comments

  • powrap generates some inconsistencies because our current work is not "powrapped"
  • the header ("Maintained by the python-doc-es workteam.", etc) of all the files are changed by powrap because it's too large

Reference: #22
References: https://www.sphinx-doc.org/en/master/usage/advanced/intl.html#update-your-po-files-by-new-pot-files

@raulcd
Copy link
Copy Markdown
Collaborator

raulcd commented May 4, 2020

Qué grande!

Copy link
Copy Markdown
Collaborator

@raulcd raulcd left a comment

Choose a reason for hiding this comment

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

Ponemos la rama 3.8 como principal y empezamos a meter los cambios ahí? Creo que lo mejor sería tener la última versión traducida como foco y luego centrarnos en otras versiones como la 3.7. Qué dicen @humitos @gilgamezh ?

Comment thread .overrides/upgrade-python-version.rst
@humitos
Copy link
Copy Markdown
Collaborator Author

humitos commented May 5, 2020

Creo que lo mejor sería tener la última versión traducida como foco y luego centrarnos en otras versiones como la 3.7

Me parece bien centrarnos en 3.8, sí.

@humitos
Copy link
Copy Markdown
Collaborator Author

humitos commented May 5, 2020

Si les parece, hago el push con todos los cambios que genera este proceso en esta rama 3.8 así ya quedan y podemos seguir trabajando desde ahí.

humitos added 2 commits May 5, 2020 12:55
This updates all the repository to match cpython 3.8 branch.
@humitos
Copy link
Copy Markdown
Collaborator Author

humitos commented May 5, 2020

Actualicé todos los archivos con los cambios que vienen de 3.8 --debería estar lista esta branch (no hay que hacer merge ya que está contra 3.7, e igualmente esta branch se llama 3.8, que entiendo que es la que vamos a usar)

@humitos
Copy link
Copy Markdown
Collaborator Author

humitos commented May 6, 2020

@raulcd @gilgamezh ¿les parece bien que cerremos esta PR y hagamos que 3.8 sea el branch por default en GitHub así la gente ya empieza a trabajar con eso?

Luego, cuando se haga merge de las PR que tenemos contra 3.7 actualmente, puedo ir actualizando esas traducciones desde 3.7 para traerlas a 3.8.

@raulcd
Copy link
Copy Markdown
Collaborator

raulcd commented May 6, 2020

A mí me parece perfecto, creo que mientras antes lo hagamos mejor

@humitos
Copy link
Copy Markdown
Collaborator Author

humitos commented May 6, 2020

Listo. Ya lo hice.

Por cada PR viejo que tengamos tenemos que ir actualizando 3.8. Todos los PRs nuevos van a ser contra 3.8.

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

Successfully merging this pull request may close these issues.

2 participants