Loading market data...

Ruben Dias utelukket fra Portugals VM-åpning mot Kongo

Ruben Dias utelukket fra Portugals VM-åpning mot Kongo
tags. Use "Kongo" for Congo (Norwegian spelling). "defensive anchor" = defensiv anker? Or "forsvarsanker". "dealing a blow" = et slag, en smell. "building momentum" = bygget opp fart/oppkjør. "exact nature of the injury" = den eksakte skadens art. "has not been disclosed" = er ikke offentliggjort. H2: "Why Dias’s absence matters" = "Hvorfor Dias' fravær betyr noe" or "Hvorfor Dias' fravær er viktig". "bedrock" = grunnfjell, fundament. "back line" = forsvarslinje. "organize the defense" = organisere forsvaret. "read the game" = lese spillet. "near-automatic starter" = nær automatisk starter. "every match in the group stage carries heavy weight" = hver kamp i gruppespillet har stor betydning. "traditional powerhouse" = tradisjonell stormakt. "punish defensive mistakes" = straffe defensive feil. "high-stakes opener" = høyt spill åpning. H2: "Who steps into the void" = "Hvem trer inn i tomrommet". "coaching staff" = trenerteamet. "difficult choice" = vanskelig valg. "veteran center-back" = veteran midtstopper. "leadership" = lederskap. "younger player" = yngre spiller. "impressed in recent friendlies" = imponert i nylige vennskapskamper. "big-game experience" = erfaring fra store kamper. "handling Congo’s attacking threats" = håndtere Kongos angrepstrusler. "speed on the counter" = fart i kontringer. H2: "Congo’s threat and Portugal’s adjustment" = "Kongos trussel og Portugals tilpasning". "little to lose" = lite å tape. "everything to prove" = alt å bevise. "forwards" = spisser. "good form" = god form. "see Dias’s absence as an opportunity" = se Dias' fravær som en mulighet. "midfield and fullbacks" = midtbane og backer. "provide extra cover" = gi ekstra dekning. "goalkeeper" = keeper/målmann. "called upon more than anticipated" = bli mer involvert enn forventet. "set-piece routines" = dødballrutiner. "primary target on corners and free kicks" = primært mål på hjørnespark og frispark. "aerial threat" = lufttrussel. "forces a tactical rethink" = tvinger fram en taktisk omstilling. Last paragraph: "The match is the first test of Portugal’s depth." = "Kampen er den første testen av Portugals dybde." "replacement defense holds up" = erstatningsforsvaret holder stand. "move forward with confidence" = gå videre med selvtillit. "star defender" = stjernespiller i forsvar. Meta description: "Portugal will face Congo without star defender Ruben Dias, who has been ruled out of the World Cup opener. The team must now find a replacement for their defensive anchor." Translate: "Portugal møter Kongo uten stjernespissen Ruben Dias, som er utelukket fra VM-åpningen. Laget må nå finne en erstatter for deres defensive anker." But careful: "star defender" not "stjernespissen" (that's forward). Use "stjernespiller i forsvar" or "stjernestopper". Simpler: "Portugal møter Kongo uten stjernestopper Ruben Dias, som er utelukket fra VM-åpningen. Laget må nå finne en erstatter for forsvarsankeret sitt." Now produce JSON. Ensure valid JSON. Use double quotes. Escape any quotes inside. The content has
tags with

and

. Translate all text inside tags but keep tags intact. Also note that the original has a stray

after the second h2? Actually original: after "

Congo enters..." but there is a

before that? Let's see: after "tactical rethink.

The match..." So two paragraphs. We'll replicate structure. I'll write the translated content as a string with HTML. Need to be careful with line breaks? JSON can have newlines inside string, but better to keep as one line or use \n. I'll keep it as a single line with no indentation to avoid issues, but it's fine to have newlines as long as escaped. I'll produce pretty JSON with indentation for readability, but ensure it's valid. For the content, I'll write it as a multi-line string inside the JSON, but in JSON, newlines must be escaped or use \n. I can use actual newlines inside the string if I enclose in quotes? Actually JSON strings can contain literal newlines if they are escaped as \n, but not raw newlines. So I'll replace newlines with \n. Alternatively, I can keep the HTML as a single line. Since it's short, I'll make it a single line to avoid escaping issues. But the original has

...