DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to compare the Chinese, English and Spanish editions with Pi Book

Read the same chapter in its three language versions to check translation consistency.

Who it is forA bilingual reader or translator who wants to confirm that a term or claim reads the same across the book's editions.

The problemThe book has one Chinese source and two translations, so a claim could drift in translation without anyone noticing.

The outcomeA short list of places where the English or Spanish version differs in meaning from the Chinese original.

What you need first

  • A web browser to read the online edition, or git and Node.js (npm) for the local reader
  • Access to the pi repository at commit cd20a8d2e if you want to check code references
  • An AI coding tool such as Claude or Cursor if you want an agent to check the book against source

Steps

  1. Clone the Pi Book repo to get the Markdown files. (inferred, check the README)
  2. Open the same chapter in agent/, agent/en/ and agent/es/.
  3. Read the workspace translation notes in agent/TRANSLATION.md to see how the translations are maintained.
  4. Compare key technical terms and code citations across the three versions.

Prompt for your agent

In the antinomie-lab/pi-book repo, open the same chapter from agent/, agent/en/ and agent/es/. Output a list of statements where the English or Spanish text differs in meaning from the Chinese original, with the section name for each. Verify that all code citations appear unchanged in all three versions.

Caveat. The Chinese original is the only content source, so translation differences are fixes to the translated files, not reasons to change the original.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page