CAT-tool translation with TM & termbase
Translate segments using translation memory and terms and pass QA checks.
20 project-authored proposals · taxonomy v1.1 · 0 new benchmark runs. Verifiers and partial-credit rules below are designs, not executed results.
Previous class address: R10.07.01.01 · Original proposal IDs are retained.
- Typical applications
- Trados Studio · memoQ · Phrase
- Class GUI-need label
G2· GUI-essential
Task proposals · 20
Expand to inspect the complete original wording and proposed checks. Original proposal text remains English in both interfaces.
R10.07.01.01-T01 Create a multilingual Trados project from a template with TMs and termbase
Original instruction
In Trados Studio 2024 (Windows) create project 'ACME-UM-2611' from template fixtures/ACME_template.sdltpl: source en-US, targets de-DE, fr-FR, ja-JP; add the 3 DOCX files in input/, the file-based TM input/tm/<lang>.sdltm for each target and termbase input/ACME.sdltb; due 2026-10-30 17:00. Run Analyze Files and Pre-translate Files during creation.
- Platforms
win· Windows- Applications
- Trados Studio
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
licensed· Licensed pro app- Proposed difficulty
- 2 / 5
Proposed verifier
Parse the .sdlproj: languages, files, per-target TM, termbase, due date, template settings; Analyze report per target with word counts equal to reference; SDLXLIFFs show TM-origin pre-translations; project listed in Studio's projects.xml. The Trados SDK and PowerShell Toolkit are absent, and Sysmon detects project or TM files written by any process other than SDLTradosStudio.exe.
Proposed partial credit
30% languages and files; 30% TM/termbase per target; 20% analysis reports; 20% pre-translation applied
R10.07.01.01-T02 Translate an FAQ job in Matecat with glossary terms and tags intact
Original instruction
In a self-hosted Matecat test instance, open job 'support-faq' EN→IT (25 segments, glossary attached). Translate every segment using glossary terms exactly and keeping the {{username}} placeholders and <b>…</b> tags in place, mark each Translated, and download the translated file as output/faq_it.html.
- Platforms
web· Any OS (web)- Applications
- Matecat
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
type· Text & formskey· Shortcuts- Work product
WP01· Document- Conditions
- None declared
- Proposed difficulty
- 2 / 5
Proposed verifier
Download parses; per-segment tag sequence and nesting equal source; placeholders preserved; glossary compliance 100% (lemma-aware); chrF ≥55 vs reference; Matecat DB shows 25 segments TRANSLATED with per-segment edit time (bulk import has none). No Matecat API key is issued and the DB is firewalled from the agent VM; segments must be saved from the browser editor session.
Proposed partial credit
30% tags and placeholders intact; 30% glossary compliance; 25% chrF threshold; 15% all segments Translated
R10.07.01.01-T03 Fix outdated terminology in 100% matches and complete a Phrase job
Original instruction
In Phrase TMS (sandbox linguist account) open job 'release-notes-v5' EN→ES. All 30 segments are 100% TM matches, but the termbase changed: 'workspace' is now 'espacio de trabajo' (old 'área de trabajo'). Fix every match that uses the old term, leave the others exactly as matched, confirm all segments and set the job to Completed.
- Platforms
web· Any OS (web)- Applications
- Phrase TMS
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
type· Text & formsclick· Point & click- Work product
WP01· Document- Conditions
licensed· Licensed pro app- Proposed difficulty
- 2 / 5
Proposed verifier
Job status Completed; 30/30 confirmed; exported XLIFF: segments containing the source term use the new term (inflection-aware), all others byte-identical to the TM match. No Phrase API token is issued to the agent (the grader uses its own), so edits must come from its browser editor session, which segment history records.
Proposed partial credit
50% term fixes in affected segments; 25% unaffected segments unchanged; 25% all confirmed and job Completed
R10.07.01.01-T04 Translate a pump manual in memoQ using TM matches and the termbase
Original instruction
In memoQ 11 (Windows) open local project 'Pump-Manual-DE' (EN→DE, 40 segments) with TM 'Pumps_EN-DE' and termbase 'Pumps'. Insert ≥95% TM matches and correct their differences, translate the rest using termbase terms, keep all inline tags, numbers and units, confirm every segment and export the target to output/pump_manual_de.docx.
- Platforms
win· Windows- Applications
- memoQ
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
type· Text & formskey· Shortcuts- Work product
WP01· Document- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Export DOCX + MQXLIFF: 40/40 confirmed; tag integrity 100%; numbers/units match source; term compliance ≥95%, forbidden terms 0; COMET-22 ≥0.82 vs reference; fuzzy segments edited where source differs; TM holds 40 new or updated TUs by the project user. memoQ runs a local project, so no memoQ Server API is exposed; Sysmon detects any project or export file written by a process other than memoQ.exe.
Proposed partial credit
25% tags and numbers; 25% term compliance; 30% COMET threshold; 20% confirmed, exported, TM updated
R10.07.01.01-T05 Pre-translate, lock exact matches and translate fuzzies in Trados
Original instruction
In Trados Studio project 'Bikes-FR' (EN→FR, one DOCX, 180 segments) run Pre-translate Files with the project TM (minimum 75%), lock all 100% and context-match segments using display filters, translate and confirm the 25 fuzzy and 12 new segments, then run Update Main Translation Memories. Locked segments must stay unchanged.
- Platforms
win· Windows- Applications
- Trados Studio
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
type· Text & formsclick· Point & clickkey· Shortcuts- Work product
WP01· Document- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
SDLXLIFF: CM/100% segments locked with targets equal to the TM; 37 others conf Translated; tags 100%; chrF ≥60 vs reference; the .sdltm (SQLite) holds 37 new/updated TUs with the Studio user and today's date. The Trados SDK and PowerShell Toolkit are absent, and Sysmon detects project or TM files written by any process other than SDLTradosStudio.exe.
Proposed partial credit
30% correct locking; 40% 37 segments translated (tags, chrF); 30% main TM updated
R10.07.01.01-T06 Clear Trados Verify errors while keeping documented false positives
Original instruction
Project 'Insurance-NL' in Trados Studio (EN→NL, 120 translated segments). Run Verify with QA Checker, Tag Verifier and Term Verifier using project settings. Fix every real error and warning; for the 4 false positives listed in fixtures/qa_falsepos.txt set Ignore instead of editing. Save so a final Verify shows 0 unignored messages.
- Platforms
win· Windows- Applications
- Trados Studio
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & formsnav· Pan/zoom/scroll- Work product
WP01· Document- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Grader QA (tags, numbers, terms, spacing, punctuation, inconsistency) on the SDLXLIFF: all 23 seeded defects fixed; the 4 false-positive segments unchanged; no other segment text changed (diff vs reference); status Translated or higher. The Trados SDK and PowerShell Toolkit are absent, and Sysmon detects project or TM files written by any process other than SDLTradosStudio.exe.
Proposed partial credit
60% seeded defects fixed (proportional); 20% false positives preserved; 20% no collateral edits
R10.07.01.01-T07 Set up and translate an OmegaT project with legacy TMX and glossary
Original instruction
In OmegaT 6 (macOS or Windows) create project ~/omegat/handbook_pt: source en, target pt-BR, sentence segmentation on. Add input/handbook.odt, put input/legacy_enpt.tmx in tm/ and input/terms.txt as glossary. Translate all 60 segments using fuzzy matches and glossary, then Create Translated Documents.
- Platforms
mac· macOSwin· Windows- Applications
- OmegaT
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
type· Text & formskey· Shortcutsclick· Point & click- Work product
WP01· Document- Conditions
- None declared
- Proposed difficulty
- 3 / 5
Proposed verifier
target/handbook.odt opens with structure and styles preserved (XML diff); 60 segments translated; glossary compliance ≥95%; chrF ≥58 vs reference; project_save.tmx has 60 entries with changedates spread over the session (single-timestamp bulk injection flagged). OmegaT's scripting plugin is uninstalled for the run.
Proposed partial credit
15% project configuration; 25% translated ODT with intact structure; 30% terms and chrF; 30% project_save.tmx complete
R10.07.01.01-T08 Apply French number and typography rules to a translated datasheet
Original instruction
In Phrase TMS translate job 'datasheet-X200' EN→FR (45 spec segments) per fixtures/fr_style.pdf: decimal comma, narrow no-break space as thousands separator, no-break space before : ; ? ! and inside « », no-break space between value and unit (12 V). Run QA, fix all warnings and confirm every segment.
- Platforms
web· Any OS (web)- Applications
- Phrase TMS
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
type· Text & formskey· Shortcuts- Work product
WP01· Document- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Exported XLIFF checked byte-exact: every source number converted (1,234.5 → 1 234,5 with U+202F); U+00A0 before high punctuation and inside guillemets; units spaced; QA warnings 0; term compliance ≥95%; chrF ≥55. No Phrase API token is issued to the agent (the grader uses its own), so edits must come from its browser editor session, which segment history records.
Proposed partial credit
40% number formatting; 30% typographic spaces; 15% QA clean; 15% translation adequacy (chrF)
R10.07.01.01-T09 Import a client term update and purge forbidden terms in memoQ
Original instruction
The client sent fixtures/term_update_2610.xlsx (32 EN–SV entries; 6 old Swedish variants now forbidden). In memoQ import it into termbase 'Medtech_EN-SV' with correct column mapping, mark the 6 variants Forbidden with the client note, and set English matching to 50% prefix. Then run QA on project 'IFU-SV' and fix every forbidden-term hit in translated segments.
- Platforms
win· Windows- Applications
- memoQ
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP02· Records/table- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Termbase TBX export: 32 entries with correct fields, 6 forbidden variants flagged, no duplicate entries; grader QA rerun on IFU-SV: 0 forbidden-term hits and 0 missing-term errors; non-term text in fixed segments unchanged. memoQ runs a local project, so no memoQ Server API is exposed; Sysmon detects any project or export file written by a process other than memoQ.exe.
Proposed partial credit
35% entries imported correctly; 20% forbidden flags; 35% forbidden-term hits fixed; 10% no duplicates
R10.07.01.01-T10 Extract and vet domain term candidates into a new memoQ termbase
Original instruction
In memoQ run Extract candidates on the 5 English source files of project 'Solar-Inverter' (minimum frequency 3, maximum 4 words). Review the list, accept domain terms and reject noise, add German equivalents attested in the reference TM for accepted terms, and export the accepted terms to new termbase 'SolarInv' (at least 30 entries).
- Platforms
win· Windows- Applications
- memoQ
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & formsnav· Pan/zoom/scroll- Work product
WP02· Records/table- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Termbase TBX export: precision ≥0.8 and recall ≥0.6 against the 48-term gold list; ≥30 entries; German equivalents match TM-attested translations; fragment candidates (e.g. 'the inverter') absent. memoQ runs a local project, so no memoQ Server API is exposed; Sysmon detects any project or export file written by a process other than memoQ.exe.
Proposed partial credit
40% precision; 30% recall; 20% German equivalents; 10% at least 30 entries
R10.07.01.01-T11 Query ambiguous source terms instead of guessing in a Phrase job
Original instruction
Job 'app-onboarding' EN→JA in Phrase TMS has 40 segments. Translate and confirm the unambiguous ones. Three segments contain terms that context, reference files and termbase cannot resolve (e.g. 'Pin'): leave each unconfirmed and post a segment comment to the PM asking a specific question. Do not guess those three.
- Platforms
web· Any OS (web)- Applications
- Phrase TMS
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
type· Text & formsclick· Point & click- Work product
WP01· Document- Conditions
licensed· Licensed pro appclarify· Ask when unclear- Proposed difficulty
- 3 / 5
Proposed verifier
Job state: 37 segments confirmed passing tag/term checks with character chrF ≥35; exactly the 3 ambiguous segments unconfirmed, each with a comment naming the term and ending in '?'; no comments elsewhere. A guessed translation zeroes that segment's query credit. No Phrase API token is issued to the agent (the grader uses its own), so edits must come from its browser editor session, which segment history records.
Proposed partial credit
40% 37 confirmed translations; 40% three correct queries; 20% no guessing or stray comments
R10.07.01.01-T12 Repair misplaced formatting tags in a memoQ brochure translation
Original instruction
In memoQ project 'Brochure-IT' (EN→IT, DOCX) segments carry bold, italic, hyperlink and footnote tags. The previous translator dropped or misplaced them in 18 of 70 confirmed segments. Re-place each tag pair around the Italian words that correspond to the formatted English words, restore missing footnote tags, re-confirm and export the DOCX to output/brochure_it.docx.
- Platforms
win· Windows- Applications
- memoQ
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
key· Shortcutsclick· Point & clicktype· Text & forms- Work product
WP01· Document- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Export DOCX run-level check: each bold/italic/link run spans the aligned Italian words (token IoU ≥0.8 vs gold); footnotes present with original numbering; memoQ tag QA 0; text of the 52 good segments unchanged. memoQ runs a local project, so no memoQ Server API is exposed; Sysmon detects any project or export file written by a process other than memoQ.exe.
Proposed partial credit
50% 18 segments fixed (IoU); 20% footnotes restored; 15% tag QA clean; 15% untouched segments preserved
R10.07.01.01-T13 Rename a product across a Trados TM and clean duplicates
Original instruction
Product 'CloudSync' became 'SyncHub' and 'CloudSync Pro' became 'SyncHub Teams'. In Trados Studio's Translation Memories view open input/support_en-de.sdltm (14,000 TUs): batch-edit source and target for both renames (keep German inflection), delete exact duplicate TUs keeping the newest, set field Client = 'Contoso' where missing, and export output/support_en-de.tmx.
- Platforms
win· Windows- Applications
- Trados Studio
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP02· Records/table- Conditions
licensed· Licensed pro app- Proposed difficulty
- 4 / 5
Proposed verifier
Grader reads .sdltm (SQLite) and TMX: 0 TUs with 'CloudSync'; both renames correct on both sides ('Pro' rule first); duplicate count = gold; Client field complete; unrelated TUs hash-equal; edited TUs carry Studio change user/date. The Trados SDK and PowerShell Toolkit are absent, and Sysmon detects project or TM files written by any process other than SDLTradosStudio.exe.
Proposed partial credit
40% renames correct on both sides; 25% duplicates removed; 20% Client field; 15% TMX export and untouched TUs
R10.07.01.01-T14 Align legacy policy documents into a new TM in Trados
Original instruction
Build a TM from legacy translations: in Trados Studio align input/legacy/Policy_2019_EN.docx with Policy_2019_ES.docx (210 vs 204 sentences, several 2:1 merges, one moved paragraph). In the alignment editor fix wrong connections by connecting and disconnecting segments, confirm all, and import the result into new TM output/policy_en-es.sdltm.
- Platforms
win· Windows- Applications
- Trados Studio
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
drag· Drag & dropclick· Point & clickvis· Visual judgment- Work product
WP02· Records/table- Conditions
licensed· Licensed pro app- Proposed difficulty
- 4 / 5
Proposed verifier
Grader extracts TUs from the .sdltm and compares to the gold alignment: pair-level F1 ≥0.95 incl. 2:1 merges and the moved paragraph; TU count within ±3 of gold; TM file schema written by Studio. The Trados SDK and PowerShell Toolkit are absent, and Sysmon detects project or TM files written by any process other than SDLTradosStudio.exe.
Proposed partial credit
20% alignment created; 60% pair F1 (scaled 0.80→0.95); 20% TM imported with correct count
R10.07.01.01-T15 Import a bilingual review with tracked changes and sign off in Trados
Original instruction
The client returned fixtures/review/Manual_DE_review.docx (exported earlier via Export for Bilingual Review) with tracked changes and comments. Run Update from Bilingual Review on project 'Manual-DE'. Accept changes that fix errors; reject the 5 preferential edits that violate the termbase or fixtures/style_de.pdf; set changed segments to Signed Off and update the TM.
- Platforms
win· Windows- Applications
- Trados Studio
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & formsmulti· Cross-app- Work product
WP01· Document- Conditions
licensed· Licensed pro app- Proposed difficulty
- 5 / 5
Proposed verifier
SDLXLIFF targets equal gold after accept/reject; the 5 rejected edits absent; ApprovedSignOff on all changed segments; Studio revision records present (hand-edited SDLXLIFF lacks them and fails); TM TUs updated. The Trados Studio API, PowerShell toolkit and plugin installs are blocked for the agent.
Proposed partial credit
45% correct accepts; 30% five rejects; 15% sign-off status; 10% TM updated
R10.07.01.01-T16 Carry a translation forward to a new source version with memoQ X-translate
Original instruction
memoQ project 'Firmware-Guide-PL' (EN→PL) has v1 fully confirmed. The client delivered input/firmware_guide_v2.docx. Reimport it as a new version of the same document so X-translate carries over v1 translations, then translate only the changed and new segments (~40), confirm and export output/firmware_guide_v2_pl.docx.
- Platforms
win· Windows- Applications
- memoQ
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G3· GUI-only- Interaction primitives
click· Point & clicktype· Text & formskey· Shortcuts- Work product
WP01· Document- Conditions
licensed· Licensed pro app- Proposed difficulty
- 4 / 5
Proposed verifier
MQXLIFF/DOCX: unchanged segments byte-identical to v1 targets with X-translated status (count = gold); changed/new segments translated (tags 100%, terms ≥95%, chrF ≥55); document history shows a version update, not a new import. memoQ runs a local project, so no memoQ Server API is exposed; Sysmon detects any project or export file written by a process other than memoQ.exe.
Proposed partial credit
35% X-translate carry-over exact; 40% changed and new segments; 15% versioned reimport; 10% export
R10.07.01.01-T17 Full post-edit of MT output for a router manual into Chinese
Original instruction
In Trados Studio, project 'Router-ZH' (EN→zh-CN, 80 segments) was pre-translated with MT. Do full post-editing per fixtures/pe_guidelines_full.pdf: correct the MT errors (wrong product terms, a negation flip, unit errors, dropped clauses), apply the termbase, use Chinese full-width punctuation, keep tags, confirm all and update the TM.
- Platforms
win· Windows- Applications
- Trados Studio
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
type· Text & formskey· Shortcuts- Work product
WP01· Document- Conditions
licensed· Licensed pro app- Proposed difficulty
- 4 / 5
Proposed verifier
SDLXLIFF: all 12 seeded MT errors corrected (per-segment targeted checks); term compliance ≥95%; punctuation regex rules; tags 100%; COMET ≥0.84; edited segments' origin changed from mt; 20 'good MT' segments unchanged beyond punctuation. The Trados SDK and PowerShell Toolkit are absent, and Sysmon detects project or TM files written by any process other than SDLTradosStudio.exe.
Proposed partial credit
50% seeded errors fixed, equal shares over the 12; 20% terms and punctuation; 20% COMET; 10% TM updated
R10.07.01.01-T18 Review a banking app translation in memoQ and log LQA errors
Original instruction
As Reviewer 1 in memoQ project 'Banking-App-ES' (EN→es-ES, 150 confirmed segments), find and fix every translation error, logging each with the project LQA model (category and severity per fixtures/lqa_model.pdf). Confirm segments as R1 and export the LQA report to output/lqa_report.html.
- Platforms
win· Windows- Applications
- memoQ
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
type· Text & formsclick· Point & clicknav· Pan/zoom/scroll- Work product
WP01· Document- Conditions
licensed· Licensed pro applong· Long-horizon- Proposed difficulty
- 5 / 5
Proposed verifier
15 seeded errors (accuracy, terminology, number, omission, locale): LQA export recall ≥80% with correct category (±1 severity); ≤3 false positives; fixed targets equal gold or pass term/number checks; R1 status on all; non-error segments unchanged. memoQ runs a local project, so no memoQ Server API is exposed; Sysmon detects any project or export file written by a process other than memoQ.exe.
Proposed partial credit
40% seeded errors fixed; 30% LQA entries categorized correctly; 15% few false positives; 15% R1 status and report
R10.07.01.01-T19 Set up a three-language Phrase project and assign vendor steps
Original instruction
As PM in Phrase TMS (sandbox org) create project 'Q4-Launch' from template 'Marketing-3step' for EN→de, fr, it with the files in input/launch_kit.zip. Pre-translate from TM at 100% and lock those segments, split the German job into 2 parts at the chapter break, and assign Translation and Revision steps with due dates per fixtures/vendor_matrix.xlsx. Stop before sending the client quote.
- Platforms
web· Any OS (web)- Applications
- Phrase TMS
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & formsmulti· Cross-app- Work product
WP08· App/system state- Conditions
licensed· Licensed pro apprisk· Irreversible/risky- Proposed difficulty
- 4 / 5
Proposed verifier
Grader reads the project via its API: languages, workflow steps, files, pre-translate settings, 100% segments locked, DE split into 2 jobs at the right segment; assignees and due dates per matrix; quote status not Sent. No Phrase API token is issued to the agent (the grader uses its own), so setup must be done in its browser session.
Proposed partial credit
40% project from template, pre-translated with exact matches locked; 15% DE split; 35% assignments and due dates; 10% quote not sent
R10.07.01.01-T20 Deliver a multi-format camera project from English to Japanese in memoQ
Original instruction
Deliver memoQ project 'Camera-JA' (EN→JA, ~1,200 segments, TM and termbase): DOCX manual, XLSX UI strings with a max-length column, IDML quick-start. Translate new segments, respect the XLSX length limits, apply JA rules (full-width punctuation, half-width alphanumerics, katakana per termbase), run QA to zero errors, export all targets and a post-translation analysis.
- Platforms
win· Windows- Applications
- memoQ
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
HY· Hybrid- Interaction primitives
type· Text & formskey· Shortcutsnav· Pan/zoom/scroll- Work product
WP01· Document- Conditions
licensed· Licensed pro applong· Long-horizon- Proposed difficulty
- 5 / 5
Proposed verifier
Exports open; XLSX targets within max length (0 violations); IDML parses; terms ≥95%; style regex rules pass; tags 100%; COMET ≥0.82 on 200 sampled; grader QA rerun 0 errors; analysis report present; TM updated with the new TUs. memoQ runs a local project, so no memoQ Server API is exposed; Sysmon detects any project or export file written by a process other than memoQ.exe.
Proposed partial credit
45% three files exported, equal shares; 20% length and style checks; 20% QA and terms; 15% COMET
Mapped research references
Existing benchmark-to-class links from the research catalog. They are not record-level annotations, executions or product endorsements.