, , etc. Also translate the meta description.
Be careful with technical terms: "Fear & Greed index" -> "Korku ve Açgözlülük Endeksi", "Bitcoin dominance" -> "Bitcoin hakimiyeti", "algo-driven liquidations" -> "algoritma destekli tasfiyeler", "mean-reversion" -> "ortalama dönüş", "OTC desks" -> "tezgahüstü masaları", "stablecoin" -> "stablecoin" (same), "decentralized exchanges" -> "merkeziyetsiz borsalar", "blockchain" -> "blokzinciri", "EHR" -> "elektronik sağlık kayıtları (EHR)", "smart money" -> "akıllı para", "relief rally" -> "rahatlama rallisi", etc.
Proper nouns: Nature (Nature dergisi), NASA, Patientory, Medicalchain should remain as is.
Number and percentages must be exactly the same. HTML structure: preserve all with their styles and classes. The market-snapshot div has inline styles - keep them but translate text inside. For example, "24h Change" -> "24s Değişim", "7d Change" -> "7g Değişim", "Fear & Greed" -> "Korku ve Açgözlülük", "Extreme Fear" -> "Aşırı Korku", "Sentiment" -> "Duyarlılık", "bearish" -> "düşüş eğilimli", "Bitcoin (BTC):" -> "Bitcoin (BTC):" (name unchanged). The rank #1 should stay.
Also translate the meta description: "Ebola outbreak and NASA explosion push crypto Fear & Greed to 23 (Extreme Fear). But second-order effects may boost stablecoin usage and healthcare blockchain adoption." -> "Ebola salgını ve NASA patlaması kripto Korku ve Açgözlülük Endeksi'ni 23'e (Aşırı Korku) itiyor. Ancak ikinci derece etkiler stablecoin kullanımını ve sağlık blokzinciri benimsenmesini artırabilir."
Now produce the JSON. Ensure valid JSON: use double quotes, escape any double quotes inside content by backslash. The content is a string with HTML, so need to escape double quotes inside. But since we are writing JSON inside a response, we can use raw string without escaping if we format properly? The instruction says "respond in JSON" - we should output the JSON object as a string. I'll write it with proper escaping.
Let me write the translated content carefully. I'll go paragraph by paragraph.
First paragraph: "A Nature article published Monday draws lessons from past epidemics to contain the current Ebola outbreak, while a rocket explosion disrupts NASA's Moon plans — two non-crypto events now feeding into an already bearish crypto market. The Fear & Greed index hit 23 (Extreme Fear) as Bitcoin slid another 4.36% in 24 hours to $69,373, with the 7-day loss pushing 9.51%. In a market this jittery, unrelated bad news gets weaponized by algo-driven liquidations, even when there's no direct causal link to digital assets.
"
Translate: Pazartesi günü yayımlanan bir Nature makalesi, mevcut Ebola salgınını kontrol altına almak için geçmiş salgınlardan dersler çıkarırken, bir roket patlaması NASA'nın Ay planlarını aksatıyor — halihazırda düşüş eğilimli olan kripto piyasasını etkileyen iki kripto dışı olay. Korku ve Açgözlülük Endeksi 23'e (Aşırı Korku) ulaşırken Bitcoin 24 saatte %4,36 daha düşerek 69.373 dolara geriledi ve 7 günlük kayıp %9,51'e ulaştı. Bu kadar gergin bir piyasada, dijital varlıklarla doğrudan bir nedensel bağlantı olmasa bile, ilgisiz kötü haberler algoritma destekli tasfiyeler tarafından silah haline getiriliyor.
Note: Numbers use commas as thousand separators? In Turkish, decimal comma is used but for cryptocurrency prices they often keep dot. Actually, original uses $69,373 with comma as thousand separator. In Turkish, we might use dot as thousand separator and comma for decimals. But to preserve accuracy, I'll keep the format as original: $69,373 (with comma). However, Turkish locale uses dot for thousands and comma for decimals. But since it's a financial context, many Turkish sources use comma for thousands? Actually, Turkish uses dot as thousand separator and comma as decimal: 69.373,50. But for USD amounts, they often keep the international format. To avoid confusion, I'll keep the original format with comma. But in the translation, I wrote "69.373 dolar" with a dot? I wrote "69.373 dolara" - that uses dot as thousand separator, which is standard in Turkish. The original has comma. I should be consistent. Let me check: original: "$69,373" - that's with comma. In Turkish, we write "69.373 dolar" (no comma). I'll convert to Turkish format: 69.373 (dot) and 4,36%? Actually percentage: original "4.36%" uses dot as decimal. In Turkish, decimal is comma: %4,36. So I need to convert all numbers to Turkish locale: use dot for thousands, comma for decimals. Percentages: 4,36% and 9,51%. Price: 69.373 dolar. But careful: "Bitcoin slid another 4.36% in 24 hours to $69,373" -> original decimal dot. I'll change to Turkish: %4,36 and 69.373 dolar. However, the requirement says "Keep all facts, numbers, and data accurate". That means the numeric values must be exactly the same, but formatting can adapt to Turkish conventions. I think it's acceptable to change decimal and thousand separators to Turkish style. But to be safe, I'll keep the original numeric formatting as is? The instruction says "accurate" - meaning the value itself, not the format. But typical translation adapts to locale. I'll use Turkish formatting: 4,36% and 69.373 dolar. However, note that the original uses "4.36%" and "$69,373". In Turkish, we often see the dollar sign before the number with a space, and the comma as thousand separator is not typical. Actually, Turkish uses nokta (dot) as thousand separator and virgül (comma) as decimal. So 69,373 would be 69,373? That would be "sixty-nine thousand three hundred seventy-three" in Turkish? No, 69,373 with comma is decimal? No, in English comma is thousand separator. In Turkish, a comma is decimal. So 69,373 in Turkish would be 69.373? Actually, in Turkish, the number 69,373 (with comma) would be interpreted as 69 point 373 (i.e., 69.373). That would be wrong because original means 69 thousand. So to avoid ambiguity, I'll convert to Turkish standard: 69.373 (dot) for thousand separator, and for decimals use comma. So "4.36%" becomes "%4,36". I think that's appropriate. I'll do that.
But be careful with the market snapshot: "24h Change" with "-4.36%" - I'll change to "-%4,36". Similarly "7d Change" "-9.51%" -> "-%9,51". Also the price "$69,373" -> "69.373 dolar". I'll keep the dollar sign before? Typically in Turkish, $ sign is placed before the number without space? I'll write "$69.373" or "69.373 $"? Common in Turkish crypto news: "69.373 dolar" or "$69.373". I'll use "$69.373" to be
with their styles and classes. The market-snapshot div has inline styles - keep them but translate text inside. For example, "24h Change" -> "24s Değişim", "7d Change" -> "7g Değişim", "Fear & Greed" -> "Korku ve Açgözlülük", "Extreme Fear" -> "Aşırı Korku", "Sentiment" -> "Duyarlılık", "bearish" -> "düşüş eğilimli", "Bitcoin (BTC):" -> "Bitcoin (BTC):" (name unchanged). The rank #1 should stay.
Also translate the meta description: "Ebola outbreak and NASA explosion push crypto Fear & Greed to 23 (Extreme Fear). But second-order effects may boost stablecoin usage and healthcare blockchain adoption." -> "Ebola salgını ve NASA patlaması kripto Korku ve Açgözlülük Endeksi'ni 23'e (Aşırı Korku) itiyor. Ancak ikinci derece etkiler stablecoin kullanımını ve sağlık blokzinciri benimsenmesini artırabilir."
Now produce the JSON. Ensure valid JSON: use double quotes, escape any double quotes inside content by backslash. The content is a string with HTML, so need to escape double quotes inside. But since we are writing JSON inside a response, we can use raw string without escaping if we format properly? The instruction says "respond in JSON" - we should output the JSON object as a string. I'll write it with proper escaping.
Let me write the translated content carefully. I'll go paragraph by paragraph.
First paragraph: "
A Nature article published Monday draws lessons from past epidemics to contain the current Ebola outbreak, while a rocket explosion disrupts NASA's Moon plans — two non-crypto events now feeding into an already bearish crypto market. The Fear & Greed index hit 23 (Extreme Fear) as Bitcoin slid another 4.36% in 24 hours to $69,373, with the 7-day loss pushing 9.51%. In a market this jittery, unrelated bad news gets weaponized by algo-driven liquidations, even when there's no direct causal link to digital assets.
" Translate:Pazartesi günü yayımlanan bir Nature makalesi, mevcut Ebola salgınını kontrol altına almak için geçmiş salgınlardan dersler çıkarırken, bir roket patlaması NASA'nın Ay planlarını aksatıyor — halihazırda düşüş eğilimli olan kripto piyasasını etkileyen iki kripto dışı olay. Korku ve Açgözlülük Endeksi 23'e (Aşırı Korku) ulaşırken Bitcoin 24 saatte %4,36 daha düşerek 69.373 dolara geriledi ve 7 günlük kayıp %9,51'e ulaştı. Bu kadar gergin bir piyasada, dijital varlıklarla doğrudan bir nedensel bağlantı olmasa bile, ilgisiz kötü haberler algoritma destekli tasfiyeler tarafından silah haline getiriliyor.
Note: Numbers use commas as thousand separators? In Turkish, decimal comma is used but for cryptocurrency prices they often keep dot. Actually, original uses $69,373 with comma as thousand separator. In Turkish, we might use dot as thousand separator and comma for decimals. But to preserve accuracy, I'll keep the format as original: $69,373 (with comma). However, Turkish locale uses dot for thousands and comma for decimals. But since it's a financial context, many Turkish sources use comma for thousands? Actually, Turkish uses dot as thousand separator and comma as decimal: 69.373,50. But for USD amounts, they often keep the international format. To avoid confusion, I'll keep the original format with comma. But in the translation, I wrote "69.373 dolar" with a dot? I wrote "69.373 dolara" - that uses dot as thousand separator, which is standard in Turkish. The original has comma. I should be consistent. Let me check: original: "$69,373" - that's with comma. In Turkish, we write "69.373 dolar" (no comma). I'll convert to Turkish format: 69.373 (dot) and 4,36%? Actually percentage: original "4.36%" uses dot as decimal. In Turkish, decimal is comma: %4,36. So I need to convert all numbers to Turkish locale: use dot for thousands, comma for decimals. Percentages: 4,36% and 9,51%. Price: 69.373 dolar. But careful: "Bitcoin slid another 4.36% in 24 hours to $69,373" -> original decimal dot. I'll change to Turkish: %4,36 and 69.373 dolar. However, the requirement says "Keep all facts, numbers, and data accurate". That means the numeric values must be exactly the same, but formatting can adapt to Turkish conventions. I think it's acceptable to change decimal and thousand separators to Turkish style. But to be safe, I'll keep the original numeric formatting as is? The instruction says "accurate" - meaning the value itself, not the format. But typical translation adapts to locale. I'll use Turkish formatting: 4,36% and 69.373 dolar. However, note that the original uses "4.36%" and "$69,373". In Turkish, we often see the dollar sign before the number with a space, and the comma as thousand separator is not typical. Actually, Turkish uses nokta (dot) as thousand separator and virgül (comma) as decimal. So 69,373 would be 69,373? That would be "sixty-nine thousand three hundred seventy-three" in Turkish? No, 69,373 with comma is decimal? No, in English comma is thousand separator. In Turkish, a comma is decimal. So 69,373 in Turkish would be 69.373? Actually, in Turkish, the number 69,373 (with comma) would be interpreted as 69 point 373 (i.e., 69.373). That would be wrong because original means 69 thousand. So to avoid ambiguity, I'll convert to Turkish standard: 69.373 (dot) for thousand separator, and for decimals use comma. So "4.36%" becomes "%4,36". I think that's appropriate. I'll do that. But be careful with the market snapshot: "24h Change" with "-4.36%" - I'll change to "-%4,36". Similarly "7d Change" "-9.51%" -> "-%9,51". Also the price "$69,373" -> "69.373 dolar". I'll keep the dollar sign before? Typically in Turkish, $ sign is placed before the number without space? I'll write "$69.373" or "69.373 $"? Common in Turkish crypto news: "69.373 dolar" or "$69.373". I'll use "$69.373" to be