structure/list-became-table
The target shows as a table what the source keeps as a list; the source changes a row and adds one.
What changed
English changed
@@ -1,5 +1,6 @@ ## Prices - Adult: 300 SEK -- Junior: 150 SEK +- Junior: 100 SEK +- Senior: 200 SEK - Family: 600 SEK
Runs
hunks
✓ Run 1 · 1 edit · 2 turns · 4,255 in / 363 out tokens · $0.0098 · 4.2 s
Checks
- ✓
keeps "| Kategori | Pris |" - ✓
lacks /^- /m - ✓
has /^\| *Junior *\| *100 kr *\|$/m - ✓
has /^\| *(Senior|Pensionär)\w* *\| *200 kr *\|$/m - ✓
6× /^\|/gm
Swedish, before → after
@@ -3,5 +3,6 @@ | Kategori | Pris | |---|---| | Vuxen | 300 kr | -| Junior | 150 kr | +| Junior | 100 kr | +| Senior | 200 kr | | Familj | 600 kr |
The translator's notes
Changes in en: the Junior price went from 150 to 100 SEK (a price correction or update), and a new Senior category at 200 SEK was added between Junior and Family. Places in sv: - "| Junior | 150 kr |" needs an edit to 100 kr. - The table has no Senior row, so I'm adding "| Senior | 200 kr |" after Junior. This follows en's order, and Swedish keeps its own table format. - The other rows, "Vuxen" and "Familj", stay as they are.I made two changes to the Swedish price table to match the English one. I lowered the Junior price from 150 kr to 100 kr, and I added a new row, Senior at 200 kr, between Junior and Familj. The table format and the "kr" currency style are unchanged.
Tool calls
edit_file: {"old_string":"| Junior | 150 kr |","new_string":"| Junior | 100 kr |\n| Senior | 200 kr |"}
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: ## Prices - Adult: 300 SEK - Junior: 150 SEK - Family: 600 SEK ## Changes made to en since then: @@ -1,5 +1,6 @@ ## Prices - Adult: 300 SEK -- Junior: 150 SEK +- Junior: 100 SEK +- Senior: 200 SEK - Family: 600 SEK ## Current sv content (this is what you'll edit): ## Priser | Kategori | Pris | |---|---| | Vuxen | 300 kr | | Junior | 150 kr | | Familj | 600 kr | Update the sv file.
✓ Run 2 · 1 edit · 2 turns · 4,244 in / 352 out tokens · $0.0097 · 4.0 s
Checks
- ✓
keeps "| Kategori | Pris |" - ✓
lacks /^- /m - ✓
has /^\| *Junior *\| *100 kr *\|$/m - ✓
has /^\| *(Senior|Pensionär)\w* *\| *200 kr *\|$/m - ✓
6× /^\|/gm
Swedish, before → after
@@ -3,5 +3,6 @@ | Kategori | Pris | |---|---| | Vuxen | 300 kr | -| Junior | 150 kr | +| Junior | 100 kr | +| Senior | 200 kr | | Familj | 600 kr |
The translator's notes
Changes in en: the Junior price went from 150 to 100 SEK (a correction or price change), and a new Senior category at 200 SEK was added between Junior and Family. Places in sv: - `| Junior | 150 kr |` needs an edit, because the price is now 100 kr. - The table needs a new row `| Senior | 200 kr |`, placed after Junior and before Familj to match the en order. - The heading, the Vuxen row and the Familj row stay as they are.I updated the Swedish price table to match the English changes. The Junior price is now 100 kr (it was 150). I also added a Senior row at 200 kr between Junior and Familj, the same position as in English. The heading and the other rows were already correct, so I left them alone.
Tool calls
edit_file: {"old_string":"| Junior | 150 kr |","new_string":"| Junior | 100 kr |\n| Senior | 200 kr |"}
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: ## Prices - Adult: 300 SEK - Junior: 150 SEK - Family: 600 SEK ## Changes made to en since then: @@ -1,5 +1,6 @@ ## Prices - Adult: 300 SEK -- Junior: 150 SEK +- Junior: 100 SEK +- Senior: 200 SEK - Family: 600 SEK ## Current sv content (this is what you'll edit): ## Priser | Kategori | Pris | |---|---| | Vuxen | 300 kr | | Junior | 150 kr | | Familj | 600 kr | Update the sv file.
✓ Run 3 · 1 edit · 2 turns · 4,239 in / 335 out tokens · $0.0095 · 3.9 s
Checks
- ✓
keeps "| Kategori | Pris |" - ✓
lacks /^- /m - ✓
has /^\| *Junior *\| *100 kr *\|$/m - ✓
has /^\| *(Senior|Pensionär)\w* *\| *200 kr *\|$/m - ✓
6× /^\|/gm
Swedish, before → after
@@ -3,5 +3,6 @@ | Kategori | Pris | |---|---| | Vuxen | 300 kr | -| Junior | 150 kr | +| Junior | 100 kr | +| Senior | 200 kr | | Familj | 600 kr |
The translator's notes
Changes in en: 1. Junior price went from 150 to 100 SEK. This is a correction or price change. In sv, the row "| Junior | 150 kr |" needs to change to 100 kr. 2. A new Senior category at 200 SEK was added between Junior and Family. In sv, the table needs a new row "| Senior | 200 kr |" in the same position. The heading and the other rows stay as they are. Swedish uses a table, so I'm keeping that format.I updated the Swedish price table to match the English changes. The Junior price is now 100 kr (it was 150). I also added a Senior row at 200 kr between Junior and Family. I kept the table format and the "kr" currency style.
Tool calls
edit_file: {"old_string":"| Junior | 150 kr |","new_string":"| Junior | 100 kr |\n| Senior | 200 kr |"}
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: ## Prices - Adult: 300 SEK - Junior: 150 SEK - Family: 600 SEK ## Changes made to en since then: @@ -1,5 +1,6 @@ ## Prices - Adult: 300 SEK -- Junior: 150 SEK +- Junior: 100 SEK +- Senior: 200 SEK - Family: 600 SEK ## Current sv content (this is what you'll edit): ## Priser | Kategori | Pris | |---|---| | Vuxen | 300 kr | | Junior | 150 kr | | Familj | 600 kr | Update the sv file.