format/table-row
A row is added to a table.
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,127 in / 283 out tokens · $0.0088 · 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
The English change adds a new schedule row, Saturday 9–12. Presumably a new session was added. The Swedish file has the same table, so the row belongs there too. Nothing else in the Swedish file mentions the schedule. Swedish uses "Lördag" for Saturday and keeps the time format "9–12".I added a Saturday row, "Lördag | 9–12", to the Swedish schedule table. This matches the new row in English. The rest of the Swedish file didn't mention the schedule, so nothing else needed changing.
Tool calls
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,146 in / 318 out tokens · $0.0048 · 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 row to the schedule, Saturday 9–12, most likely because a new session was added. The Swedish table has the same structure (Dag/Tid) and lacks that row, so it needs the row: "| Onsdag | 18–20 |" followed by "| 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. English had added a Saturday session, and the Swedish table was missing it. Nothing else in the Swedish file refers to the schedule, so no other edits were needed.
Tool calls
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,127 in / 285 out tokens · $0.0044 · 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 Monday and Wednesday rows, so it needs the same row. Swedish uses "Lördag" and keeps the same time format, so the row is "| Lördag | 9–12 |".I added a Saturday row to the Swedish schedule table: `| Lördag | 9–12 |`. It matches the new row in English. The edit result shows the table reading correctly, with nothing else in the Swedish file affected.
Tool calls
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.