How can a publisher translate a Common Cartridge 1.4 course package so that a teacher abroad can find the right lesson without losing the files, assessment settings, launch links or course structure? Common Cartridge is an interoperability format for exchanging educational content between learning management systems and repositories. A cartridge is not merely a zip file containing prose. It is a network of resources, references, assessments, navigation labels and often learning-tool connections whose relationships matter as much as the words on the screen.
People searching for Common Cartridge localization, Thin Common Cartridge translation, LMS course import, imsmanifest.xml navigation, K–12 curriculum metadata, QTI assessment language, LTI resource links and multilingual educational content need a process that separates text suitable for translation from identifiers and controls that must remain technically stable. This guide explains those boundaries with teaching examples, practical import tests, cross-border curriculum decisions and ways to distinguish a successful translation from an attractive but broken course.
The audience includes educational publishers, school systems, universities, instructional designers, localization specialists, accessibility reviewers and administrators who move content between platforms. You do not need to write software to follow the main ideas. You do need to recognize that a course title, an assessment key, a resource identifier and an authorization reference serve different purposes. The central aim is to let more people understand and use a learning resource while protecting what the original course actually teaches, tests and grants access to.
Why a course package is not a translated booklet
A textbook usually has a visible reading order, a beginning and an end. A digital course package may contain several orders at once: the course menu, the teacher’s preferred route, dependencies among resources, and the path through an assessment. A teacher might open chapter five before chapter two, while students see only the items that have been released. Translating the headings accurately does not guarantee that those routes still exist after import. The interface could show a perfect translated menu while the next link points to a missing file.
Treat the package as a teaching environment rather than a document. Ask what each element does for the learner: introduces an idea, supplies evidence, gives practice, measures performance, opens an outside tool or provides administrative guidance. If the same short word appears in all these places, its translation may need to differ because the job differs. The label ‘Review’, for instance, could mean revising a lesson, reviewing an assignment before submission or opening an instructor’s moderation screen. Preserve the action as well as the literal wording.
What Common Cartridge and Thin Common Cartridge exchange
Common Cartridge packages can combine web content, resources and structured assessments for import into learning platforms. Thin Common Cartridge is primarily a way to transfer a structured collection of links to learning resources that remain outside the receiving system. Both approaches support useful reuse, but the operational consequences are different. A traditional cartridge may contain local media files that can be checked for completeness; a thin cartridge may depend on live external availability, authorization and changing content at the supplier.
A translation plan must state which arrangement it covers. When the resources are embedded, the translator may have direct access to the source HTML, captions, PDF alternatives and assessment text. When resources remain external, the team may only control the displayed discovery labels and the publisher’s own localized destinations. Never describe a successfully imported thin cartridge as a fully offline course. Its navigation may appear locally, but the learning experience still depends on external services and the learner’s permission to open them.
Version 1.4 and implementation profiles
The Common Cartridge and Thin Common Cartridge 1.4 material on 1EdTech’s standards site describes a candidate-final specification and related K–12 interoperability goals. Particular learning platforms may implement earlier releases, different certification profiles or selected features. A content supplier therefore needs the receiving system’s accepted version and capabilities, not just the newest number visible in a web search. An export from one system can contain features that another system imports incompletely without warning.
Before preparing multilingual editions, gather the source package version, platform release, target import profile, assessment support, external-tool support and content accessibility expectations. Record what happened in a reference import of the original-language package. This baseline matters: if a mathematics question was already broken before localization, the translation should not be blamed for it. Conversely, a target-language build that adds a new defect should not hide behind the fact that import generated a success message.
The manifest as a map rather than an essay
A manifest describes the package and its inventory. In many content-package workflows an imsmanifest.xml file connects resources, organizations and items so importing systems know which objects to locate and how to present them. The machine-readable element names, namespaces, reference IDs and resource locations are structural data. Their apparent English words do not make them ordinary sentences. Translating a field name or modifying an identifier can break an otherwise clear package.
The text that appears inside a menu title may be a genuine translation target, while the identifier on the surrounding item is not. The same rule applies when a resource path happens to contain words: the path is first an address, and changing it requires corresponding changes everywhere it is referenced. For localization, the safer starting model is to leave addresses intact, create target-language descriptions where the format permits them and prove that every reference still resolves after packaging.
Course organizations, hierarchy and the learner’s route
An organization or navigation structure expresses how topics are arranged for use. Imagine a history course with an introduction, three thematic units, a source-analysis workshop and a final essay. A translated title such as ‘Primary sources’ may be concise and correct, yet a new learner could mistake it for sources about primary education. Contextualizing the label as ‘Historical primary sources’ helps without moving its item. Clarity can improve while hierarchy remains unchanged.
A localization reviewer should walk the course as several real users would. A learner checks whether the next activity is understandable. A teacher checks whether resource ordering, hidden teaching notes and lesson objectives remain sensible. An administrator checks whether imports preserve item counts and access restrictions. These are different tests. A heading can be linguistically correct and still mislead a role that encounters the heading in a different part of the platform.
Resources, dependencies and file inventory
A course resource may refer to HTML pages, images, stylesheets, scripts, worksheets or further subresources. Its displayed name is not necessarily its filesystem location, and packaging systems can impose resource-type conventions. A translator who opens a zip archive and renames image folders into a target language may unintentionally invalidate every HTML reference that expected the original path. The resulting failure might appear only when a student reaches a late lesson.
Create a file inventory that distinguishes learner-facing language, embedded media content, software resources and stable technical references. Inspect HTML relative links and media references; identify which source files need translation or captions and which must be preserved byte for byte. If a file is truly being replaced, manage the changed dependency deliberately, update all references that are meant to change and validate the complete package. Do not use attractive filenames as a substitute for link testing.
A course title, a resource title and a page heading are different
A course may be called ‘Scientific Investigation’, its first module ‘Observation’, and a video ‘What counts as evidence?’. Those names live at different levels and answer different reader questions. Translation must respect their scope. Replacing the course title with the name of the introductory module can make the imported resource appear narrower than it is. Replacing a video heading with a generic subject name can conceal what students are about to watch.
A useful terminology sheet therefore includes context, source location and audience as well as approved equivalents. A bare bilingual glossary cannot resolve all cases. In some languages a short menu label may require a noun, while a page heading reads more naturally as a question. That variation is acceptable if both expressions point to the same learning activity. What must not change is whether the resource teaches, assesses, references or administers a particular topic.
Learning-object metadata and discoverability
Cartridge metadata can help a teacher locate resources by subject, audience, education level and standards alignment. Descriptive terms can be translated; stable framework identifiers and resource identities should not be invented or silently redirected. A geometry worksheet mapped to one jurisdiction’s progression is not automatically aligned to every similarly named unit elsewhere. Translating a grade label may make it familiar, but familiarity is not proof of curricular correspondence.
A strong multilingual record keeps the originating framework visible and explains any separately reviewed local comparison. The target metadata should help users evaluate suitability rather than oversell universality. Say that a resource introduces triangle congruence with specified prerequisites instead of claiming it meets a foreign national examination standard without review. Search optimization is useful only if the users arriving from search find material matching the promised level, content and activity.
Curriculum references and the boundary of equivalence
The 1EdTech ecosystem includes ways to reference competency and academic-standard identifiers, including CASE. A course package can use such references to support discovery and alignment. Those identifiers are not convenient strings for free translation. They designate framework nodes maintained by a particular authority. A target-language label can explain a node, but replacing its identifier with an apparent foreign equivalent would create a new substantive educational assertion.
Consider two curricula that both mention fractions. One expects visual representations only; the other expects operations with mixed numbers and explanation of errors. They share vocabulary but may not share demand. Keep the recorded source alignment and, when a qualified curriculum expert has compared the actual outcomes, add a clearly identified local mapping. Students need the truth about readiness more than a broad claim that every lesson suits every country’s schools.
Assessment questions need stronger protections
A question is a measured task, not simply a string in a learning page. Translating its prompt can change difficulty, hint at the correct answer or remove an ambiguity deliberately present in the source. For an essay question, the verbs ‘compare’, ‘evaluate’ and ‘describe’ demand different cognitive work. For a multiple-choice item, changing the grammatical form of one option can reveal the key even if all options appear semantically related.
Coordinate bilingual review with a subject expert and a test specialist. Preserve which response is keyed, what evidence a response must supply, how partial credit is allocated and what the platform displays after an attempt. For consequential assessments, test translated items empirically where feasible rather than assuming that linguistic similarity guarantees equal measurement. A translated item may need documented adaptation, and the decision to equate scores across versions requires more than a valid package import.
QTI content inside the course
Question and Test Interoperability, or QTI, is one route by which assessment material can move among compatible systems. Common Cartridge 1.4 describes support within the broader 1EdTech ecosystem for QTI 3 contexts, though real import compatibility depends on platform implementation. A translator may encounter question stems, feedback messages, item metadata, scoring expressions and response-processing rules in related artifacts. Only some are prose intended for display.
Never translate a variable, response identifier, processing expression or machine-recognized token because it resembles English. Translate the candidate-facing wording and appropriate feedback while retaining the relationship to answer processing. A negative-worded question deserves an additional review: if ‘not’ disappears or moves, the keyed answer may become wrong. The target package should be tested by actually taking sample quizzes, not merely by opening a list of imported assessment titles.
LTI links and external-learning tools
Some cartridges contain references that launch external learning tools through LTI rather than storing the entire exercise locally. A display name such as ‘Explore the simulation’ can usually be localized. A launch endpoint, tool registration, deployment identifier or security claim is not a display name. Editing those controls can prevent access, place learners into the wrong context or break gradebook communication. Translation responsibilities stop before unauthorized changes to the tool’s integration contract.
Ask whether the external provider offers a supported language setting, a target-language content path or a genuinely separate localized edition. Do not point a link at an unrelated website because it has a similar title in the target language. A teacher planning an international course also needs to know whether licensing, authentication, age rules and data processing terms differ by region. A translated description cannot promise access that the supplier has not granted.
Language tags and mixed-language courses
A course may contain English narration, Spanish subtitles, mathematics notation and a French glossary. The language of the menu is not necessarily the language of every embedded learning object. A cataloguer should distinguish interface language, learning-content language, available translation, subtitle language and the language being taught. Labeling an entire course ‘Spanish’ because its new menu is Spanish can mislead someone looking for Spanish-language instruction.
Use recognized language tagging where the format and receiving platform support it, and test whether the tags survive import. Treat bilingual and language-teaching materials with special care because changing a source phrase can remove the very example a student is meant to analyze. If the source includes an untranslated quotation, indicate that it is intentional rather than presenting partial coverage as a completed translation.
Accessibility is part of educational fidelity
A narrated science video may have captions, a transcript, descriptive text for diagrams and controls that work with assistive technology. Localization that replaces only the visible slide headings gives neither equivalent access nor a faithful learning experience. Captions need timing and speaker meaning; an accessible diagram description must communicate relationships rather than merely list colors. A local script with different reading speed may make the same timed exercise inaccessible.
Check keyboard navigation, reading order, headings, image alternatives, captions, language changes and media controls after import. Ask an accessibility specialist to verify learning tasks that depend on sensory information. An audio description of a geometry construction must communicate the angle, orientation and sequence relevant to the task. Simply calling the image ‘a triangle’ is insufficient when the answer depends on which sides are marked equal.
Permissions, licensing and regional availability
A cartridge may include teaching content for which the publisher owns translation rights, content licensed only for one market and links to third-party material. The ability to export a package does not automatically confer permission to translate or redistribute every asset inside it. Likewise, a resource that opens during an administrator’s test may fail for students in another country because of licensing, institutional authorization or geographic restrictions.
Document the rights and provenance of assets before promising a full multilingual edition. Separate permission to describe a work from permission to modify it and permission to distribute a modified copy. A localized catalogue entry can help users discover a resource even when the underlying textbook cannot lawfully be adapted. When limits exist, communicate them plainly; do not replace the missing material with something that changes the learning objectives without telling teachers.
Keep teacher instructions and student instructions distinct
The same source package may contain content for a student and for a facilitator. A note saying ‘Release the model answer after marking’ is a teacher’s operational instruction, not a message to display to students before the activity. If it is translated and accidentally placed into the student view, the assessment can be compromised. Conversely, withholding a student safety instruction because it was mislabeled as teacher-only can harm the learning experience.
Inventory roles before translation. Mark answer keys, grading rubrics, teacher guides, hidden setup instructions and student-facing activities separately. Review whether the target LMS imports their visibility correctly. Wording choices also depend on audience: an instruction for an instructor can be concise and operational, while a younger learner may require concrete steps and familiar language. Adapt register without collapsing the role boundary.
Term consistency across lessons
Long courses repeat concepts across introductions, exercises, feedback and summary cards. If one key term receives four unrelated translations, a learner may assume the author has introduced four concepts. On the other hand, forcing one target word into every context can produce unnatural or misleading phrasing. For example, ‘model’ could name a mathematical representation, a physical object, a predictive statistical method or an example answer supplied by a teacher.
Create a contextual term bank, not a blind substitution rule. For each recurring technical concept, record its definition, preferred form, permitted variants, common confusions and sample context. Review term choices across the full teaching sequence, because a wrong term in the first lesson may distort understanding of later explanations. Consistency protects learning only when the underlying meanings genuinely match.
Numbers, units and symbolic notation
Educational materials often combine decimal notation, thousands separators, percentages, currency, scientific units, graphs and formulae. Locale conventions can make an ordinary number appear different, and a careless conversion may introduce a wrong result. A worksheet that uses a decimal comma can be perfectly clear in one locale and confusing in another. The translator must decide whether to preserve the original presentation, adapt it consistently or add explanatory notation.
Distinguish display conventions from mathematical quantities. Units, tolerances, measurement bases and values must be checked after any presentation change. Do not alter a calculation to make a worked example seem locally familiar. If a geography exercise uses a historical currency value, converting it at today’s exchange rate may destroy the intended comparison. Preserve the problem’s logic, explain unfamiliar conventions and verify that the marked answer remains correct.
Dates, calendars and school-year assumptions
An imported course can contain release dates, historical dates, term labels and deadlines. These are not one category. A historical date belongs to the subject matter. A deadline belongs to course operation. A term label may refer to a local institutional calendar. Translating ‘autumn term’ to the name of a different country’s school period can imply equivalence where none exists, while converting a live due date without its timezone can make submissions late.
Document which values are fixed educational facts and which require configuration by the destination institution. A translated syllabus may explain source terms in parentheses rather than asserting a new term schedule. The receiving administrator should set operational dates in the LMS, using the learner’s timezone rules where appropriate. Avoid hiding live course configuration inside a general language translation; it is a deployment decision that needs its own review.
Worked case: a primary science cartridge
Imagine a source course containing three units: classify materials, test dissolving and explain results. The target school uses different year labels but teaches similar ideas in a different order. A weak localization changes the source year label to a familiar local year, translates every menu, and announces full curriculum alignment. The teacher then discovers that the students have not yet learned a key prerequisite required in unit two.
A better version preserves the original educational level, describes the observed content and places any local suitability advice in a separately reviewed note. It translates student instructions and visual captions, tests the embedded experiment worksheet and checks whether the assessment still measures the intended concepts. The outcome may be an excellent supplemental resource without a claim of formal alignment. That is a successful international learning decision, not a failure of translation.
Worked case: a language-learning cartridge
A vocabulary lesson may use deliberately untranslated phrases, minimal pairs or pronunciation contrasts. A translator hired to make the interface available in another language must identify which words are explanations and which words are the objects being studied. Replacing every foreign-language example with a target-language sentence can defeat a task designed to notice a sound or grammatical feature. The problem is not one of fluency; it is one of instructional purpose.
Define the teaching language, learner support language and examples as separate fields in the plan. Translate help instructions, navigation and explanations while preserving the linguistic data students must observe. Where examples do need adaptation, have a language teacher re-evaluate the outcome and distractors. The course can offer Spanish interface support for an English pronunciation lesson without claiming that the lesson itself has become a Spanish pronunciation course.
Worked case: an external simulation
A physics cartridge links to an interactive pendulum tool. The source menu promises that students will compare period and length under a controlled setting. The local team finds an unrelated simulation with a similar translated title and swaps the URL because the original lacks a translated interface. The new tool uses different default units and provides no equivalent task controls. Students complete a different experiment even though the course navigation still looks familiar.
The right decision is to retain the intended resource identity until an approved alternative has been evaluated. Translate the surrounding instructions, ask the provider about supported languages and provide an honest accessibility or language note where needed. If an alternative simulation is chosen, treat the move as curriculum adaptation, recheck the questions and update resource and licensing records. Do not disguise a substantive substitution as a text-only translation.
Worked case: a multiple-choice mathematics test
A mathematics item asks which representation does not satisfy an equation. In the target language a negative construction sounds clumsy, so an editor removes the negative and converts the question into asking which one does satisfy it. The options are preserved; the keyed response is not. The import succeeds, and only a test attempt reveals the contradiction between the new stem and scoring rule.
The correction must restore the negative logical demand or deliberately redesign the item with an updated key and subject review. Check response identifiers, feedback messages and rubric interpretation in the actual imported assessment. A bilingual reviewer should answer each item independently before seeing the official key, because that tests the target question as a learner experiences it. XML validity alone cannot detect a semantically inverted question.
An import-and-export acceptance test
A successful localization requires more than a file that decompresses. First import the original cartridge into a known test course and record its visible units, item counts and functional tools. Then import the localized package into an equivalent test environment. Compare navigation labels, resource counts, media availability, external launches, assessment attempts, learner and teacher roles, accessibility controls and course metadata. Keep the original comparison available so unexpected behavior has a baseline.
If the environment supports export after import, inspect whether the resulting resources and relationships remain meaningful. An LMS might convert a source activity into an internal object rather than preserving the original package bytes, so byte-for-byte equality is not always the right acceptance criterion. Test functional equivalence: can the learner perform the same intended learning task, receive the same kind of feedback and reach the same resource? Record exceptions rather than claiming blanket success.
How to handle platform differences honestly
Two products can support Common Cartridge and still differ in which optional resource types, version profiles or display behaviors they implement. Some importers may ignore unsupported metadata, while others convert it into text or fail a particular resource. Translators should not be asked to solve these differences merely by shortening labels. A missing assessment or misplaced navigation link is an interoperability issue to diagnose with the platform and content supplier.
Keep a compatibility matrix with the exact importer version, accepted cartridge profile, tested resource types and known limitations. If a target LMS cannot preserve a supported interaction, make the adaptation explicit and submit it for instructional approval. Do not silently turn a scored quiz into an unscored reading page, or a teacher-only guide into a learner handout. Transparency prevents technical compatibility work from becoming an undocumented curriculum rewrite.
Publishing, revisions and version identity
A localized course can receive corrections long after the initial import. Its source edition may also change. Treat these as distinguishable events: a typographical correction in a target-language caption is not the same as a new source edition with changed assessment criteria. A shared course title does not establish that two imports contain the same version. Teachers need enough information to decide whether to replace, supplement or retain an existing course.
Record source and target edition references, affected resource identifiers, important adaptations and review dates. If an instructor has already assigned the course, changing the underlying content can alter the learner’s experience mid-unit. Plan updates around active cohorts and institutional policy. The correct translation workflow keeps a history intelligible to teachers without exposing students to unreviewed changes or producing several indistinguishable copies in the LMS.
A practical acceptance decision
Before approving a multilingual cartridge, ask five questions. Does the package import into the intended platform? Do all controlled references and links still work? Are student-facing directions and the content of learning tasks faithful? Are assessment answers, grades and access roles protected? Do metadata and curriculum statements describe the actual resource rather than an assumed local equivalent? Each question has an identifiable reviewer and a demonstrable test.
Approval can be conditional. A cartridge might be sound for teacher-led supplementary lessons yet not suitable for automatic assessment, or its translated menu might work while third-party tools remain available in one language only. State those limits in plain language. A professional outcome is not always an unconditional green light. It is a defensible decision that helps a real institution understand what is safe to deploy and what further work is necessary.
How to decide what to translate first
If an institution has limited resources, prioritize high-consequence learner interactions before decorative interface details. Start with safety instructions, assessment prompts, submission controls and access guidance. Continue with lesson explanations, captions, teacher directions and discovery descriptions. Labels that affect navigation should be reviewed early enough for realistic import testing. A translated marketing description alone does not make a course usable; users still need to understand the tasks inside.
Do not postpone technical triage until every sentence is translated. A broken resource reference can invalidate a large body of completed work. Run a small bilingual import early, including one embedded media object, one external link, one assessment and a teacher-only instruction. The early result will reveal whether the chosen platform preserves language metadata, file paths and role visibility. This allows writing effort to concentrate on material the receiving system can actually deliver.
Managing changes to embedded media
Images sometimes contain meaningful written labels, and videos may rely on burned-in text that cannot be changed by editing captions. Identify those assets before writing the final translation. For a graph, the correct choice may be to recreate an accessible target-language graphic while keeping all measured points, axes, units and relationships intact. For a video, a localized caption track can sometimes meet the teaching need without changing the original recording.
Mark media adaptations as genuine derivatives, preserve source attribution and verify dimensions or timestamps that participate in an assessment. A physics problem whose key depends on the arrow direction in a diagram cannot accept a newly drawn arrow pointing the other way. Similarly, a transcript that paraphrases a measured result may teach the wrong scientific claim. Review high-information media with both a language specialist and a subject reviewer.
A readable bilingual review worksheet
A strong review worksheet links each target-language item to an understandable source location. It includes the displayed source text, intended user role, resource context, proposed translation, terminology decision, educational risk and validation result. This does not require a complicated system; a well-designed table can be enough for a small course. The essential feature is traceability from a reader-visible phrase to the actual lesson or assessment where it occurs.
Use that worksheet to distinguish a translation correction from a platform correction or curriculum adaptation. For example, changing an ambiguous instruction may be a language fix. Replacing a unavailable simulation is a learning-design decision. Altering a scoring rule is an assessment decision. If all three are placed under the word ‘translation’, reviewers may approve work beyond their expertise. Clear responsibility improves accuracy and makes later updates less expensive.
Frequently asked questions
Is a translated Common Cartridge automatically certified?
No. A translated package can be well written and still fail a required import or conformance test. Certification applies to specified implementations and profiles, not to the literary quality of course content. Test the actual package and importing platform against their supported specifications.
Should filenames be translated?
Not simply because they contain English. A filename may be part of a technical reference or a preserved source artifact. Translate display metadata where possible; when physical renaming is necessary, update every dependent reference and verify it in the target environment.
Is Thin Common Cartridge an offline format?
A thin cartridge principally carries structured links to outside resources. Imported navigation does not guarantee that the referenced learning tools and content can work offline. Explain that dependency to teachers and learners.
Can an imported course be aligned to another national syllabus?
Only after an appropriate curriculum review. Shared topic names or similar grade numbers do not prove equal prerequisites, cognitive demand or assessment requirements. Preserve the original alignment and label local comparisons accurately.
Does a valid QTI file guarantee equivalent assessment?
No. Machine validation can protect structure and processing, but translated wording may change difficulty, logic or what a candidate understands. Subject and assessment review remain essential.
Does the translator need to change LTI launch parameters?
Ordinary language localization should not modify security claims, deployment identifiers or launch URLs. Arrange supported language or content variants with the tool provider and the LMS administrator instead.
How many test imports are enough?
At minimum test the original and localized packages in comparable environments. Cover every resource type actually used and the roles that will access it. High-stakes assessments and complex third-party links warrant more extensive checks.
What should an institution publish about limitations?
State incomplete language coverage, unverified curricular alignments, unavailable third-party resources, accessibility gaps and known importer limitations. Such disclosures protect learner expectations and allow teachers to choose suitable materials.
Official references and connected reading
The definitive starting points are the 1EdTech Common Cartridge standards page and the Common Cartridge 1.4 implementation material. For adjacent but different questions, consult eduKateSG’s LRMI metadata guide for educational discovery claims and the ITS 2.0 guide for translating content-bearing XML and HTML. The job of this article is to keep an entire transferable course package usable across language and LMS boundaries.