← all cases

format/table-row

A row is added to a table.

hunks ✓✓✓ · diff ✓✓✓ · difflook ✓✓✓ · target Swedish · languages English, Swedish

What changed

English changed

@@ -4,3 +4,4 @@
 |-----|------|
 | Monday | 18–20 |
 | Wednesday | 18–20 |
+| Saturday | 9–12 |

Runs

hunks

✓ Run 1 · 1 edit · 2 turns · 4,130 in / 286 out tokens · $0.0088 · 3.7 s

Checks

  • ✓ has /^\| *Lördag *\| *9–12 *\|$/m
  • ✓ 5× /^\|/gm
  • ✓ in order: "Onsdag" → "Lördag"
  • ✓ changes only "| Onsdag"…"| Onsdag"

Swedish, before → after

@@ -4,3 +4,4 @@
 |-----|-----|
 | Måndag | 18–20 |
 | Onsdag | 18–20 |
+| Lördag | 9–12 |

The translator's notes

The English change adds a new schedule row, Saturday 9–12, probably because a new session was added. The Swedish file has the same table, with the Monday and Wednesday rows and no Saturday row. It needs one edit: add "Lördag | 9–12" after the Wednesday row. The time format "9–12" stays the same.I added a Saturday row, "Lördag | 9–12", to the Swedish schedule table. It matches the new row in English. Nothing else in the Swedish file mentions the schedule, so nothing else needed to change.

Tool calls

  1. edit_file: {"old_string":"| Onsdag | 18–20 |","new_string":"| Onsdag | 18–20 |\n| Lördag | 9–12 |"}
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions. The languages are equal peers; none is the original. Since Swedish was last brought up to date, someone changed English (en). For each language that changed, you have the content from when Swedish was last synced and a diff showing what changed since then.

Your job is not to translate the diff. It is to understand each change (what it says, and why it was likely made: a new fact, a correction, a rewording, a removal, a reordering) and then ask: if the person who made it had been editing the Swedish version instead, what would they have changed there? Make those changes.

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. Keep all of that, except where a change is about it. It follows that:
- One change may need several edits in Swedish: everywhere Swedish says what changed, also where the other language never said it, so that Swedish does not contradict itself.
- A change may need no edit at all: when Swedish does not have the content it is about, or already says what the change says.
- A change to order or structure applies only where Swedish follows that order or structure.
- Something that only looks like the changed content, but is about something else, 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: for each change, what it says and why it was likely made; then every place in the Swedish file that it concerns, quoted, with whether that place needs an edit and why. Places the other language never mentions count too.

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
## en content at time of last sync:
## Schedule

| Day | Time |
|-----|------|
| Monday | 18–20 |
| Wednesday | 18–20 |


## Changes made to en since then:
@@ -4,3 +4,4 @@
 |-----|------|
 | Monday | 18–20 |
 | Wednesday | 18–20 |
+| Saturday | 9–12 |

## Current sv content (this is what you'll edit):
## Schema

| Dag | Tid |
|-----|-----|
| Måndag | 18–20 |
| Onsdag | 18–20 |


Update the sv file.
✓ Run 2 · 1 edit · 2 turns · 4,094 in / 262 out tokens · $0.0041 · 3.5 s

Checks

  • ✓ has /^\| *Lördag *\| *9–12 *\|$/m
  • ✓ 5× /^\|/gm
  • ✓ in order: "Onsdag" → "Lördag"
  • ✓ changes only "| Onsdag"…"| Onsdag"

Swedish, before → after

@@ -4,3 +4,4 @@
 |-----|-----|
 | Måndag | 18–20 |
 | Onsdag | 18–20 |
+| Lördag | 9–12 |

The translator's notes

Change: English added a new schedule row, Saturday 9–12, probably because a new session was added. The Swedish table has the same structure and lacks that row, so it needs the row added: "Lördag | 9–12".I added a Saturday row, "Lördag | 9–12", to the Swedish schedule table. English had added the same session, and the Swedish table had no equivalent row. Nothing else in the Swedish file mentions the schedule, so no other edits were needed.

Tool calls

  1. edit_file: {"old_string":"| Onsdag | 18–20 |","new_string":"| Onsdag | 18–20 |\n| Lördag | 9–12 |"}
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions. The languages are equal peers; none is the original. Since Swedish was last brought up to date, someone changed English (en). For each language that changed, you have the content from when Swedish was last synced and a diff showing what changed since then.

Your job is not to translate the diff. It is to understand each change (what it says, and why it was likely made: a new fact, a correction, a rewording, a removal, a reordering) and then ask: if the person who made it had been editing the Swedish version instead, what would they have changed there? Make those changes.

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. Keep all of that, except where a change is about it. It follows that:
- One change may need several edits in Swedish: everywhere Swedish says what changed, also where the other language never said it, so that Swedish does not contradict itself.
- A change may need no edit at all: when Swedish does not have the content it is about, or already says what the change says.
- A change to order or structure applies only where Swedish follows that order or structure.
- Something that only looks like the changed content, but is about something else, 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: for each change, what it says and why it was likely made; then every place in the Swedish file that it concerns, quoted, with whether that place needs an edit and why. Places the other language never mentions count too.

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
## en content at time of last sync:
## Schedule

| Day | Time |
|-----|------|
| Monday | 18–20 |
| Wednesday | 18–20 |


## Changes made to en since then:
@@ -4,3 +4,4 @@
 |-----|------|
 | Monday | 18–20 |
 | Wednesday | 18–20 |
+| Saturday | 9–12 |

## Current sv content (this is what you'll edit):
## Schema

| Dag | Tid |
|-----|-----|
| Måndag | 18–20 |
| Onsdag | 18–20 |


Update the sv file.
✓ Run 3 · 1 edit · 2 turns · 4,113 in / 267 out tokens · $0.0042 · 3.6 s

Checks

  • ✓ has /^\| *Lördag *\| *9–12 *\|$/m
  • ✓ 5× /^\|/gm
  • ✓ in order: "Onsdag" → "Lördag"
  • ✓ changes only "| Onsdag"…"| Onsdag"

Swedish, before → after

@@ -4,3 +4,4 @@
 |-----|-----|
 | Måndag | 18–20 |
 | Onsdag | 18–20 |
+| Lördag | 9–12 |

The translator's notes

Change: English added a new schedule row, Saturday 9–12. It is a new fact, a third session. The Swedish table has the same two rows as the old English one and nothing else mentions the schedule. It needs one new row, "Lördag | 9–12", in Swedish.I added a Saturday row, "Lördag | 9–12", to the Swedish schedule table. It matches the new English row. Nothing else in the Swedish file refers to the schedule, so no other edits were needed.

Tool calls

  1. edit_file: {"old_string":"| Onsdag | 18–20 |","new_string":"| Onsdag | 18–20 |\n| Lördag | 9–12 |"}
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions. The languages are equal peers; none is the original. Since Swedish was last brought up to date, someone changed English (en). For each language that changed, you have the content from when Swedish was last synced and a diff showing what changed since then.

Your job is not to translate the diff. It is to understand each change (what it says, and why it was likely made: a new fact, a correction, a rewording, a removal, a reordering) and then ask: if the person who made it had been editing the Swedish version instead, what would they have changed there? Make those changes.

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. Keep all of that, except where a change is about it. It follows that:
- One change may need several edits in Swedish: everywhere Swedish says what changed, also where the other language never said it, so that Swedish does not contradict itself.
- A change may need no edit at all: when Swedish does not have the content it is about, or already says what the change says.
- A change to order or structure applies only where Swedish follows that order or structure.
- Something that only looks like the changed content, but is about something else, 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: for each change, what it says and why it was likely made; then every place in the Swedish file that it concerns, quoted, with whether that place needs an edit and why. Places the other language never mentions count too.

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
## en content at time of last sync:
## Schedule

| Day | Time |
|-----|------|
| Monday | 18–20 |
| Wednesday | 18–20 |


## Changes made to en since then:
@@ -4,3 +4,4 @@
 |-----|------|
 | Monday | 18–20 |
 | Wednesday | 18–20 |
+| Saturday | 9–12 |

## Current sv content (this is what you'll edit):
## Schema

| Dag | Tid |
|-----|-----|
| Måndag | 18–20 |
| Onsdag | 18–20 |


Update the sv file.

diff

✓ Run 1 · 1 edit · 2 turns · 4,050 in / 242 out tokens · $0.0082 · 3.3 s

Checks

  • ✓ has /^\| *Lördag *\| *9–12 *\|$/m
  • ✓ 5× /^\|/gm
  • ✓ in order: "Onsdag" → "Lördag"
  • ✓ changes only "| Onsdag"…"| Onsdag"

Swedish, before → after

@@ -4,3 +4,4 @@
 |-----|-----|
 | Måndag | 18–20 |
 | Onsdag | 18–20 |
+| Lördag | 9–12 |

The translator's notes

Change: English added a new schedule row, Saturday 9–12. The Swedish table has the same structure and lacks this row, so it needs the same row. In Swedish the row reads "Lördag | 9–12".I added a row for Saturday, "Lördag | 9–12", to the Swedish schedule table, matching the new English row. The rest of the table was already the same as English, so nothing else needed changing.

Tool calls

  1. edit_file: {"old_string":"| Onsdag | 18–20 |","new_string":"| Onsdag | 18–20 |\n| Lördag | 9–12 |"}
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions. The languages are equal peers; none is the original. Since Swedish was last brought up to date, someone changed English (en). For each language that changed, you have a diff showing what changed since Swedish was last synced: a line starting with a space is unchanged context, "-" was removed, "+" was added. The rest of that file is not shown.

Your job is not to translate the diff. It is to understand each change (what it says, and why it was likely made: a new fact, a correction, a rewording, a removal, a reordering) and then ask: if the person who made it had been editing the Swedish version instead, what would they have changed there? Make those changes.

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. Keep all of that, except where a change is about it. It follows that:
- One change may need several edits in Swedish: everywhere Swedish says what changed, also where the other language never said it, so that Swedish does not contradict itself.
- A change may need no edit at all: when Swedish does not have the content it is about, or already says what the change says.
- A change to order or structure applies only where Swedish follows that order or structure.
- Something that only looks like the changed content, but is about something else, 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: for each change, what it says and why it was likely made; then every place in the Swedish file that it concerns, quoted, with whether that place needs an edit and why. Places the other language never mentions count too.

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
## Changes made to en since sv last synced:
@@ -4,3 +4,4 @@
 |-----|------|
 | Monday | 18–20 |
 | Wednesday | 18–20 |
+| Saturday | 9–12 |

## Current sv content (this is what you'll edit):
## Schema

| Dag | Tid |
|-----|-----|
| Måndag | 18–20 |
| Onsdag | 18–20 |


Update the sv file.
✓ Run 2 · 1 edit · 2 turns · 4,054 in / 264 out tokens · $0.0084 · 3.4 s

Checks

  • ✓ has /^\| *Lördag *\| *9–12 *\|$/m
  • ✓ 5× /^\|/gm
  • ✓ in order: "Onsdag" → "Lördag"
  • ✓ changes only "| Onsdag"…"| Onsdag"

Swedish, before → after

@@ -4,3 +4,4 @@
 |-----|-----|
 | Måndag | 18–20 |
 | Onsdag | 18–20 |
+| Lördag | 9–12 |

The translator's notes

Change: English added a new schedule row, Saturday 9–12. The Swedish file has the same table, so it needs the same row, with the day written as "Lördag". Nothing else in the Swedish file mentions the schedule.I added a Saturday row, "Lördag | 9–12", to the Swedish schedule table. This matches the new Saturday 9–12 row in English. The rest of the Swedish file doesn't mention the schedule, so nothing else needed changing.

Tool calls

  1. edit_file: {"old_string":"| Onsdag | 18–20 |","new_string":"| Onsdag | 18–20 |\n| Lördag | 9–12 |"}
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions. The languages are equal peers; none is the original. Since Swedish was last brought up to date, someone changed English (en). For each language that changed, you have a diff showing what changed since Swedish was last synced: a line starting with a space is unchanged context, "-" was removed, "+" was added. The rest of that file is not shown.

Your job is not to translate the diff. It is to understand each change (what it says, and why it was likely made: a new fact, a correction, a rewording, a removal, a reordering) and then ask: if the person who made it had been editing the Swedish version instead, what would they have changed there? Make those changes.

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. Keep all of that, except where a change is about it. It follows that:
- One change may need several edits in Swedish: everywhere Swedish says what changed, also where the other language never said it, so that Swedish does not contradict itself.
- A change may need no edit at all: when Swedish does not have the content it is about, or already says what the change says.
- A change to order or structure applies only where Swedish follows that order or structure.
- Something that only looks like the changed content, but is about something else, 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: for each change, what it says and why it was likely made; then every place in the Swedish file that it concerns, quoted, with whether that place needs an edit and why. Places the other language never mentions count too.

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
## Changes made to en since sv last synced:
@@ -4,3 +4,4 @@
 |-----|------|
 | Monday | 18–20 |
 | Wednesday | 18–20 |
+| Saturday | 9–12 |

## Current sv content (this is what you'll edit):
## Schema

| Dag | Tid |
|-----|-----|
| Måndag | 18–20 |
| Onsdag | 18–20 |


Update the sv file.
✓ Run 3 · 1 edit · 2 turns · 4,061 in / 264 out tokens · $0.0041 · 3.4 s

Checks

  • ✓ has /^\| *Lördag *\| *9–12 *\|$/m
  • ✓ 5× /^\|/gm
  • ✓ in order: "Onsdag" → "Lördag"
  • ✓ changes only "| Onsdag"…"| Onsdag"

Swedish, before → after

@@ -4,3 +4,4 @@
 |-----|-----|
 | Måndag | 18–20 |
 | Onsdag | 18–20 |
+| Lördag | 9–12 |

The translator's notes

Change: English added a new schedule row, Saturday 9–12. The Swedish table has the same structure but lacks this row, so it needs one added row: "Lördag | 9–12". Nothing else in the Swedish file mentions the schedule.I added a Saturday row, "Lördag | 9–12", to the Swedish schedule table, matching the new row in English. The edit result shows the table reading correctly, and nothing else in the Swedish file mentions the schedule.

Tool calls

  1. edit_file: {"old_string":"| Onsdag | 18–20 |","new_string":"| Onsdag | 18–20 |\n| Lördag | 9–12 |"}
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions. The languages are equal peers; none is the original. Since Swedish was last brought up to date, someone changed English (en). For each language that changed, you have a diff showing what changed since Swedish was last synced: a line starting with a space is unchanged context, "-" was removed, "+" was added. The rest of that file is not shown.

Your job is not to translate the diff. It is to understand each change (what it says, and why it was likely made: a new fact, a correction, a rewording, a removal, a reordering) and then ask: if the person who made it had been editing the Swedish version instead, what would they have changed there? Make those changes.

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. Keep all of that, except where a change is about it. It follows that:
- One change may need several edits in Swedish: everywhere Swedish says what changed, also where the other language never said it, so that Swedish does not contradict itself.
- A change may need no edit at all: when Swedish does not have the content it is about, or already says what the change says.
- A change to order or structure applies only where Swedish follows that order or structure.
- Something that only looks like the changed content, but is about something else, 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: for each change, what it says and why it was likely made; then every place in the Swedish file that it concerns, quoted, with whether that place needs an edit and why. Places the other language never mentions count too.

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
## Changes made to en since sv last synced:
@@ -4,3 +4,4 @@
 |-----|------|
 | Monday | 18–20 |
 | Wednesday | 18–20 |
+| Saturday | 9–12 |

## Current sv content (this is what you'll edit):
## Schema

| Dag | Tid |
|-----|-----|
| Måndag | 18–20 |
| Onsdag | 18–20 |


Update the sv file.

difflook

✓ Run 1 · 1 edit · 2 turns · 4,910 in / 252 out tokens · $0.0095 · 3.3 s

Checks

  • ✓ has /^\| *Lördag *\| *9–12 *\|$/m
  • ✓ 5× /^\|/gm
  • ✓ in order: "Onsdag" → "Lördag"
  • ✓ changes only "| Onsdag"…"| Onsdag"

Swedish, before → after

@@ -4,3 +4,4 @@
 |-----|-----|
 | Måndag | 18–20 |
 | Onsdag | 18–20 |
+| Lördag | 9–12 |

The translator's notes

Change: English added a new schedule row, Saturday 9–12. The Swedish table has the same structure and lacks that row, so I'm adding "Lördag | 9–12" after Onsdag.I added a Saturday row, "Lördag | 9–12", to the Swedish schedule table, after Onsdag. This matches the row English added. The Swedish table had the same structure and no Saturday entry, so nothing else needed changing.

Tool calls

  1. edit_file: {"old_string":"| Onsdag | 18–20 |","new_string":"| Onsdag | 18–20 |\n| Lördag | 9–12 |"}
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions. The languages are equal peers; none is the original. Since Swedish was last brought up to date, someone changed English (en). For each language that changed, you have a diff showing what changed since Swedish was last synced: a line starting with a space is unchanged context, "-" was removed, "+" was added. The rest of that file is not shown. You can look at the current English page with search and read. Use them when what to do in Swedish depends on what that page says outside the diff: above all, whether something a change removed or renamed is still mentioned anywhere on it.

Your job is not to translate the diff. It is to understand each change (what it says, and why it was likely made: a new fact, a correction, a rewording, a removal, a reordering) and then ask: if the person who made it had been editing the Swedish version instead, what would they have changed there? Make those changes.

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. Keep all of that, except where a change is about it. It follows that:
- One change may need several edits in Swedish: everywhere Swedish says what changed, also where the other language never said it, so that Swedish does not contradict itself.
- A change may need no edit at all: when Swedish does not have the content it is about, or already says what the change says.
- A change to order or structure applies only where Swedish follows that order or structure.
- Something that only looks like the changed content, but is about something else, 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: for each change, what it says and why it was likely made; then every place in the Swedish file that it concerns, quoted, with whether that place needs an edit and why. Places the other language never mentions count too.

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
## Changes made to en since sv last synced:
@@ -4,3 +4,4 @@
 |-----|------|
 | Monday | 18–20 |
 | Wednesday | 18–20 |
+| Saturday | 9–12 |

## Current sv content (this is what you'll edit):
## Schema

| Dag | Tid |
|-----|-----|
| Måndag | 18–20 |
| Onsdag | 18–20 |


Update the sv file.
✓ Run 2 · 1 edit · 2 turns · 4,935 in / 285 out tokens · $0.0099 · 3.8 s

Checks

  • ✓ has /^\| *Lördag *\| *9–12 *\|$/m
  • ✓ 5× /^\|/gm
  • ✓ in order: "Onsdag" → "Lördag"
  • ✓ changes only "| Onsdag"…"| Onsdag"

Swedish, before → after

@@ -4,3 +4,4 @@
 |-----|-----|
 | Måndag | 18–20 |
 | Onsdag | 18–20 |
+| Lördag | 9–12 |

The translator's notes

The English change adds a new row to the schedule table: Saturday, 9–12. Probably a new session was added. The Swedish file has the same table without that row, and nothing else in it mentions days or times. So I'm adding "Lördag | 9–12" after the Wednesday row.I added a Saturday row, `| Lördag | 9–12 |`, after Wednesday in the Swedish schedule table. This matches the new Saturday row in the English version. Nothing else in the Swedish file mentions days or times, so no other edits were needed.

Tool calls

  1. edit_file: {"old_string":"| Onsdag | 18–20 |","new_string":"| Onsdag | 18–20 |\n| Lördag | 9–12 |"}
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions. The languages are equal peers; none is the original. Since Swedish was last brought up to date, someone changed English (en). For each language that changed, you have a diff showing what changed since Swedish was last synced: a line starting with a space is unchanged context, "-" was removed, "+" was added. The rest of that file is not shown. You can look at the current English page with search and read. Use them when what to do in Swedish depends on what that page says outside the diff: above all, whether something a change removed or renamed is still mentioned anywhere on it.

Your job is not to translate the diff. It is to understand each change (what it says, and why it was likely made: a new fact, a correction, a rewording, a removal, a reordering) and then ask: if the person who made it had been editing the Swedish version instead, what would they have changed there? Make those changes.

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. Keep all of that, except where a change is about it. It follows that:
- One change may need several edits in Swedish: everywhere Swedish says what changed, also where the other language never said it, so that Swedish does not contradict itself.
- A change may need no edit at all: when Swedish does not have the content it is about, or already says what the change says.
- A change to order or structure applies only where Swedish follows that order or structure.
- Something that only looks like the changed content, but is about something else, 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: for each change, what it says and why it was likely made; then every place in the Swedish file that it concerns, quoted, with whether that place needs an edit and why. Places the other language never mentions count too.

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
## Changes made to en since sv last synced:
@@ -4,3 +4,4 @@
 |-----|------|
 | Monday | 18–20 |
 | Wednesday | 18–20 |
+| Saturday | 9–12 |

## Current sv content (this is what you'll edit):
## Schema

| Dag | Tid |
|-----|-----|
| Måndag | 18–20 |
| Onsdag | 18–20 |


Update the sv file.
✓ Run 3 · 1 edit · 2 turns · 4,909 in / 263 out tokens · $0.0042 · 3.4 s

Checks

  • ✓ has /^\| *Lördag *\| *9–12 *\|$/m
  • ✓ 5× /^\|/gm
  • ✓ in order: "Onsdag" → "Lördag"
  • ✓ changes only "| Onsdag"…"| Onsdag"

Swedish, before → after

@@ -4,3 +4,4 @@
 |-----|-----|
 | Måndag | 18–20 |
 | Onsdag | 18–20 |
+| Lördag | 9–12 |

The translator's notes

Change: English added a new schedule row, Saturday 9–12. The Swedish table has the same structure and lacks that row, so I'll add "Lördag | 9–12" after Onsdag.I added a Saturday row, "Lördag | 9–12", to the Swedish schedule table, after Onsdag. English had added that same row, and the Swedish table had no equivalent. Nothing else in the Swedish file mentions the schedule, so no other edits were needed.

Tool calls

  1. edit_file: {"old_string":"| Onsdag | 18–20 |","new_string":"| Onsdag | 18–20 |\n| Lördag | 9–12 |"}
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions. The languages are equal peers; none is the original. Since Swedish was last brought up to date, someone changed English (en). For each language that changed, you have a diff showing what changed since Swedish was last synced: a line starting with a space is unchanged context, "-" was removed, "+" was added. The rest of that file is not shown. You can look at the current English page with search and read. Use them when what to do in Swedish depends on what that page says outside the diff: above all, whether something a change removed or renamed is still mentioned anywhere on it.

Your job is not to translate the diff. It is to understand each change (what it says, and why it was likely made: a new fact, a correction, a rewording, a removal, a reordering) and then ask: if the person who made it had been editing the Swedish version instead, what would they have changed there? Make those changes.

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. Keep all of that, except where a change is about it. It follows that:
- One change may need several edits in Swedish: everywhere Swedish says what changed, also where the other language never said it, so that Swedish does not contradict itself.
- A change may need no edit at all: when Swedish does not have the content it is about, or already says what the change says.
- A change to order or structure applies only where Swedish follows that order or structure.
- Something that only looks like the changed content, but is about something else, 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: for each change, what it says and why it was likely made; then every place in the Swedish file that it concerns, quoted, with whether that place needs an edit and why. Places the other language never mentions count too.

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
## Changes made to en since sv last synced:
@@ -4,3 +4,4 @@
 |-----|------|
 | Monday | 18–20 |
 | Wednesday | 18–20 |
+| Saturday | 9–12 |

## Current sv content (this is what you'll edit):
## Schema

| Dag | Tid |
|-----|-----|
| Måndag | 18–20 |
| Onsdag | 18–20 |


Update the sv file.