Skip to content

🌐 [translation-sync] Fix broken raw GitHub URLs for CSV data files#76

Open
mmcky wants to merge 4 commits intomainfrom
translation-sync-2026-03-24T06-31-39-pr-491
Open

🌐 [translation-sync] Fix broken raw GitHub URLs for CSV data files#76
mmcky wants to merge 4 commits intomainfrom
translation-sync-2026-03-24T06-31-39-pr-491

Conversation

@mmcky
Copy link
Contributor

@mmcky mmcky commented Mar 24, 2026

Automated Translation Sync

This PR contains automated translations from QuantEcon/lecture-python-programming.

Source PR

#491 - Fix broken raw GitHub URLs for CSV data files

Files Updated

  • ✏️ lectures/pandas.md
  • ✏️ .translate/state/pandas.md.yml
  • ✏️ lectures/python_advanced_features.md
  • ✏️ .translate/state/python_advanced_features.md.yml

⚠️ Sections Pending Earlier Translation PR

The following sections were not modified by this source PR and are missing from the target. They have been omitted from this PR to keep it scoped to the source PR's actual changes. An earlier translation PR should add them. If that PR is abandoned, run /translate-resync to recover.

  • lectures/python_advanced_features.md: Type hints

Details

  • Source Language: en
  • Target Language: fa
  • Model: claude-sonnet-4-6

This PR was created automatically by the translation action.

@netlify
Copy link

netlify bot commented Mar 24, 2026

Deploy Preview for majestic-griffin-10b166 ready!

Name Link
🔨 Latest commit 5c0b32b
🔍 Latest deploy log https://app.netlify.com/projects/majestic-griffin-10b166/deploys/69c22fd07eb98e0008f92193
😎 Deploy Preview https://deploy-preview-76--majestic-griffin-10b166.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions
Copy link

github-actions bot commented Mar 24, 2026

✅ Translation Quality Review

Verdict: PASS | Model: claude-sonnet-4-6 | Date: 2026-03-24


📝 Translation Quality

Criterion Score
Accuracy 9/10
Fluency 8/10
Terminology 9/10
Formatting 9/10
Overall 8.8/10

Summary: The Persian translation is of high quality overall, demonstrating strong technical accuracy and consistent terminology use. The translation correctly handles Python-specific concepts by retaining English technical terms while providing Persian explanations. Formatting is well-preserved throughout. Minor issues include inconsistent use of 'درس' vs 'سخنرانی' for 'lecture' (the glossary specifies 'درس'), a small inconsistency in footnote vs. body translation of 'data munging', and one instance where 'بازده' (returns) is used in a comment context where 'قیمت' (prices) would be more precise. These are relatively minor issues that do not significantly impact comprehension. Technical Python terminology (iterators, generators, decorators, descriptors, DataFrames, Series) is consistently kept in English with Persian explanations, which is standard practice for Persian technical documentation. The heading-map in the frontmatter is comprehensive and well-structured, correctly mapping all section headings to their Persian equivalents. Mathematical and code formatting is fully preserved — LaTeX, code cells, MyST directives, and all special syntax are intact. The translation of the * and ** operators section is clear and accurate, with 'باز کردن آرگومان‌ها' and 'آرگومان‌های دلخواه' being natural and appropriate Persian translations. Decorators and descriptors section is translated with high accuracy, preserving the pedagogical flow of the original and using appropriate terminology like 'نحو شیرین' for 'syntactic sugar'.

Suggestions:

  • Overview (python_advanced_features): 'سخنرانی' is used to translate 'lecture' — per the glossary, 'lecture' should be translated as 'درس'. The heading and body text use 'این سخنرانی آخر' and 'این سخنرانی اینجاست' where 'این درس آخر' and 'این درس اینجاست' would be more consistent with glossary conventions.

  • Iterables and Iterators: The section heading in the heading-map reads 'Iterables and iterators' (lowercase 'i' in iterators) but in the body it is rendered as 'Iterableها و Iteratorها'. While this is minor, consistency with the source heading 'Iterables and Iterators' (both capitalized) should be maintained in the heading-map key.

  • Advantages of Iterators: 'نمونه بگیریم' for 'sample' is acceptable, but the phrase 'از یک binomial(n,0.5) نمونه بگیریم' mixes English and Persian awkwardly. A clearer phrasing would be 'می‌خواهیم یک نمونه از توزیع دوجمله‌ای binomial(n,0.5) بگیریم' to make the statistical concept clearer.

  • DataFrames (Overview section): The translation of 'data munging' footnote as 'پاک‌سازی داده از یک فرم خام به یک فرم ساختاریافته و تصفیه شده' is accurate but 'تبدیل داده' used in the main body for 'data munging' is slightly inconsistent with 'پاک‌سازی داده' in the footnote. Both occurrences should use the same term for consistency.

  • Exercises (pandas): In the solution to pd_ex2, the comment 'تاریخ شروع مشترک' correctly translates 'Common Start Date', but the inline comment for 'Get the first set of returns as a DataFrame' is translated as 'اولین مجموعه بازده‌ها را به عنوان DataFrame بگیرید' — 'بازده' (return/yield) is used here but in the context it refers to 'prices' (قیمت‌ها), not returns. The variable is named 'p1' suggesting prices. Consider 'اولین مجموعه قیمت‌ها را به عنوان DataFrame بگیرید'.


🔍 Diff Quality

Check Status
Scope Correct
Position Correct
Structure Preserved
Heading-map Correct
Overall 7.5/10

Summary: The scope and position of changes are correct, and document structure is preserved, but the heading-map has minor issues: the pandas.md title heading entry maps to an untranslated value, and the python_advanced_features.md heading-map keys were correctly updated to match the new lowercase source headings.

Issues:

  • In pandas.md heading-map, a new entry '{index}Pandas <single: Pandas>' was added mapping to itself, but the English source title '# {index}Pandas <single: Pandas>' is a level-1 heading that does not appear in the original heading-map. This addition is questionable — the title heading is not a section heading that needs mapping in the same way, and the value maps to the untranslated English string rather than a Persian translation.
  • In python_advanced_features.md, the heading-map keys were changed from title-case (e.g., 'Iterables and Iterators', 'Iterators in For Loops', 'Unpacking Arguments', 'Arbitrary Arguments', 'Generator Expressions', 'Generator Functions', 'Advantages of Iterators', 'An Example', 'Enter Decorators', 'A Solution', 'How it Works', 'Decorators and Properties') to lowercase/original-case versions matching the source headings (e.g., 'Iterables and iterators', 'Iterators in for loops', 'Unpacking arguments', etc.). This is correct because the source document after the edit uses these exact heading texts, so the heading-map keys must match the English heading text that generates the ID. The new source uses lowercase headings, so the keys are now correct.
  • The heading-map in python_advanced_features.md also added a top-level 'More Language Features' entry mapping to 'ویژگی‌های بیشتر زبان', which corresponds to the '# More Language Features' title heading. This is consistent with the pandas.md approach of adding the title heading to the map, though the value in pandas.md maps to itself (not translated) while this one is properly translated.
  • The 'Type hints' section was removed from the source English document (after state) but no corresponding removal or update is needed in the translation heading-map since it was never present in the translation's heading-map to begin with — this is acceptable.
  • The pandas.md heading-map entry for the Pandas title heading maps the value to the untranslated '{index}Pandas <single: Pandas>' rather than a Persian translation, which may be intentional for index directives but is inconsistent with the translation approach used elsewhere.

This review was generated automatically by action-translation review mode.

@github-actions
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant