To translate JSON Feed 1.1 syndication feeds correctly, begin by separating human-readable language from the structured values that identify, route or validate the record. This guide answers the practical question: how to localize JSON Feed 1.1 article items, summaries, languages and enclosures without breaking subscribers. It is written for publishers, feed-reader developers, editors, translators and independent website maintainers, with original examples, a repeatable audit process and clear boundaries around what a translator may change.
The visible mistake is usually simple: An editor publishes a translated JSON feed and also translates each item’s `id` and attachment URL. A feed reader then treats previously seen posts as new, links to media that does not exist, and mixes two languages under an unchanged language tag. The words are translated, but the subscription experience is broken. A correct translation must let an ordinary reader understand the record and let the receiving system behave as intended. The standard is not stylistic similarity alone; feed subscribers receive accurate translated text for the same items and attachments without duplicate IDs, broken URLs or invented media properties. Start by classifying each piece of information before typing a target-language equivalent.
Quick reference: Translate explanatory prose where permitted; protect identifiers, references, technical tokens and factual conditions; work from the specification rather than intuition; maintain a field-level change log; check original and translated renderings together; run structural checks; use real-world reader tasks as final proof. The following sections explain each action through JSON Feed 1.1 syndication feeds, rather than offering generic translation advice.
The precise translation problem and the limits of this guide
JSON Feed is a JSON-based syndication format with feed-level properties and an `items` array. In version 1.1, an item has a stable `id`, optional titles and summaries, content expressed as `content_text` and/or `content_html`, and may include authors, language and attachments. The translation decision must separate prose readers should see from identifiers and structural values that applications depend on.
This article explains JSON Feed 1.1 internationalization and localization. It does not prescribe a single approach to bilingual publishing: a site can create distinct feed URLs for languages or intentionally mix item languages, but whichever strategy it chooses must be documented and consistent.
A file can be syntactically correct while carrying the wrong meaning, and a fluent translation can be syntactically invalid. For JSON Feed 1.1 syndication feeds, both kinds of failure must be found before publication. In practical work, record which values are display language, which are authoritative identity, which are program instructions and which are evidence or measurements. A reviewer should be able to defend every change in those terms.
First principles: the three layers that must remain distinct
Layer 1: the record that machines interpret
A structured record is not a continuous paragraph. It is a collection of named fields with defined relationships. Keys, identifiers and field types often use English-looking words, but their appearance does not make them phrases for translation. A program does not understand a localized synonym for a protocol key unless the format explicitly defines such a mechanism. Keep the original machine layer reproducible and testable.
The first diagnostic is to point to every changed character and ask whether the change is expected by the schema. If it is not, a human-readable explanation may belong in a label or documentation field instead. This distinction prevents attractive but destructive edits from passing a casual proofreading review. A useful exercise is to highlight every token that must remain byte-for-byte identical before translating the first sentence.
Layer 2: the statement a person will read
Human-facing titles, instructions, summaries, notices and descriptions are evaluated by what a reader can accurately recover. Translation should keep who did what, when, why and under what conditions. Where a sentence signals possibility, limitation or responsibility, preserve those limits. A fluent rewrite which implies a stronger permission, a completed action or a certified capability does not satisfy the source, even if it sounds elegant.
Read a candidate translation aloud as a decision instruction. Would a user make the same choice after seeing the target-language version? Could they identify the same author, object, service, field or publication? If not, the translation is not ready. In structured information, tiny words such as may, expected, only, optional, duplicate and experimental often carry disproportionate practical significance.
Layer 3: the evidence that lets another person verify it
The most reliable review combines a source snapshot, a field-by-field translation decision and a rendered output. That is stronger than comparing prose alone because the source may contain facts that the interface hides. Evidence includes actual links, identifiers, dates, numeric values and the documented meaning of status or type fields. A reviewer must distinguish what the record explicitly says from an editorial inference.
A defensible translation has an audit trail. Keep one entry for every disputed expression: original value, proposed target form, reason, authoritative reference and reviewer decision. When someone later asks why a field stayed in English or why a particular status was qualified, that record gives a precise answer. Such notes are especially important when different teams maintain the source record and its translated display.
Field-by-field guide: what to translate, what to protect
`version`
`version` represents exact format URL identifying the feed specification. The safe translation decision is to preserve the specified version URL exactly. The corresponding boundary is that a localized URL string may stop clients recognizing the format. For example, `https://jsonfeed.org/version/1.1` is a protocol value. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`title` at feed level
`title` at feed level represents human-readable name of the feed. The safe translation decision is to translate a descriptive title when a localized edition is intended. The corresponding boundary is that do not change the publisher’s identity or mislabel language coverage. For example, `Community Science Updates` can have a natural localized display title. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`home_page_url`
`home_page_url` represents publisher’s main site URL. The safe translation decision is to retain or replace only with a confirmed real localized homepage. The corresponding boundary is that translating path characters without a working destination breaks navigation. For example, the publisher must own a tested target URL. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`feed_url`
`feed_url` represents where the feed is served. The safe translation decision is to preserve if unchanged or set to an actual new locale feed endpoint. The corresponding boundary is that cannot point a translated feed at the wrong source URL. For example, each locale feed can have a stable distinct address. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`description`
`description` represents optional prose summary of the feed. The safe translation decision is to translate purpose and editorial scope. The corresponding boundary is that do not imply every post is bilingual when only some are. For example, `Updates about open-source water data` remains scope-limited. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`language` at feed level
`language` at feed level represents optional primary language tag in RFC 5646 format. The safe translation decision is to use the correct tag for the feed’s primary language. The corresponding boundary is that never translate tag tokens into full language names inside JSON. For example, `en` and `fr` are code values. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`items`
`items` represents required array holding individual feed items. The safe translation decision is to preserve list structure and understand whether items are translated editions or shared originals. The corresponding boundary is that duplicating items or changing IDs alters reader behavior. For example, a feed with zero items still includes an items array. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`id`
`id` represents required item identifier stable across later updates. The safe translation decision is to keep stable for the same item over time. The corresponding boundary is that changing id on ordinary translation update can create apparent new posts. For example, an absolute URL is a common reliable identifier. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`url`
`url` represents permalink to the item’s hosted resource. The safe translation decision is to use a tested localized permalink only when it exists. The corresponding boundary is that an editor must not fabricate URL slugs by translation alone. For example, a localized landing page can be linked intentionally. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`external_url`
`external_url` represents optional link to a separate object an item discusses. The safe translation decision is to retain the true external destination. The corresponding boundary is that do not confuse it with the feed item’s own permalink. For example, a linkblog can point to a research paper here. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`content_text`
`content_text` represents plain-text content of the item. The safe translation decision is to translate content as plain text and preserve meaning. The corresponding boundary is that do not introduce HTML markup into a plain-text property. For example, simple paragraphs remain text. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`content_html`
`content_html` represents HTML content of the item. The safe translation decision is to translate visible prose while preserving safe markup and anchors. The corresponding boundary is that HTML belongs in this designated field, not in ordinary plain-text fields. For example, a link’s displayed phrase may change while href remains valid. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`summary`
`summary` represents short human-readable description of an item. The safe translation decision is to translate as an honest summary. The corresponding boundary is that do not replace the item with claims the full article does not make. For example, a summary is not the full text. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`authors`
`authors` represents array of named credited creators at feed or item level. The safe translation decision is to preserve names and verified identities and apply feed/item fallback deliberately. The corresponding boundary is that never change contributor attribution to fit translated copy. For example, item-level authors may override the default feed authors. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`date_published` and `date_modified`
`date_published` and `date_modified` represents RFC 3339 timestamps for publication and edits. The safe translation decision is to preserve facts and format in the feed. The corresponding boundary is that translation alone must not reset publish date or duplicate an updated item. For example, a modified timestamp reflects a real modification. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`tags`
`tags` represents optional array of plain text tags. The safe translation decision is to translate categories only under the publisher’s discovery policy. The corresponding boundary is that do not assume JSON Feed tags are hashtags or alter taxonomy silently. For example, a localized label can be useful without breaking editorial links. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`attachments`
`attachments` represents item resources such as audio or video files. The safe translation decision is to translate media-facing titles when appropriate. The corresponding boundary is that preserve attachment identities and required technical members. For example, an audio enclosure still points to the original file until a localized one exists. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`mime_type`
`mime_type` represents required media type for an attachment. The safe translation decision is to preserve exact MIME token. The corresponding boundary is that an incorrect media type can prevent proper playback or handling. For example, `audio/mpeg` stays literal. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`size_in_bytes` and `duration_in_seconds`
`size_in_bytes` and `duration_in_seconds` represents optional numeric attachment measurements. The safe translation decision is to preserve true numbers; update only when the attached file genuinely changes. The corresponding boundary is that a translated title does not change file size or duration. For example, do not turn seconds into minutes in the numeric field. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
`expired` and `hubs`
`expired` and `hubs` represents feed completion flag and optional real-time notification endpoints. The safe translation decision is to preserve booleans and working notification URLs. The corresponding boundary is that a translation is not a reason to mark a feed expired or invent a hub. For example, `expired: true` means the feed is finished. A good reviewer verifies this field both in isolation and in the whole record, because a locally plausible edit may change a link, a data relationship or a reader’s inference elsewhere.
Ask two separate questions here: does the value obey its structural contract, and does any visible text convey the correct human meaning? If the first answer is no, restore the source identifier or rule before editing prose. If the second answer is no, revise the explanatory language without silently rewriting the authoritative data. This discipline makes corrections traceable rather than a succession of guesses.
A repeatable twelve-stage translation and publication method
1. Identify the reader and the use case
Write down the audience, the task they want to complete and the language in which they will act. A support dashboard, academic citation and feed reader ask different things of the same phrase. In JSON Feed 1.1 syndication feeds, the practical focus at this stage is exact format URL identifying the feed specification. It is tempting to move quickly because the field appears familiar, yet the safer decision is to preserve the specified version URL exactly. Keep that rule in the working checklist so another translator can repeat it rather than relying on the first editor’s memory.
Test the decision against a concrete situation: feed language: en; item rewritten entirely in French. The review should not accidentally produce this alternative: Keep en and assume readers infer the language. Instead, Set a correct item language tag if a mixed-language feed is intentional, or publish a coherent French feed policy. Record the source value, the reason for the edit and the structural check that proves the intended behavior survived. If the reasoning cannot be explained in one or two clear sentences, escalate the ambiguity before publication.
2. Fix the canonical source version
Record the version, source URL and responsible owner before editing. Translation of an unstable or unapproved snapshot creates review problems when the upstream record changes. In JSON Feed 1.1 syndication feeds, the practical focus at this stage is where the feed is served. It is tempting to move quickly because the field appears familiar, yet the safer decision is to preserve if unchanged or set to an actual new locale feed endpoint. Keep that rule in the working checklist so another translator can repeat it rather than relying on the first editor’s memory.
Test the decision against a concrete situation: id: https://example.org/posts/42 The review should not accidentally produce this alternative: Translate the digits or change the ID each time the sentence is revised. Instead, Keep the same identifier for the same item and update modification information appropriately. Record the source value, the reason for the edit and the structural check that proves the intended behavior survived. If the reasoning cannot be explained in one or two clear sentences, escalate the ambiguity before publication.
3. Inventory all fields before translating
Extract keys and values into a field inventory. Mark reader-facing sentences, schema tokens, codes, names, measurements, references and absent fields separately. In JSON Feed 1.1 syndication feeds, the practical focus at this stage is required array holding individual feed items. It is tempting to move quickly because the field appears familiar, yet the safer decision is to preserve list structure and understand whether items are translated editions or shared originals. Keep that rule in the working checklist so another translator can repeat it rather than relying on the first editor’s memory.
Test the decision against a concrete situation: summary: This article compares three possible survey methods. The review should not accidentally produce this alternative: Translate it as proven best method for every city. Instead, Retain that the item compares methods and does not reach a universal verdict. Record the source value, the reason for the edit and the structural check that proves the intended behavior survived. If the reasoning cannot be explained in one or two clear sentences, escalate the ambiguity before publication.
4. Fence the protected data
Mark anything that must not change without a separately approved data migration. Identifiers, links, timestamps and validation tokens commonly belong here. In JSON Feed 1.1 syndication feeds, the practical focus at this stage is optional link to a separate object an item discusses. It is tempting to move quickly because the field appears familiar, yet the safer decision is to retain the true external destination. Keep that rule in the working checklist so another translator can repeat it rather than relying on the first editor’s memory.
Test the decision against a concrete situation: content_html: <p>Read <a href="https://example.org/help">the instructions</a>.</p> The review should not accidentally produce this alternative: Translate HTML tag names and alter the href to a made-up URL. Instead, Translate the visible phrase while preserving functioning markup and target address. Record the source value, the reason for the edit and the structural check that proves the intended behavior survived. If the reasoning cannot be explained in one or two clear sentences, escalate the ambiguity before publication.
5. Define language and terminology policy
Select an appropriate target variety, preferred equivalents and a rule for official names. A glossary supports consistency without turning every borrowed term into literal prose. In JSON Feed 1.1 syndication feeds, the practical focus at this stage is short human-readable description of an item. It is tempting to move quickly because the field appears familiar, yet the safer decision is to translate as an honest summary. Keep that rule in the working checklist so another translator can repeat it rather than relying on the first editor’s memory.
Test the decision against a concrete situation: attachment mime_type: audio/mpeg; title: Episode 4 interview The review should not accidentally produce this alternative: Translate mime_type into a localized phrase such as audio/mp3 en français. Instead, Keep mime_type literal while translating the friendly attachment title. Record the source value, the reason for the edit and the structural check that proves the intended behavior survived. If the reasoning cannot be explained in one or two clear sentences, escalate the ambiguity before publication.
6. Translate meaning with its conditions intact
Render each human-readable statement while preserving uncertainty, agency, negation, scope, time and technical qualifications. Test what the reader will infer. In JSON Feed 1.1 syndication feeds, the practical focus at this stage is optional array of plain text tags. It is tempting to move quickly because the field appears familiar, yet the safer decision is to translate categories only under the publisher’s discovery policy. Keep that rule in the working checklist so another translator can repeat it rather than relying on the first editor’s memory.
Test the decision against a concrete situation: duration_in_seconds: 1854; size_in_bytes: 19000000 The review should not accidentally produce this alternative: Convert 1854 into 30.9 without changing the property name. Instead, Preserve measurements in their required units; show minutes separately in the interface. Record the source value, the reason for the edit and the structural check that proves the intended behavior survived. If the reasoning cannot be explained in one or two clear sentences, escalate the ambiguity before publication.
7. Resolve ambiguous terms against the schema
When a phrase seems ordinary but its field has a specialized meaning, return to the specification and example records instead of trusting intuition. In JSON Feed 1.1 syndication feeds, the practical focus at this stage is optional numeric attachment measurements. It is tempting to move quickly because the field appears familiar, yet the safer decision is to preserve true numbers; update only when the attached file genuinely changes. Keep that rule in the working checklist so another translator can repeat it rather than relying on the first editor’s memory.
Test the decision against a concrete situation: authors: [{name: Ana Martín}] The review should not accidentally produce this alternative: Strip diacritics and replace the author with translated first and family names. Instead, Keep the credited name as supplied by the author or publisher. Record the source value, the reason for the edit and the structural check that proves the intended behavior survived. If the reasoning cannot be explained in one or two clear sentences, escalate the ambiguity before publication.
8. Preserve the document structure
Maintain required keys, nesting, data types, array shapes and references. Formatting and quoting changes are reviewed like code changes, not typography. In JSON Feed 1.1 syndication feeds, the practical focus at this stage is human-readable name of the feed. It is tempting to move quickly because the field appears familiar, yet the safer decision is to translate a descriptive title when a localized edition is intended. Keep that rule in the working checklist so another translator can repeat it rather than relying on the first editor’s memory.
Test the decision against a concrete situation: url points to publisher commentary; external_url points to a published study. The review should not accidentally produce this alternative: Replace both links with the study, losing the publisher commentary page. Instead, Preserve distinction between post permalink and referenced external object. Record the source value, the reason for the edit and the structural check that proves the intended behavior survived. If the reasoning cannot be explained in one or two clear sentences, escalate the ambiguity before publication.
9. Compare field-level before and after states
Use a structured diff. A reviewer should see exactly which human-readable values changed and which protected values stayed identical. In JSON Feed 1.1 syndication feeds, the practical focus at this stage is optional prose summary of the feed. It is tempting to move quickly because the field appears familiar, yet the safer decision is to translate purpose and editorial scope. Keep that rule in the working checklist so another translator can repeat it rather than relying on the first editor’s memory.
Test the decision against a concrete situation: attachments points to original English audio. The review should not accidentally produce this alternative: Translate the attachment title and claim that the audio language has changed. Instead, Keep honest language labeling; create a verified new attachment only when localized audio actually exists. Record the source value, the reason for the edit and the structural check that proves the intended behavior survived. If the reasoning cannot be explained in one or two clear sentences, escalate the ambiguity before publication.
10. Validate machine readability
Parse or validate the target record using the tools appropriate to the format. A file that cannot be consumed is not a successful translation artifact. In JSON Feed 1.1 syndication feeds, the practical focus at this stage is required item identifier stable across later updates. It is tempting to move quickly because the field appears familiar, yet the safer decision is to keep stable for the same item over time. Keep that rule in the working checklist so another translator can repeat it rather than relying on the first editor’s memory.
Test the decision against a concrete situation: authors is supported; legacy author may also appear for compatibility. The review should not accidentally produce this alternative: Remove authors and keep only author because the translator is used to singular grammar. Instead, Preserve the format’s precedence: prefer authors in readers when both appear. Record the source value, the reason for the edit and the structural check that proves the intended behavior survived. If the reasoning cannot be explained in one or two clear sentences, escalate the ambiguity before publication.
11. Test a real user journey
Open the translated object in a relevant reader or application. Verify not just that text appears but that its actions, links, identity and interpretation remain correct. In JSON Feed 1.1 syndication feeds, the practical focus at this stage is plain-text content of the item. It is tempting to move quickly because the field appears familiar, yet the safer decision is to translate content as plain text and preserve meaning. Keep that rule in the working checklist so another translator can repeat it rather than relying on the first editor’s memory.
Test the decision against a concrete situation: feed language: en; item rewritten entirely in French. The review should not accidentally produce this alternative: Keep en and assume readers infer the language. Instead, Set a correct item language tag if a mixed-language feed is intentional, or publish a coherent French feed policy. Record the source value, the reason for the edit and the structural check that proves the intended behavior survived. If the reasoning cannot be explained in one or two clear sentences, escalate the ambiguity before publication.
12. Approve, publish and preserve a rollback
Obtain an editorial sign-off on nontrivial language decisions. Preserve the source and a reversible revision history for future corrections. In JSON Feed 1.1 syndication feeds, the practical focus at this stage is array of named credited creators at feed or item level. It is tempting to move quickly because the field appears familiar, yet the safer decision is to preserve names and verified identities and apply feed/item fallback deliberately. Keep that rule in the working checklist so another translator can repeat it rather than relying on the first editor’s memory.
Test the decision against a concrete situation: id: https://example.org/posts/42 The review should not accidentally produce this alternative: Translate the digits or change the ID each time the sentence is revised. Instead, Keep the same identifier for the same item and update modification information appropriately. Record the source value, the reason for the edit and the structural check that proves the intended behavior survived. If the reasoning cannot be explained in one or two clear sentences, escalate the ambiguity before publication.
Worked cases: how accurate translation changes the result
Worked case 1: Language tag and article translation
Source situation. feed language: en; item rewritten entirely in French. This is a deliberately simplified teaching example, not a live institutional record. The first job is to identify whether the statement is evidence, an instruction, a display label or machine data. That classification determines how far the translator can legitimately rewrite it.
Common wrong move. Keep en and assume readers infer the language. Such a rewrite may appear helpful to a reader who sees only the target text, but it crosses a boundary in the source. If a later reviewer compares real outcomes against the translated record, that unsupported change becomes a factual error rather than a matter of stylistic preference.
Correct move and reason. Set a correct item language tag if a mixed-language feed is intentional, or publish a coherent French feed policy. Language metadata is a promise about what a reader should expect. A translation that changes content but not language metadata can damage filtering, accessibility and discovery. The practical proof is to place the original and localized versions side by side, check the protected fields, then ask whether both versions support the same defensible decision. That last test catches subtle semantic drift that an automated parser cannot detect.
Worked case 2: Stable item across copy edit
Source situation. id: https://example.org/posts/42 This is a deliberately simplified teaching example, not a live institutional record. The first job is to identify whether the statement is evidence, an instruction, a display label or machine data. That classification determines how far the translator can legitimately rewrite it.
Common wrong move. Translate the digits or change the ID each time the sentence is revised. Such a rewrite may appear helpful to a reader who sees only the target text, but it crosses a boundary in the source. If a later reviewer compares real outcomes against the translated record, that unsupported change becomes a factual error rather than a matter of stylistic preference.
Correct move and reason. Keep the same identifier for the same item and update modification information appropriately. Subscription systems track item identity. Revision is not creation of a second article. The practical proof is to place the original and localized versions side by side, check the protected fields, then ask whether both versions support the same defensible decision. That last test catches subtle semantic drift that an automated parser cannot detect.
Worked case 3: A translated summary without an invented claim
Source situation. summary: This article compares three possible survey methods. This is a deliberately simplified teaching example, not a live institutional record. The first job is to identify whether the statement is evidence, an instruction, a display label or machine data. That classification determines how far the translator can legitimately rewrite it.
Common wrong move. Translate it as proven best method for every city. Such a rewrite may appear helpful to a reader who sees only the target text, but it crosses a boundary in the source. If a later reviewer compares real outcomes against the translated record, that unsupported change becomes a factual error rather than a matter of stylistic preference.
Correct move and reason. Retain that the item compares methods and does not reach a universal verdict. A summary is short, so each qualifier carries more weight. The reader may act on it before opening the article. The practical proof is to place the original and localized versions side by side, check the protected fields, then ask whether both versions support the same defensible decision. That last test catches subtle semantic drift that an automated parser cannot detect.
Worked case 4: HTML versus plain-text content
Source situation. content_html: <p>Read <a href="https://example.org/help">the instructions</a>.</p> This is a deliberately simplified teaching example, not a live institutional record. The first job is to identify whether the statement is evidence, an instruction, a display label or machine data. That classification determines how far the translator can legitimately rewrite it.
Common wrong move. Translate HTML tag names and alter the href to a made-up URL. Such a rewrite may appear helpful to a reader who sees only the target text, but it crosses a boundary in the source. If a later reviewer compares real outcomes against the translated record, that unsupported change becomes a factual error rather than a matter of stylistic preference.
Correct move and reason. Translate the visible phrase while preserving functioning markup and target address. The representation must still be valid HTML. Syntax does not become natural-language content because it appears inside quotation marks. The practical proof is to place the original and localized versions side by side, check the protected fields, then ask whether both versions support the same defensible decision. That last test catches subtle semantic drift that an automated parser cannot detect.
Worked case 5: Required media MIME type
Source situation. attachment mime_type: audio/mpeg; title: Episode 4 interview This is a deliberately simplified teaching example, not a live institutional record. The first job is to identify whether the statement is evidence, an instruction, a display label or machine data. That classification determines how far the translator can legitimately rewrite it.
Common wrong move. Translate mime_type into a localized phrase such as audio/mp3 en français. Such a rewrite may appear helpful to a reader who sees only the target text, but it crosses a boundary in the source. If a later reviewer compares real outcomes against the translated record, that unsupported change becomes a factual error rather than a matter of stylistic preference.
Correct move and reason. Keep mime_type literal while translating the friendly attachment title. Metadata tells clients how to handle bytes. An editorial label can change without changing media encoding. The practical proof is to place the original and localized versions side by side, check the protected fields, then ask whether both versions support the same defensible decision. That last test catches subtle semantic drift that an automated parser cannot detect.
Worked case 6: Duration and file size
Source situation. duration_in_seconds: 1854; size_in_bytes: 19000000 This is a deliberately simplified teaching example, not a live institutional record. The first job is to identify whether the statement is evidence, an instruction, a display label or machine data. That classification determines how far the translator can legitimately rewrite it.
Common wrong move. Convert 1854 into 30.9 without changing the property name. Such a rewrite may appear helpful to a reader who sees only the target text, but it crosses a boundary in the source. If a later reviewer compares real outcomes against the translated record, that unsupported change becomes a factual error rather than a matter of stylistic preference.
Correct move and reason. Preserve measurements in their required units; show minutes separately in the interface. Technical field names already encode units, so unit conversion must not be buried in a translation. The practical proof is to place the original and localized versions side by side, check the protected fields, then ask whether both versions support the same defensible decision. That last test catches subtle semantic drift that an automated parser cannot detect.
Worked case 7: A bilingual author’s name
Source situation. authors: [{name: Ana Martín}] This is a deliberately simplified teaching example, not a live institutional record. The first job is to identify whether the statement is evidence, an instruction, a display label or machine data. That classification determines how far the translator can legitimately rewrite it.
Common wrong move. Strip diacritics and replace the author with translated first and family names. Such a rewrite may appear helpful to a reader who sees only the target text, but it crosses a boundary in the source. If a later reviewer compares real outcomes against the translated record, that unsupported change becomes a factual error rather than a matter of stylistic preference.
Correct move and reason. Keep the credited name as supplied by the author or publisher. Translating surrounding editorial prose does not authorize a change of personal identity. The practical proof is to place the original and localized versions side by side, check the protected fields, then ask whether both versions support the same defensible decision. That last test catches subtle semantic drift that an automated parser cannot detect.
Worked case 8: A linkblog source reference
Source situation. url points to publisher commentary; external_url points to a published study. This is a deliberately simplified teaching example, not a live institutional record. The first job is to identify whether the statement is evidence, an instruction, a display label or machine data. That classification determines how far the translator can legitimately rewrite it.
Common wrong move. Replace both links with the study, losing the publisher commentary page. Such a rewrite may appear helpful to a reader who sees only the target text, but it crosses a boundary in the source. If a later reviewer compares real outcomes against the translated record, that unsupported change becomes a factual error rather than a matter of stylistic preference.
Correct move and reason. Preserve distinction between post permalink and referenced external object. A reader needs to know where a claim is discussed and where the underlying object lives. The two destinations serve different jobs. The practical proof is to place the original and localized versions side by side, check the protected fields, then ask whether both versions support the same defensible decision. That last test catches subtle semantic drift that an automated parser cannot detect.
Worked case 9: New localized audio file
Source situation. attachments points to original English audio. This is a deliberately simplified teaching example, not a live institutional record. The first job is to identify whether the statement is evidence, an instruction, a display label or machine data. That classification determines how far the translator can legitimately rewrite it.
Common wrong move. Translate the attachment title and claim that the audio language has changed. Such a rewrite may appear helpful to a reader who sees only the target text, but it crosses a boundary in the source. If a later reviewer compares real outcomes against the translated record, that unsupported change becomes a factual error rather than a matter of stylistic preference.
Correct move and reason. Keep honest language labeling; create a verified new attachment only when localized audio actually exists. A localized feed title is not evidence of a dubbed recording. Reviewers should listen to actual files. The practical proof is to place the original and localized versions side by side, check the protected fields, then ask whether both versions support the same defensible decision. That last test catches subtle semantic drift that an automated parser cannot detect.
Worked case 10: Version 1.1 author fields
Source situation. authors is supported; legacy author may also appear for compatibility. This is a deliberately simplified teaching example, not a live institutional record. The first job is to identify whether the statement is evidence, an instruction, a display label or machine data. That classification determines how far the translator can legitimately rewrite it.
Common wrong move. Remove authors and keep only author because the translator is used to singular grammar. Such a rewrite may appear helpful to a reader who sees only the target text, but it crosses a boundary in the source. If a later reviewer compares real outcomes against the translated record, that unsupported change becomes a factual error rather than a matter of stylistic preference.
Correct move and reason. Preserve the format’s precedence: prefer authors in readers when both appear. Schema evolution is not grammar. Version 1.1 supports the authors array and readers should prefer it when both forms are present. The practical proof is to place the original and localized versions side by side, check the protected fields, then ask whether both versions support the same defensible decision. That last test catches subtle semantic drift that an automated parser cannot detect.
Failure modes and how to diagnose them
Failure mode 1: Language tag and article translation
This failure arises when an editor treats `title` at feed level as though it were unrestricted prose or assumes that keep en and assume readers infer the language. The warning sign is a translated record that sounds clearer but can no longer support the original task. To diagnose it, locate the precise source claim, inspect whether the target added certainty or removed an essential condition, and identify the affected field or downstream link.
Repair it by returning to the recorded meaning: Set a correct item language tag if a mixed-language feed is intentional, or publish a coherent French feed policy. Then re-run both checks: does the structured object still parse and map to the same entities, and can a person using the target language make the same practical interpretation? Language metadata is a promise about what a reader should expect. A translation that changes content but not language metadata can damage filtering, accessibility and discovery. A resolved issue needs both forms of evidence, not an editor’s impression that the passage now reads more smoothly.
Failure mode 2: Stable item across copy edit
This failure arises when an editor treats `home_page_url` as though it were unrestricted prose or assumes that translate the digits or change the id each time the sentence is revised. The warning sign is a translated record that sounds clearer but can no longer support the original task. To diagnose it, locate the precise source claim, inspect whether the target added certainty or removed an essential condition, and identify the affected field or downstream link.
Repair it by returning to the recorded meaning: Keep the same identifier for the same item and update modification information appropriately. Then re-run both checks: does the structured object still parse and map to the same entities, and can a person using the target language make the same practical interpretation? Subscription systems track item identity. Revision is not creation of a second article. A resolved issue needs both forms of evidence, not an editor’s impression that the passage now reads more smoothly.
Failure mode 3: A translated summary without an invented claim
This failure arises when an editor treats `feed_url` as though it were unrestricted prose or assumes that translate it as proven best method for every city. The warning sign is a translated record that sounds clearer but can no longer support the original task. To diagnose it, locate the precise source claim, inspect whether the target added certainty or removed an essential condition, and identify the affected field or downstream link.
Repair it by returning to the recorded meaning: Retain that the item compares methods and does not reach a universal verdict. Then re-run both checks: does the structured object still parse and map to the same entities, and can a person using the target language make the same practical interpretation? A summary is short, so each qualifier carries more weight. The reader may act on it before opening the article. A resolved issue needs both forms of evidence, not an editor’s impression that the passage now reads more smoothly.
Failure mode 4: HTML versus plain-text content
This failure arises when an editor treats `description` as though it were unrestricted prose or assumes that translate html tag names and alter the href to a made-up url. The warning sign is a translated record that sounds clearer but can no longer support the original task. To diagnose it, locate the precise source claim, inspect whether the target added certainty or removed an essential condition, and identify the affected field or downstream link.
Repair it by returning to the recorded meaning: Translate the visible phrase while preserving functioning markup and target address. Then re-run both checks: does the structured object still parse and map to the same entities, and can a person using the target language make the same practical interpretation? The representation must still be valid HTML. Syntax does not become natural-language content because it appears inside quotation marks. A resolved issue needs both forms of evidence, not an editor’s impression that the passage now reads more smoothly.
Failure mode 5: Required media MIME type
This failure arises when an editor treats `language` at feed level as though it were unrestricted prose or assumes that translate mime_type into a localized phrase such as audio/mp3 en français. The warning sign is a translated record that sounds clearer but can no longer support the original task. To diagnose it, locate the precise source claim, inspect whether the target added certainty or removed an essential condition, and identify the affected field or downstream link.
Repair it by returning to the recorded meaning: Keep mime_type literal while translating the friendly attachment title. Then re-run both checks: does the structured object still parse and map to the same entities, and can a person using the target language make the same practical interpretation? Metadata tells clients how to handle bytes. An editorial label can change without changing media encoding. A resolved issue needs both forms of evidence, not an editor’s impression that the passage now reads more smoothly.
Failure mode 6: Duration and file size
This failure arises when an editor treats `items` as though it were unrestricted prose or assumes that convert 1854 into 30.9 without changing the property name. The warning sign is a translated record that sounds clearer but can no longer support the original task. To diagnose it, locate the precise source claim, inspect whether the target added certainty or removed an essential condition, and identify the affected field or downstream link.
Repair it by returning to the recorded meaning: Preserve measurements in their required units; show minutes separately in the interface. Then re-run both checks: does the structured object still parse and map to the same entities, and can a person using the target language make the same practical interpretation? Technical field names already encode units, so unit conversion must not be buried in a translation. A resolved issue needs both forms of evidence, not an editor’s impression that the passage now reads more smoothly.
Failure mode 7: A bilingual author’s name
This failure arises when an editor treats `id` as though it were unrestricted prose or assumes that strip diacritics and replace the author with translated first and family names. The warning sign is a translated record that sounds clearer but can no longer support the original task. To diagnose it, locate the precise source claim, inspect whether the target added certainty or removed an essential condition, and identify the affected field or downstream link.
Repair it by returning to the recorded meaning: Keep the credited name as supplied by the author or publisher. Then re-run both checks: does the structured object still parse and map to the same entities, and can a person using the target language make the same practical interpretation? Translating surrounding editorial prose does not authorize a change of personal identity. A resolved issue needs both forms of evidence, not an editor’s impression that the passage now reads more smoothly.
Failure mode 8: A linkblog source reference
This failure arises when an editor treats `url` as though it were unrestricted prose or assumes that replace both links with the study, losing the publisher commentary page. The warning sign is a translated record that sounds clearer but can no longer support the original task. To diagnose it, locate the precise source claim, inspect whether the target added certainty or removed an essential condition, and identify the affected field or downstream link.
Repair it by returning to the recorded meaning: Preserve distinction between post permalink and referenced external object. Then re-run both checks: does the structured object still parse and map to the same entities, and can a person using the target language make the same practical interpretation? A reader needs to know where a claim is discussed and where the underlying object lives. The two destinations serve different jobs. A resolved issue needs both forms of evidence, not an editor’s impression that the passage now reads more smoothly.
Failure mode 9: New localized audio file
This failure arises when an editor treats `external_url` as though it were unrestricted prose or assumes that translate the attachment title and claim that the audio language has changed. The warning sign is a translated record that sounds clearer but can no longer support the original task. To diagnose it, locate the precise source claim, inspect whether the target added certainty or removed an essential condition, and identify the affected field or downstream link.
Repair it by returning to the recorded meaning: Keep honest language labeling; create a verified new attachment only when localized audio actually exists. Then re-run both checks: does the structured object still parse and map to the same entities, and can a person using the target language make the same practical interpretation? A localized feed title is not evidence of a dubbed recording. Reviewers should listen to actual files. A resolved issue needs both forms of evidence, not an editor’s impression that the passage now reads more smoothly.
Practice and transfer: exercises with model reasoning
Exercise 1: audit language tag and article translation
Task. You receive this source cue: feed language: en; item rewritten entirely in French. A teammate proposes the following shortcut: Keep en and assume readers infer the language. Write a correction note that identifies the protected information, the meaning that must remain visible and one test that would catch an error. Use `home_page_url` as an additional cross-check in your answer.
Model reasoning. Set a correct item language tag if a mixed-language feed is intentional, or publish a coherent French feed policy. The reasoning is not merely that the original wording is preferable: Language metadata is a promise about what a reader should expect. A translation that changes content but not language metadata can damage filtering, accessibility and discovery. The additional check should ask whether publisher’s main site URL remains valid after localization. Where the field is absent or evidence is incomplete, the correct answer is to say what is unknown rather than supplying an attractive guess.
Exercise 2: audit stable item across copy edit
Task. You receive this source cue: id: https://example.org/posts/42 A teammate proposes the following shortcut: Translate the digits or change the ID each time the sentence is revised. Write a correction note that identifies the protected information, the meaning that must remain visible and one test that would catch an error. Use `feed_url` as an additional cross-check in your answer.
Model reasoning. Keep the same identifier for the same item and update modification information appropriately. The reasoning is not merely that the original wording is preferable: Subscription systems track item identity. Revision is not creation of a second article. The additional check should ask whether where the feed is served remains valid after localization. Where the field is absent or evidence is incomplete, the correct answer is to say what is unknown rather than supplying an attractive guess.
Exercise 3: audit a translated summary without an invented claim
Task. You receive this source cue: summary: This article compares three possible survey methods. A teammate proposes the following shortcut: Translate it as proven best method for every city. Write a correction note that identifies the protected information, the meaning that must remain visible and one test that would catch an error. Use `description` as an additional cross-check in your answer.
Model reasoning. Retain that the item compares methods and does not reach a universal verdict. The reasoning is not merely that the original wording is preferable: A summary is short, so each qualifier carries more weight. The reader may act on it before opening the article. The additional check should ask whether optional prose summary of the feed remains valid after localization. Where the field is absent or evidence is incomplete, the correct answer is to say what is unknown rather than supplying an attractive guess.
Exercise 4: audit html versus plain-text content
Task. You receive this source cue: content_html: <p>Read <a href="https://example.org/help">the instructions</a>.</p> A teammate proposes the following shortcut: Translate HTML tag names and alter the href to a made-up URL. Write a correction note that identifies the protected information, the meaning that must remain visible and one test that would catch an error. Use `language` at feed level as an additional cross-check in your answer.
Model reasoning. Translate the visible phrase while preserving functioning markup and target address. The reasoning is not merely that the original wording is preferable: The representation must still be valid HTML. Syntax does not become natural-language content because it appears inside quotation marks. The additional check should ask whether optional primary language tag in RFC 5646 format remains valid after localization. Where the field is absent or evidence is incomplete, the correct answer is to say what is unknown rather than supplying an attractive guess.
Exercise 5: audit required media mime type
Task. You receive this source cue: attachment mime_type: audio/mpeg; title: Episode 4 interview A teammate proposes the following shortcut: Translate mime_type into a localized phrase such as audio/mp3 en français. Write a correction note that identifies the protected information, the meaning that must remain visible and one test that would catch an error. Use `items` as an additional cross-check in your answer.
Model reasoning. Keep mime_type literal while translating the friendly attachment title. The reasoning is not merely that the original wording is preferable: Metadata tells clients how to handle bytes. An editorial label can change without changing media encoding. The additional check should ask whether required array holding individual feed items remains valid after localization. Where the field is absent or evidence is incomplete, the correct answer is to say what is unknown rather than supplying an attractive guess.
Exercise 6: audit duration and file size
Task. You receive this source cue: duration_in_seconds: 1854; size_in_bytes: 19000000 A teammate proposes the following shortcut: Convert 1854 into 30.9 without changing the property name. Write a correction note that identifies the protected information, the meaning that must remain visible and one test that would catch an error. Use `id` as an additional cross-check in your answer.
Model reasoning. Preserve measurements in their required units; show minutes separately in the interface. The reasoning is not merely that the original wording is preferable: Technical field names already encode units, so unit conversion must not be buried in a translation. The additional check should ask whether required item identifier stable across later updates remains valid after localization. Where the field is absent or evidence is incomplete, the correct answer is to say what is unknown rather than supplying an attractive guess.
Exercise 7: audit a bilingual author’s name
Task. You receive this source cue: authors: [{name: Ana Martín}] A teammate proposes the following shortcut: Strip diacritics and replace the author with translated first and family names. Write a correction note that identifies the protected information, the meaning that must remain visible and one test that would catch an error. Use `url` as an additional cross-check in your answer.
Model reasoning. Keep the credited name as supplied by the author or publisher. The reasoning is not merely that the original wording is preferable: Translating surrounding editorial prose does not authorize a change of personal identity. The additional check should ask whether permalink to the item’s hosted resource remains valid after localization. Where the field is absent or evidence is incomplete, the correct answer is to say what is unknown rather than supplying an attractive guess.
Exercise 8: audit a linkblog source reference
Task. You receive this source cue: url points to publisher commentary; external_url points to a published study. A teammate proposes the following shortcut: Replace both links with the study, losing the publisher commentary page. Write a correction note that identifies the protected information, the meaning that must remain visible and one test that would catch an error. Use `external_url` as an additional cross-check in your answer.
Model reasoning. Preserve distinction between post permalink and referenced external object. The reasoning is not merely that the original wording is preferable: A reader needs to know where a claim is discussed and where the underlying object lives. The two destinations serve different jobs. The additional check should ask whether optional link to a separate object an item discusses remains valid after localization. Where the field is absent or evidence is incomplete, the correct answer is to say what is unknown rather than supplying an attractive guess.
Exercise 9: audit new localized audio file
Task. You receive this source cue: attachments points to original English audio. A teammate proposes the following shortcut: Translate the attachment title and claim that the audio language has changed. Write a correction note that identifies the protected information, the meaning that must remain visible and one test that would catch an error. Use `content_text` as an additional cross-check in your answer.
Model reasoning. Keep honest language labeling; create a verified new attachment only when localized audio actually exists. The reasoning is not merely that the original wording is preferable: A localized feed title is not evidence of a dubbed recording. Reviewers should listen to actual files. The additional check should ask whether plain-text content of the item remains valid after localization. Where the field is absent or evidence is incomplete, the correct answer is to say what is unknown rather than supplying an attractive guess.
A compact quality-assurance checklist to use before releasing translations
- Can a reader identify the same object, action, condition and limit in both languages?
- Are all field names, keys and machine tokens still valid under the governing specification?
- Have IDs, URLs, numeric units, author or agency names, timestamps and reference relations been preserved or explicitly verified?
- Does the target-language UI clearly distinguish a documented fact from a possibility, example or estimate?
- Does the structured file parse and does a real reader/application behave correctly?
- Have examples and tests covered the edge cases rather than only the easy path?
- Is there a versioned source, diff, reviewer decision and rollback point?
Do not mark an item complete just because it passed a spell checker. The highest-risk translation mistakes frequently preserve perfect grammar while changing obligations, provenance, units or identity. Conversely, a machine validator may report no errors while a translated summary asserts something unsupported. Good publication control therefore assigns separate responsibility for linguistic accuracy and structural integrity.
Frequently asked questions
Does JSON Feed 1.1 require a language field?
No. The language field is optional, but accurate tags are valuable for multilingual feeds and individual items. For an actual release, confirm the specific record against its governing schema and authoritative publisher. When the same expression has both an ordinary-language and a technical meaning, make the difference explicit in the reviewer note. Correct translation is demonstrated by reproducible decisions, not confidence in a phrase alone.
What is the difference between `id` and `url`?
The id is the stable item identifier required by the format. The url is an optional resource permalink, often the same URL but serving a distinct role. For an actual release, confirm the specific record against its governing schema and authoritative publisher. When the same expression has both an ordinary-language and a technical meaning, make the difference explicit in the reviewer note. Correct translation is demonstrated by reproducible decisions, not confidence in a phrase alone.
Can the feed title change by language?
Yes when the publisher deliberately offers localized editions; maintain recognizable identity and stable confirmed endpoints. For an actual release, confirm the specific record against its governing schema and authoritative publisher. When the same expression has both an ordinary-language and a technical meaning, make the difference explicit in the reviewer note. Correct translation is demonstrated by reproducible decisions, not confidence in a phrase alone.
Should a translated post retain the original id?
If it is the same item updated in place, yes. A separately published localized edition may have a separate stable identity according to the publisher’s policy. For an actual release, confirm the specific record against its governing schema and authoritative publisher. When the same expression has both an ordinary-language and a technical meaning, make the difference explicit in the reviewer note. Correct translation is demonstrated by reproducible decisions, not confidence in a phrase alone.
Can HTML be placed in `content_text`?
That property is plain text. Put valid HTML in `content_html` and translate visible text while respecting markup. For an actual release, confirm the specific record against its governing schema and authoritative publisher. When the same expression has both an ordinary-language and a technical meaning, make the difference explicit in the reviewer note. Correct translation is demonstrated by reproducible decisions, not confidence in a phrase alone.
Can attachment titles be translated?
Yes, if they are readable labels. Keep the actual URL, MIME type and numeric measurements accurate. For an actual release, confirm the specific record against its governing schema and authoritative publisher. When the same expression has both an ordinary-language and a technical meaning, make the difference explicit in the reviewer note. Correct translation is demonstrated by reproducible decisions, not confidence in a phrase alone.
What if I update an article’s translation?
Preserve item identity and update date_modified when a real modification occurred; do not present an ordinary edit as a brand-new publication. For an actual release, confirm the specific record against its governing schema and authoritative publisher. When the same expression has both an ordinary-language and a technical meaning, make the difference explicit in the reviewer note. Correct translation is demonstrated by reproducible decisions, not confidence in a phrase alone.
Are JSON Feed tags the same as hashtags?
No. They are plain-text tagging values and are not necessarily social-media hashtags. For an actual release, confirm the specific record against its governing schema and authoritative publisher. When the same expression has both an ordinary-language and a technical meaning, make the difference explicit in the reviewer note. Correct translation is demonstrated by reproducible decisions, not confidence in a phrase alone.
Must author names be transliterated?
No. Use authoritative names and approved script alternatives. Attribution is not a free-text translation exercise. For an actual release, confirm the specific record against its governing schema and authoritative publisher. When the same expression has both an ordinary-language and a technical meaning, make the difference explicit in the reviewer note. Correct translation is demonstrated by reproducible decisions, not confidence in a phrase alone.
How do we validate the feed?
Parse the JSON, check required fields and language codes, test URLs and attachments, and observe how a real feed reader behaves on updates. For an actual release, confirm the specific record against its governing schema and authoritative publisher. When the same expression has both an ordinary-language and a technical meaning, make the difference explicit in the reviewer note. Correct translation is demonstrated by reproducible decisions, not confidence in a phrase alone.
What to read next and how to transfer this method
Use this guide when the problem is specifically how to localize JSON Feed 1.1 article items, summaries, languages and enclosures without breaking subscribers. For broader decisions about multilingual vocabulary, English meaning and schema-aware translation, choose the relevant adjacent owner rather than duplicating its coverage. Useful eduKateSG reading routes are listed below.
- Vocabulary Learning Hub
- How English Works
- Translation of terminology and glossaries
- W3C ITS 2.0 translation flags
- Dublin Core multilingual metadata
- SKOS multilingual labels
Authoritative technical references for this field include JSON Feed 1.1 authoritative specification and JSON Feed home and format overview. These references define the data contract; the original examples and teaching exercises above show how to apply that contract without turning translation into unreviewed data editing.
The transferable skill is straightforward: classify the source, protect what remains factual or machine-readable, translate what a person must understand, and verify the resulting action. A translator who can explain the boundary between those layers can apply the same reasoning to new records without assuming that all files or industries obey identical rules.