with h2, p, div with market snapshot, p, h2, p. We need to translate all text, keep HTML structure and inline styles. Also keep numbers and data.
Let's translate paragraph by paragraph.
First h2: "The scale of the displacement" -> "La scala dello spostamento" or "L'entità dello sfollamento". I'll use "L'entità dello sfollamento".
First p: "The numbers are stark. Six million deportees are now trying to rebuild lives in a country already struggling with a collapsed economy and a banking system that barely functions. On top of that, another million have come back from Pakistan and Iran just in 2026, as of August. That's a lot of people arriving in a short window, and most of them have nothing to return to. The six million figure is cumulative, while the one million is for this year alone."
Translation: "I numeri sono impressionanti. Sei milioni di deportati stanno ora cercando di ricostruire le proprie vite in un paese già alle prese con un'economia collassata e un sistema bancario che funziona a malapena. In aggiunta, un altro milione è tornato dal Pakistan e dall'Iran solo nel 2026, ad agosto. Sono molte persone che arrivano in un breve lasso di tempo, e la maggior parte di loro non ha nulla a cui tornare. La cifra di sei milioni è cumulativa, mentre quella di un milione è solo per quest'anno."
Next div with market snapshot: We need to translate the text inside. The div has inline styles, we keep them. The content: "📊 Market Data Snapshot" -> "📊 Riepilogo Dati di Mercato" or "Snapshot dei Dati di Mercato". I'll use "📊 Riepilogo Dati di Mercato". Then the grid: "24h Change" -> "Variazione 24h", "7d Change" -> "Variazione 7g" (or "7d" but in Italian we use "7g" for 7 giorni? Actually "7d" is common, but we can translate as "Variazione 7g" or keep "7d"? Since it's a label, I'll translate: "Variazione 24h" and "Variazione 7g" (g for giorni). But to be consistent, maybe "Variazione 7d" is fine? I'll use "Variazione 7g" to be Italian. But the original says "7d Change" - we can translate as "Variazione 7 giorni" but that's long. I'll use "Variazione 7g" as abbreviation. Also "Fear & Greed" -> "Paura e Avidità" (common in crypto). "Sentiment" -> "Sentimento" or "Sentiment" is used in Italian too, but we can translate as "Sentimento". The values: "-0.76%", "-2.50%", "69 Greed" -> "69 Avidità" (since Greed is Avidità). "🟢 slightly bullish" -> "🟢 leggermente rialzista". Then the Bitcoin line: "Bitcoin (BTC):" -> "Bitcoin (BTC):" (keep), "$77,859" -> "$77.859" (Italian uses dot for thousands? Actually in Italian, they use comma for decimal and dot for thousands? But here it's a price, we can keep as is, but maybe convert to Italian format? The original uses comma for thousands? Actually "$77,859" is 77,859 dollars, in Italian we would write "$77.859" (dot as thousands separator). But since it's a price, we can keep as is, but to be consistent, I'll change to "$77.859". Also "Rank #1" -> "Posizione #1" or "Rank #1" is used. I'll keep "Rank #1" as it's common.
We need to preserve the HTML structure exactly, so we'll just replace the text content.
Next p: "For traders, this is not a market-moving event. The crisis is geographically contained, and there's no direct link to Bitcoin or Ethereum prices. The current crypto rally is being driven by liquidity and ETF flows, not by humanitarian emergencies in Central Asia. But the situation does add to global geopolitical risk. If it escalates into a broader regional conflict, that could shift risk sentiment. That's a low-probability scenario, but traders should keep an eye on it."
Translation: "Per i trader, questo non è un evento in grado di muovere il mercato. La crisi è geograficamente contenuta e non c'è un collegamento diretto con i prezzi di Bitcoin o Ethereum. L'attuale rally delle criptovalute è guidato dalla liquidità e dai flussi degli ETF, non da emergenze umanitarie in Asia centrale. Ma la situazione aggiunge rischio geopolitico globale. Se dovesse degenerare in un conflitto regionale più ampio, potrebbe spostare il sentiment di rischio. È uno scenario a bassa probabilità, ma i trader dovrebbero tenerlo d'occhio."
Next h2: "The long-term question" -> "La questione a lungo termine"
Next p: "Over the long term, the displacement could reinforce the narrative that crypto is a hedge against unstable governance. In countries where banks fail and currencies collapse, people often look for alternatives. Afghanistan is a case in point, though the Taliban" - it ends abruptly. We'll translate: "Nel lungo termine, lo spostamento potrebbe rafforzare la narrazione secondo cui le criptovalute sono una copertura contro una governance instabile. Nei paesi in cui le banche falliscono e le valute crollano, le persone spesso cercano alternative. L'Afghanistan è un caso esemplare, anche se i talebani" - but the original ends with "though the Taliban" - we need to keep that incomplete? It's part of the article, so we'll translate as is: "anche se i talebani" and then close the article.
Now we need to output JSON. The meta description is empty, so we'll set to "".
Let's construct the JSON.
We'll put the translated title, content as a string with the HTML, and meta.description as "".
Make sure to escape double quotes in the content? Since it's JSON, we need to escape any double quotes inside. The content has double quotes in the HTML attributes? Actually the HTML uses single quotes for attributes? It uses double quotes for some attributes like style="..." but those are inside the string, so we need to escape them. We'll use a JSON string with escaped quotes. Alternatively, we can use a JSON library, but we'll just manually escape.
We'll write the content as a single string with the HTML. We'll replace all double quotes with \" inside the string.
Let's do it.
First, the title: "I deportati afghani superano i 6 milioni mentre i rimpatri da Pakistan e Iran superano il milione quest'anno" - but we need to be careful with apostrophe? In Italian, we use apostrophe for "quest'anno" - that's fine. In JSON, we need to escape double quotes, but apostrophes are fine.
Now content: We'll write the entire ...
