← all cases

basic/glossary

A new sentence uses terms the host's glossary decides.

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

What changed

English changed

@@ -10,7 +10,7 @@ Pay by card or PayPal.
 
 ## Opening hours
 
-The boathouse is open every day from 7 to 21 during the season.
+The boathouse is open every day from 7 to 21 during the season. In winter, members train on the ergs in the gym.
 
 ## Contact
 

Runs

hunks

✓ Run 1 · 1 edit · 2 turns · 4,913 in / 451 out tokens · $0.0117 · 4.9 s

Checks

  • ✓ has /roddmaskin/i
  • ✓ lacks /\berg(s|ar|en|arna)?\b|ergometer/i
  • ✓ changes only "Båthuset är öppet"…"Båthuset är öppet"

Swedish, before → after

@@ -10,7 +10,7 @@
 
 ## Öppettider
 
-Båthuset är öppet varje dag mellan 7 och 21 under säsongen.
+Båthuset är öppet varje dag mellan 7 och 21 under säsongen. På vintern tränar medlemmarna på roddmaskinerna i gymmet.
 
 ## Kontakt

The translator's notes

**Change:** English added a sentence to the opening hours section: "In winter, members train on the ergs in the gym." This is new information about winter training, so it was likely added to say what happens when the boathouse isn't in season.

**Places in Swedish:**
- "Båthuset är öppet varje dag mellan 7 och 21 under säsongen." This is the matching paragraph and needs the new sentence. "Erg" becomes "roddmaskin" under the glossary.
- The payment line ("Betala med kort eller Swish") is a deliberate local difference and is unrelated to this change, so it stays.
- No other place in the Swedish file mentions winter or training indoors.I added the new winter-training sentence to the "Öppettider" section of the Swedish file: "På vintern tränar medlemmarna på roddmaskinerna i gymmet." I used "roddmaskinerna" for "ergs", as the glossary requires. I left the rest of the file as it was, including the Swish payment line, which is a local difference unrelated to this change.

Tool calls

  1. edit_file: {"old_string":"under säsongen.","new_string":"under säsongen. På vintern tränar medlemmarna på roddmaskinerna i gymmet."}
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.

The following rules and glossary are binding — follow them even where another translation would read naturally:

Glossary: "erg" is "roddmaskin" in Swedish, never "erg" or "ergometer". "Riverside Rowing Club" is "Riverside Roddklubb".
User
## en content at time of last sync:
# Membership

Join the Riverside Rowing Club and get access to boats, coaching and the clubhouse.

## Fees

Membership costs 200 SEK per year. Students pay half.

Pay by card or PayPal.

## Opening hours

The boathouse is open every day from 7 to 21 during the season.

## Contact

Email the board at board@riverside.example.


## Changes made to en since then:
@@ -10,7 +10,7 @@ Pay by card or PayPal.
 
 ## Opening hours
 
-The boathouse is open every day from 7 to 21 during the season.
+The boathouse is open every day from 7 to 21 during the season. In winter, members train on the ergs in the gym.
 
 ## Contact
 

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

Bli medlem i Riverside Roddklubb och få tillgång till båtar, träning och klubbhuset.

## Avgifter

Medlemskapet kostar 200 kr per år. Studenter betalar halva priset.

Betala med kort eller Swish.

## Öppettider

Båthuset är öppet varje dag mellan 7 och 21 under säsongen.

## Kontakt

Mejla styrelsen på board@riverside.example.


Update the sv file.
✓ Run 2 · 1 edit · 2 turns · 4,896 in / 428 out tokens · $0.0114 · 5.0 s

Checks

  • ✓ has /roddmaskin/i
  • ✓ lacks /\berg(s|ar|en|arna)?\b|ergometer/i
  • ✓ changes only "Båthuset är öppet"…"Båthuset är öppet"

Swedish, before → after

@@ -10,7 +10,7 @@
 
 ## Öppettider
 
-Båthuset är öppet varje dag mellan 7 och 21 under säsongen.
+Båthuset är öppet varje dag mellan 7 och 21 under säsongen. På vintern tränar medlemmarna på roddmaskinerna i gymmet.
 
 ## Kontakt

The translator's notes

**Change:** English added a sentence to the opening hours section: "In winter, members train on the ergs in the gym." This is new information about winter training, so it was likely added to say what happens outside the season.

**Places in sv:**
- "Båthuset är öppet varje dag mellan 7 och 21 under säsongen." This is the matching sentence, and it needs the new sentence added after it. Per the glossary, "erg" is "roddmaskin".
- The payment line says Swish where English says PayPal. That is a deliberate local difference and has nothing to do with this change, so it stays.
- The other sections don't concern this change.I added the new winter-training sentence to the opening hours section in the Swedish file: "På vintern tränar medlemmarna på roddmaskinerna i gymmet." It uses "roddmaskinerna" for "ergs", as the glossary requires. I left the Swish payment line alone, since it is a deliberate local difference from English's PayPal.

Tool calls

  1. edit_file: {"old_string":"under säsongen.","new_string":"under säsongen. På vintern tränar medlemmarna på roddmaskinerna i gymmet."}
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.

The following rules and glossary are binding — follow them even where another translation would read naturally:

Glossary: "erg" is "roddmaskin" in Swedish, never "erg" or "ergometer". "Riverside Rowing Club" is "Riverside Roddklubb".
User
## en content at time of last sync:
# Membership

Join the Riverside Rowing Club and get access to boats, coaching and the clubhouse.

## Fees

Membership costs 200 SEK per year. Students pay half.

Pay by card or PayPal.

## Opening hours

The boathouse is open every day from 7 to 21 during the season.

## Contact

Email the board at board@riverside.example.


## Changes made to en since then:
@@ -10,7 +10,7 @@ Pay by card or PayPal.
 
 ## Opening hours
 
-The boathouse is open every day from 7 to 21 during the season.
+The boathouse is open every day from 7 to 21 during the season. In winter, members train on the ergs in the gym.
 
 ## Contact
 

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

Bli medlem i Riverside Roddklubb och få tillgång till båtar, träning och klubbhuset.

## Avgifter

Medlemskapet kostar 200 kr per år. Studenter betalar halva priset.

Betala med kort eller Swish.

## Öppettider

Båthuset är öppet varje dag mellan 7 och 21 under säsongen.

## Kontakt

Mejla styrelsen på board@riverside.example.


Update the sv file.
✓ Run 3 · 1 edit · 2 turns · 4,904 in / 439 out tokens · $0.0115 · 4.8 s

Checks

  • ✓ has /roddmaskin/i
  • ✓ lacks /\berg(s|ar|en|arna)?\b|ergometer/i
  • ✓ changes only "Båthuset är öppet"…"Båthuset är öppet"

Swedish, before → after

@@ -10,7 +10,7 @@
 
 ## Öppettider
 
-Båthuset är öppet varje dag mellan 7 och 21 under säsongen.
+Båthuset är öppet varje dag mellan 7 och 21 under säsongen. På vintern tränar medlemmarna på roddmaskinerna i gymmet.
 
 ## Kontakt

The translator's notes

**Change:** English added a sentence to the Opening hours section: "In winter, members train on the ergs in the gym." This is a new fact, saying what happens outside the season.

**Places in the Swedish file:**
- "Båthuset är öppet varje dag mellan 7 och 21 under säsongen." This is the matching paragraph, and it needs the new sentence. Per the glossary, "ergs" becomes "roddmaskiner".
- The payment line ("Swish" instead of PayPal) is a deliberate local difference and is unrelated to this change, so it stays.
- The other sections don't mention winter training, so they stay as they are.I added the new winter-training sentence to the Opening hours section of the Swedish file: "På vintern tränar medlemmarna på roddmaskinerna i gymmet." I used "roddmaskinerna" for "ergs", as the glossary requires. I left the rest of the file as it was, including the Swish payment line, which is a deliberate difference from the English.

Tool calls

  1. edit_file: {"old_string":"under säsongen.","new_string":"under säsongen. På vintern tränar medlemmarna på roddmaskinerna i gymmet."}
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.

The following rules and glossary are binding — follow them even where another translation would read naturally:

Glossary: "erg" is "roddmaskin" in Swedish, never "erg" or "ergometer". "Riverside Rowing Club" is "Riverside Roddklubb".
User
## en content at time of last sync:
# Membership

Join the Riverside Rowing Club and get access to boats, coaching and the clubhouse.

## Fees

Membership costs 200 SEK per year. Students pay half.

Pay by card or PayPal.

## Opening hours

The boathouse is open every day from 7 to 21 during the season.

## Contact

Email the board at board@riverside.example.


## Changes made to en since then:
@@ -10,7 +10,7 @@ Pay by card or PayPal.
 
 ## Opening hours
 
-The boathouse is open every day from 7 to 21 during the season.
+The boathouse is open every day from 7 to 21 during the season. In winter, members train on the ergs in the gym.
 
 ## Contact
 

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

Bli medlem i Riverside Roddklubb och få tillgång till båtar, träning och klubbhuset.

## Avgifter

Medlemskapet kostar 200 kr per år. Studenter betalar halva priset.

Betala med kort eller Swish.

## Öppettider

Båthuset är öppet varje dag mellan 7 och 21 under säsongen.

## Kontakt

Mejla styrelsen på board@riverside.example.


Update the sv file.