-
Notifications
You must be signed in to change notification settings - Fork 390
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
Traducido archivo reference/datamodel #3351
base: 3.13
Are you sure you want to change the base?
Conversation
All entries translated, horray! 🎉 |
Co-authored-by: rtobar <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Revisado hasta la línea 1658 del po (más las entradas del índice que aparecen al final), todo bien! Súper buen trabajo hasta ahora @xooseph :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Revisado hasta línea 2340, perdón por la demora!
"El iterador retorna objetos :class:`tuple` que contienen ``(start_line, " | ||
"end_line, start_column, end_column)``. La tupla *i-ésima* corresponde a la " | ||
"posición del código fuente que se compiló en la unidad de código *i-ésima*. " | ||
"La información de la columna son compensaciones de utf-8 bytes indexadas en " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"La información de la columna son compensaciones de utf-8 bytes indexadas en " | |
"La información de la columna son compensaciones de bytes utf-8 indexados en " |
@@ -2055,245 +2091,273 @@ msgid "" | |||
"`bytecode`\\s. Each item yielded is a ``(start, end, lineno)`` :class:" | |||
"`tuple`:" | |||
msgstr "" | |||
"Retorna un iterador que produce información sobre rangos sucesivos de " | |||
"objetos :term:`bytecode`. Cada elemento que se produjo es un objeto :class:" | |||
"`tuple`: ``(start, end, lineno)``:" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"`tuple`: ``(start, end, lineno)``:" | |
"`tuple` ``(start, end, lineno)``:" |
|
||
#: ../Doc/reference/datamodel.rst:1345 | ||
msgid "" | ||
"``start`` (an :class:`int`) represents the offset (inclusive) of the start " | ||
"of the :term:`bytecode` range" | ||
msgstr "" | ||
"``start`` (un objeto :class:`int`) representa la compensación (incluido) del " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"``start`` (un objeto :class:`int`) representa la compensación (incluido) del " | |
"``start`` (un objeto :class:`int`) representa la compensación (inclusiva) del " |
|
||
#: ../Doc/reference/datamodel.rst:1347 | ||
msgid "" | ||
"``end`` (an :class:`int`) represents the offset (exclusive) of the end of " | ||
"the :term:`bytecode` range" | ||
msgstr "" | ||
"``end`` (un objeto :class:`int`) representa el desplazamiento (excluido) del " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"``end`` (un objeto :class:`int`) representa el desplazamiento (excluido) del " | |
"``end`` (un objeto :class:`int`) representa el desplazamiento (exclusivo) del " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
También noté que acá usas desplazamiento para offset, que creo que es mejor que "compensación", que se usa en entradas anteriores. Podrías cambiar "compensación" por "desplazamiento" donde corresponda? Gracias!
|
||
#: ../Doc/reference/datamodel.rst:1430 | ||
msgid "" | ||
"The dictionary used by the frame to look up :ref:`built-in (intrinsic) names " | ||
"<naming>`" | ||
msgstr "" | ||
"El diccionario utilizado por el marco para buscar :ref:`nombres " | ||
"(intrínsecos) incorporados <naming>`" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"(intrínsecos) incorporados <naming>`" | |
"incorporados (intrínsecos) <naming>`" |
|
||
#: ../Doc/reference/datamodel.rst:1488 | ||
msgid "" | ||
"Attempting to clear a suspended frame raises :exc:`RuntimeError` (as has " | ||
"always been the case for executing frames)." | ||
msgstr "" | ||
"Al intentar borrar un marco suspendido genera :exc:`RuntimeError` (como " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Al intentar borrar un marco suspendido genera :exc:`RuntimeError` (como " | |
"Al intentar borrar un marco suspendido lanza :exc:`RuntimeError` (como " |
|
||
# Cómo puede quedar esta traducción, para que no quede como: "hace referencia a un :term:`optimized scope`"? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Creo que lo puedes hacer haciendo :term:`ámbito optimizado <optimied scope>`
. Pero creo que también debería traducirse automáticamente si es que el término está ya traducido en glossary.po
, te animas a probar traduciendo solo esa entrada? Puedes ver cómo queda la traducción si sigues el link al readthedocs que aparece en los chequeos de CI (hacia el fondo de la página del merge request donde aparecen en verde o rojo los tests que pasan o no), o si quieres puedes intentar construir la documentación localmente también.
Closes #3289