Skip to content

Traduccion tutorial/errors.po #58

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 5 commits into from
May 6, 2020
Merged

Traduccion tutorial/errors.po #58

merged 5 commits into from
May 6, 2020

Conversation

hectorcanto
Copy link
Contributor

Trabajo realizado:

  • acabar traducciones pendientes
  • revisar el resto de traducciones para corregir errores (acentos) y dar consistencia

Trabajo transversal:

  • cambiar manejar (y derivados) por gestionar [excepciones]
  • reformular el uso de la forma pasiva por impersonal (evitar la traducción literal)
  • cambiar el pasado por el compuesto

Dudas pendientes:

  • uso complementario de cláusula, declaración, bloque

@hectorcanto hectorcanto changed the title Traduccion tutorial errors Traduccion tutorial/errors.po May 4, 2020
@hectorcanto
Copy link
Contributor Author

Faltan alguns claves, por ejemplo:
If a finally clause is present, the finally clause will execute as the last task before the try statement completes. The finally clause runs whether or not the try statement produces an exception. The following points discuss more complex cases when an exception occurs:

TODO añadir al po

humitos
humitos approved these changes May 4, 2020
View reviewed changes
Copy link
Collaborator

@humitos humitos left a comment

Choose a reason for hiding this comment

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

Genial! Hice algunas sugerencias para que consideres si te parecen bien. Gracias! 👍

eamanu
eamanu reviewed May 5, 2020
View reviewed changes
tutorial/errors.po
"necesita ser verdad para excepciones definidas por el usuario (aunque es una "
"excepción es el nombre de la excepción predefinida que ha ocurrido. Esto es "
"válido para todas las excepciones predefinidas del intérprete, pero no tiene "
"por que ser así para excepciones definidas por el usuario (aunque es una "
Copy link
Contributor

Choose a reason for hiding this comment

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

Me parece que debe el por qué debería ser que acento el qué

@gilgamezh
Copy link
Collaborator

qué falta en este PR? ya tiene un +1 de humitos. @raulcd @eamanu @hectorcanto ?

@humitos
Copy link
Collaborator

humitos commented May 5, 2020

Por mí hacemos merge, nomás.

@humitos humitos merged commit cc9012d into python:3.7 May 6, 2020
@humitos
Copy link
Collaborator

humitos commented May 6, 2020

Gracias!

@hectorcanto
Copy link
Contributor Author

Faltaba alguna sugerencia y quería hacerle una revisión completa. Habro una nueva?

This was referenced May 6, 2020
Closed
Merged
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@humitos humitos humitos approved these changes

@eamanu eamanu eamanu left review comments

@raulcd raulcd raulcd approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@hectorcanto @gilgamezh @humitos @raulcd @eamanu