BotCurrent↗
← Back to examples

Community recipe

Prepare a bilingual document for side-by-side translation review

A bilingual reviewer must compare a document's meaning across languages, but separate files make omissions, shifted paragraphs and untranslated graphics difficult to locate.

Read original recipe
Suggested result

An editable comparison document, a rendered reading copy and a unit-level completeness/terminology review list.

What you need: Source-named agent: Claude Code. Suggested inputs: Authorized source copy; Language and terminology choices; Review requirements. Build from a copy, keep stable unit identifiers and retain the untranslated source. Use a supported document viewer for the editable file and independently inspect the rendered reading copy. Workflow costs and current compatibility remain unverified.

Approve source access and any model transmission, have a competent bilingual reviewer check meaning, and approve the destination before sharing.

Community recipe. BotCurrent has not independently tested this workflow.

Setup and access

Proposed inputs

  1. Name

    Authorized source copy

    Owner

    Document owner

    Minimum scope

    One short non-sensitive document with permission to translate its content.

    Quality check

    Identify its version, reading order and any content that cannot be extracted reliably.

  2. Name

    Language and terminology choices

    Owner

    Document owner and reviewer

    Minimum scope

    Required variety, approved names/terms and a decision on numbers and units.

    Quality check

    Keep brand names, identifiers and code distinct from ordinary prose.

  3. Name

    Review requirements

    Owner

    Bilingual reviewer

    Minimum scope

    Expected units, acceptable layout and unresolved-term policy.

    Quality check

    Require review of all consequential numbers, negations and obligations even in a routine document.

Access and setup — proposed or unknown

Proposed minimum
  1. Build from a copy, keep stable unit identifiers and retain the untranslated source.

  2. Use a supported document viewer for the editable file and independently inspect the rendered reading copy.

Compatibility unknowns
  1. Unknown: available extraction/rendering tools, font availability, mixed-direction behavior across viewers and translation accuracy.

External actions requiring approval
  1. Sending confidential source content to a provider, uploading files, changing a shared original or distributing the translation.

Detailed steps and output format

At a glance

Suggested result
An editable comparison document, a rendered reading copy and a unit-level completeness/terminology review list.Suggested; untested.
Tool
Claude CodeSource-named; check current access.
Suggested inputs
Authorized source copy; Language and terminology choices; Review requirementsProposed; access notes below.
Human review
Approve source access and any model transmission, have a competent bilingual reviewer check meaning, and approve the destination before sharing.Suggested boundaries; source approvals below.
Setup notes
Build from a copy, keep stable unit identifiers and retain the untranslated source. Use a supported document viewer for the editable file and independently inspect the rendered…
Read full note

Build from a copy, keep stable unit identifiers and retain the untranslated source. Use a supported document viewer for the editable file and independently inspect the rendered reading copy.

Guide notes; proposed setup untested.
Cost
Workflow cost not established. Check current tool pricing, setup and human review costs before trying it.No measured cost or time added.
Content depth
Source-linked example · suggestions untestedDepth does not establish successful execution.
Check source evidence and limits ↓

Function and scope

Creative production, Administration · Single task

Editorial classification; no execution or compatibility test is implied.

No tool mapping reviewed for this task.

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

A bilingual reviewer must compare a document's meaning across languages, but separate files make omissions, shifted paragraphs and untranslated graphics difficult to locate.

Suggested task · untested

Prepare a review copy that keeps corresponding content adjacent and makes translation gaps inspectable.

What you could produce

An editable comparison document, a rendered reading copy and a unit-level completeness/terminology review list.

Where these suggestions come from
  • Core problem: Our suggestion; no result reported by the source
  • Agent job: Our suggestion; no result reported by the source
  • Expected output: Our suggestion; no result reported by the source
  • Relevant job roles: Our suggestion; no result reported by the source
  • Benefit type: Our suggestion; no result reported by the source
Suggestions and their limits

Describes the proposed purpose and review output; measured benefit and successful delivery are not established.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Before you try it · suggestions untested

Original editorial decision guidance and synthetic first check; not the creator's procedure and not executed. Operational source claims are reused only through source_evidence_reference.

Read the attributed source evidence and original caveats below ↓

Why use this

  1. When text is translated into a separate document, a missing paragraph can go unnoticed because both files still read fluently. Mixed-direction text adds another risk: an identifier can look right while its punctuation or order is confusing.

  2. An adjacent review copy helps a competent reviewer locate each source unit and check meaning. It should preserve uncertain terms and graphical limitations rather than hide them behind a polished layout.

Why an agent / simpler alternative

Useful judgment

Preserve meaningful document units while drafting a translation and identifying terms that require a human language decision.

Simpler alternative

Use a trusted translator's existing bilingual review workflow or a two-column template for a short plain-text passage.

Unsuitable when

A certified translation is required, the document creates legal or medical consequences, or no qualified reviewer can verify critical meaning.

Expected deliverable and review checks

Proposed artifact

A side-by-side review draft with numbered content units, a completeness checklist and visible unresolved translation notes.

Critical checks
  1. Every intended source unit appears exactly once with its counterpart or an explicit untranslated status.

  2. Numbers, dates, names, units and negation remain semantically equivalent under human review.

  3. Long units, tables and mixed-direction identifiers do not become clipped, misplaced or visually ambiguous.

  4. Graphics are traceable to their originals and any untranslated embedded text is disclosed; visual consistency is not claimed as linguistic accuracy.

Missing output evidence

No source extraction, bilingual review, generated document or visual QA was performed.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

An original one-page museum handout contains a short list, a two-row schedule, a mixed Latin identifier, a negated instruction and a graphic whose words are baked into pixels.

Acceptance checks
  1. The unit checklist finds no missing or repeated rows.

  2. A bilingual reviewer checks the negation and identifier; the graphic's text remains explicitly outside completed translation.

  3. Both editable and reading copies keep correspondence visible without clipping.

Stop conditions
  1. Meaning cannot be verified, source permission is unclear or the request requires certification.

Tasks: Documents & filesResearch & discoveryWriting & content

Useful for: Content creatorAdministrative assistant

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.
Claude CodeIndependent testing: No
Failure handling, costs and limits

Failure signals and proposed responses

  1. Signal

    The translation reads fluently but a source unit is absent.

    Why it matters

    Surface readability can hide substantive omission.

    Proposed response

    Reconcile unit identifiers and restore or explicitly mark the missing material before review.

  2. Signal

    A long translation pushes its counterpart to another page.

    Why it matters

    The comparison purpose fails even if both texts are present.

    Proposed response

    Split at a meaningful shared boundary and recheck both files without shortening away meaning.

  3. Signal

    A graphic contains important untranslated wording.

    Why it matters

    The reader could mistake an incomplete treatment for a complete translation.

    Proposed response

    Label the limitation and seek an authorized transcription or specialist review rather than guess.

Effort and cost — unknown

Setup work
  1. Choose a manageable section, verify source rights and agree terminology.

Ongoing review
  1. Reconcile changed source units and repeat language/layout review after revisions.

Unknowns
  1. Unknown: extraction cleanup, bilingual reviewer effort, model cost and final file size.

Limits

  1. This is a comparison aid, not a certified translation. Supporting a particular language/layout recipe does not establish universal document or language support.

Full source evidence

Community recipe · Tool workflows

Original task title: Prepare a bilingual document for side-by-side translation review

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://github.com/haideralsaadi83-design/arabic-side-by-side-translation/blob/master/SKILL.md ↗

Attributed to: Haider Alsaadi

Supporting source context

Project documentation supporting the linked recipe’s scope, permissions and limits. These references do not establish an independent test or add counted jobs.

Community recipe
Original action type
tool_action
What the source reports
Extracts ordered content units, translates text into Modern Standard Arabic, keeps original graphics unchanged, assembles adjacent source/translation rows in DOCX, then renders and visually checks a PDF copy.
Source outcome limits
Reading/review copy only, not certified translation. Host-specific paths and tool compatibility remain unverified; no completed file, language review or cross-viewer layout result was inspected.
Evidence attribution caveat
This community recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description
No explicit external-sharing gate is specified. Image text without extractable labels stays untranslated with a note rather than invented labels.
Named tools
Claude Code; content-unit JSON; Node/docx assembly; LibreOffice and page rendering.
Model or version
Unknown
Publication date
Unknown
Source last checked
2026-10-14
Demonstrated in Canada
Unknown
Canadian availability
Unknown
Proposed Canadian adaptation
Use the required language variety and terminology; this Arabic recipe does not establish French/English translation suitability.
Recommended approval boundaries
Approve source access and any model transmission, have a competent bilingual reviewer check meaning, and approve the destination before sharing.