QuantEcon / QuantEcon/lecture-python-programming.fa

_admonition/gpu.md is present but untranslated (still English)

Abierto Apto para principiantes
#138 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Lenguaje dominante
Python
Estrellas
1
Forks
1
Merge medio
10 h 5 min
PR fusionados (30 d)
5

Descripción

lectures/_admonition/gpu.md in this repo is byte-identical to the English source — it was seeded but never translated. It is included by three lectures (autodiff, jax_intro, numpy_vs_numba_vs_jax), so the English GPU admonition renders inside three otherwise-Persian pages.

For comparison, .zh-cn has a properly translated copy, and .fr was missing the file entirely (fixed in .fr#14).

Why this needs its own issue

A strict build will not catch it. The include resolves, so there is no warning and no error — -W (added to this repo's ci.yml in #137) only catches the missing-file case, not the untranslated-content case. Nothing in the current pipeline flags an asset that exists but was never translated.

That is worth noting beyond this one file: shared assets under lectures/_admonition/ sit outside the set that translation sync moves, so they are neither synced nor reviewed. See action-translation#117 for the same class on quant-econ.bib.

Fix

Translate the admonition body into Persian, keeping the directive header and :class: warning option line unchanged, and keeping the Google Colab URL and the literal UI label intact.

Current content:

:class: warning

This lecture was built using a machine with access to a GPU --- although it will also run without one.

[Google Colab](https://colab.research.google.com/) has a free tier with GPUs
that you can access as follows:

1. Click on the "play" icon top right
2. Select Colab
3. Set the runtime environment to include a GPU

Found while enabling strict builds across the programming trio (QuantEcon/project-translation#9).

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Abre lectures/_admonition/gpu.md y compáralo con la fuente en inglés y la copia traducida .zh-cn. Traduce el cuerpo de la admonición al persa, conservando el encabezado de la directiva, la clase warning, la URL de Google Colab y la etiqueta literal de la UI; verifica que el resultado se renderice correctamente en autodiff, jax_intro y numpy_vs_numba_vs_jax.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
python
Área
documentation, localization
Tipo de issue
Documentación
Dificultad
2/5
Tiempo estimado
1-3 horas
Estado de actividad
Tranquilo
Claridad
Bien especificado
Aptitud para principiantes
78/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.