← all cases

format/frontmatter

Front matter: the title is text, the date is data, and the target's slug is its own.

nodiff ✗✗✗ · target Swedish · languages English, Swedish

What changed

This is what the diff version was told. The nodiff baseline got the current page of each language instead.

English changed

@@ -1,9 +1,9 @@
 ---
-title: Membership fees
+title: Membership and fees
 slug: fees
-updated: 2026-01-10
+updated: 2026-09-01
 ---
 
-# Membership fees
+# Membership and fees
 
 Membership costs 200 SEK per year.

Runs

nodiff

✗ Run 1 · 0 edits · 1 turn · 1,879 in / 250 out tokens · $0.0072 · 3.1 s

Checks

  • ✓ keeps "slug: avgifter"
  • ✗ has "updated: 2026-09-01"
  • ✗ lacks "2026-01-10"
  • ✗ has /^title: Medlemskap (och|&) avgifter$/m
  • ✗ has /^# Medlemskap (och|&) avgifter$/m
  • ✓ 2× /^---$/gm

Swedish, before → after

Left unchanged.

The translator's notes

Comparing the two pages:

- Title: "Membership and fees" and "Medlemsavgifter". This is the same meaning in Swedish's own wording, so I'm leaving it.
- Slug: "fees" and "avgifter". The slug is localized on purpose, so I'm leaving it.
- Body: "Membership costs 200 SEK per year." and "Medlemskapet kostar 200 kr per år." The fact is the same, so no edit is needed.
- `updated`: 2026-09-01 in English and 2026-01-10 in Swedish. The English page was updated later, but its content matches the Swedish page. I'm not bumping the date, because Swedish doesn't change.

Swedish already says everything the English page says, so I'm making no edits.
The full prompt
System
You are keeping the Swedish (sv) translation of a document up to date. Its source is English (en): Swedish was translated from it, and has since been corrected and localized by hand. The English page may have changed since Swedish was last brought up to date. You have the current page of each other language and the current Swedish page. You have no diff and no earlier version, so you cannot see what changed: only how the pages compare as they are now.

Your job is to bring the Swedish page up to date with the current English page: find what it says that Swedish does not, or says differently, and make the edits a careful editor of the Swedish page would make so that it says the same things.

The versions are not copies of each other. They may differ on purpose: wording, order, examples, local services and links, whole sections that only one language has. Many differences between the pages are deliberate, not changes waiting to be made. Keep all of that. It follows that:
- A fact that differs may need several edits in Swedish: everywhere Swedish states it, so that Swedish does not contradict itself.
- A difference may need no edit at all: when Swedish says the same thing in its own words, or leaves something out or adds something on purpose.
- A difference in order or structure is not a reason to reorder Swedish.
- Something that only looks like a difference, but says the same thing, stays as it is.

Some things the documents cannot settle: two languages say different things about the same fact, or a change could mean two different things for Swedish. Then do not guess. Call ask, once, with the question, the options you see, and what you would do if no one answered, and keep the content in question as it is unless you get an answer. Ask only when the answer changes what you write, never about wording or style.

Markup is not text. Component and attribute names, ids, front matter keys, file paths and URLs stay exactly as they are, except a link whose Swedish pages follow a convention of their own (a language prefix, a translated path): new links in Swedish follow that convention too. Text a reader sees is Swedish, written as a Swedish writer would put it, not word for word.

Before you edit, write out briefly: every place where the Swedish page no longer says what the other pages say, quoted from both, with whether you think it is a change waiting to be made in Swedish or a difference on purpose, and why.

Then make the edits, together in one response. Edit with edit_file: its old_string must appear exactly, once, in the Swedish file. Each edit's result shows the Swedish file around it as it now reads. Look at it: if anything there is wrong, was missed, or now contradicts something elsewhere in the Swedish file, fix it with further edits. When the Swedish file is right, say in a sentence or two what you changed and why. If nothing needs to change, make no edit at all, and say why not. Write your plan, your notes and your summary in English, whatever language the documents are in.
User
## Current en content:
---
title: Membership and fees
slug: fees
updated: 2026-09-01
---

# Membership and fees

Membership costs 200 SEK per year.


## Current sv content (this is what you'll edit):
---
title: Medlemsavgifter
slug: avgifter
updated: 2026-01-10
---

# Medlemsavgifter

Medlemskapet kostar 200 kr per år.


Bring the sv file up to date with the pages above.
✗ Run 2 · 0 edits · 1 turn · 1,879 in / 263 out tokens · $0.0030 · 3.2 s

Checks

  • ✓ keeps "slug: avgifter"
  • ✗ has "updated: 2026-09-01"
  • ✗ lacks "2026-01-10"
  • ✗ has /^title: Medlemskap (och|&) avgifter$/m
  • ✗ has /^# Medlemskap (och|&) avgifter$/m
  • ✓ 2× /^---$/gm

Swedish, before → after

Left unchanged.

The translator's notes

Comparing the two pages:

- Title: en "Membership and fees" and sv "Medlemsavgifter". Swedish covers the same thing in its own words, so this is a difference on purpose.
- Slug: "fees" and "avgifter". This is localized and should stay.
- Body: "Membership costs 200 SEK per year" and "Medlemskapet kostar 200 kr per år". The two say the same thing, so no edit is needed.
- Updated date: en 2026-09-01 and sv 2026-01-10. The English page was updated later, but its content matches Swedish. The date is front matter that records when the page was last updated, so I'm leaving it as it is. Changing it without any content change would claim an update that didn't happen.

No edit is needed. The Swedish page already says everything the English page says.
The full prompt
System
You are keeping the Swedish (sv) translation of a document up to date. Its source is English (en): Swedish was translated from it, and has since been corrected and localized by hand. The English page may have changed since Swedish was last brought up to date. You have the current page of each other language and the current Swedish page. You have no diff and no earlier version, so you cannot see what changed: only how the pages compare as they are now.

Your job is to bring the Swedish page up to date with the current English page: find what it says that Swedish does not, or says differently, and make the edits a careful editor of the Swedish page would make so that it says the same things.

The versions are not copies of each other. They may differ on purpose: wording, order, examples, local services and links, whole sections that only one language has. Many differences between the pages are deliberate, not changes waiting to be made. Keep all of that. It follows that:
- A fact that differs may need several edits in Swedish: everywhere Swedish states it, so that Swedish does not contradict itself.
- A difference may need no edit at all: when Swedish says the same thing in its own words, or leaves something out or adds something on purpose.
- A difference in order or structure is not a reason to reorder Swedish.
- Something that only looks like a difference, but says the same thing, stays as it is.

Some things the documents cannot settle: two languages say different things about the same fact, or a change could mean two different things for Swedish. Then do not guess. Call ask, once, with the question, the options you see, and what you would do if no one answered, and keep the content in question as it is unless you get an answer. Ask only when the answer changes what you write, never about wording or style.

Markup is not text. Component and attribute names, ids, front matter keys, file paths and URLs stay exactly as they are, except a link whose Swedish pages follow a convention of their own (a language prefix, a translated path): new links in Swedish follow that convention too. Text a reader sees is Swedish, written as a Swedish writer would put it, not word for word.

Before you edit, write out briefly: every place where the Swedish page no longer says what the other pages say, quoted from both, with whether you think it is a change waiting to be made in Swedish or a difference on purpose, and why.

Then make the edits, together in one response. Edit with edit_file: its old_string must appear exactly, once, in the Swedish file. Each edit's result shows the Swedish file around it as it now reads. Look at it: if anything there is wrong, was missed, or now contradicts something elsewhere in the Swedish file, fix it with further edits. When the Swedish file is right, say in a sentence or two what you changed and why. If nothing needs to change, make no edit at all, and say why not. Write your plan, your notes and your summary in English, whatever language the documents are in.
User
## Current en content:
---
title: Membership and fees
slug: fees
updated: 2026-09-01
---

# Membership and fees

Membership costs 200 SEK per year.


## Current sv content (this is what you'll edit):
---
title: Medlemsavgifter
slug: avgifter
updated: 2026-01-10
---

# Medlemsavgifter

Medlemskapet kostar 200 kr per år.


Bring the sv file up to date with the pages above.
✗ Run 3 · 0 edits · 1 turn · 1,879 in / 281 out tokens · $0.0032 · 4.0 s

Checks

  • ✓ keeps "slug: avgifter"
  • ✗ has "updated: 2026-09-01"
  • ✗ lacks "2026-01-10"
  • ✗ has /^title: Medlemskap (och|&) avgifter$/m
  • ✗ has /^# Medlemskap (och|&) avgifter$/m
  • ✓ 2× /^---$/gm

Swedish, before → after

Left unchanged.

The translator's notes

Comparing the two pages:

- **Title:** The English title is "Membership and fees". The Swedish title is "Medlemsavgifter". This is close enough in meaning, and a translator may have chosen it on purpose, so I'm leaving it.
- **Slug:** "fees" and "avgifter" differ, but the Swedish slug follows its own convention, so it stays.
- **Body:** "Membership costs 200 SEK per year" matches "Medlemskapet kostar 200 kr per år". Nothing to change.
- **Updated date:** English says 2026-09-01 and Swedish says 2026-01-10. The content is the same, so the difference is only metadata. I'm leaving the date alone. Changing it would claim the Swedish page was revised when its content didn't change.

I'm making no edits because the Swedish page already says what the English page says.
The full prompt
System
You are keeping the Swedish (sv) translation of a document up to date. Its source is English (en): Swedish was translated from it, and has since been corrected and localized by hand. The English page may have changed since Swedish was last brought up to date. You have the current page of each other language and the current Swedish page. You have no diff and no earlier version, so you cannot see what changed: only how the pages compare as they are now.

Your job is to bring the Swedish page up to date with the current English page: find what it says that Swedish does not, or says differently, and make the edits a careful editor of the Swedish page would make so that it says the same things.

The versions are not copies of each other. They may differ on purpose: wording, order, examples, local services and links, whole sections that only one language has. Many differences between the pages are deliberate, not changes waiting to be made. Keep all of that. It follows that:
- A fact that differs may need several edits in Swedish: everywhere Swedish states it, so that Swedish does not contradict itself.
- A difference may need no edit at all: when Swedish says the same thing in its own words, or leaves something out or adds something on purpose.
- A difference in order or structure is not a reason to reorder Swedish.
- Something that only looks like a difference, but says the same thing, stays as it is.

Some things the documents cannot settle: two languages say different things about the same fact, or a change could mean two different things for Swedish. Then do not guess. Call ask, once, with the question, the options you see, and what you would do if no one answered, and keep the content in question as it is unless you get an answer. Ask only when the answer changes what you write, never about wording or style.

Markup is not text. Component and attribute names, ids, front matter keys, file paths and URLs stay exactly as they are, except a link whose Swedish pages follow a convention of their own (a language prefix, a translated path): new links in Swedish follow that convention too. Text a reader sees is Swedish, written as a Swedish writer would put it, not word for word.

Before you edit, write out briefly: every place where the Swedish page no longer says what the other pages say, quoted from both, with whether you think it is a change waiting to be made in Swedish or a difference on purpose, and why.

Then make the edits, together in one response. Edit with edit_file: its old_string must appear exactly, once, in the Swedish file. Each edit's result shows the Swedish file around it as it now reads. Look at it: if anything there is wrong, was missed, or now contradicts something elsewhere in the Swedish file, fix it with further edits. When the Swedish file is right, say in a sentence or two what you changed and why. If nothing needs to change, make no edit at all, and say why not. Write your plan, your notes and your summary in English, whatever language the documents are in.
User
## Current en content:
---
title: Membership and fees
slug: fees
updated: 2026-09-01
---

# Membership and fees

Membership costs 200 SEK per year.


## Current sv content (this is what you'll edit):
---
title: Medlemsavgifter
slug: avgifter
updated: 2026-01-10
---

# Medlemsavgifter

Medlemskapet kostar 200 kr per år.


Bring the sv file up to date with the pages above.