tags. Translate text inside tags.
First paragraph: "Ethereum is trading below $2,120 and the 100-hourly Simple Moving Average this Wednesday, as a recovery wave from $2,075 loses steam." -> "Ethereum bu Çarşamba günü 2.120 dolar ve 100 saatlik Basit Hareketli Ortalamanın altında işlem görüyor; 2.075 dolardan gelen toparlanma dalgası güç kaybediyor." "The largest altcoin hit the 61.8% Fibonacci retracement of the recent $2,197-$2,075 decline but failed to hold above $2,150, leaving the short-term bias bearish." -> "En büyük altcoin, son 2.197-2.075 dolar düşüşünün %61.8 Fibonacci düzeltme seviyesine ulaştı ancak 2.150 doların üzerinde tutunamadı ve kısa vadeli eğilimi düşüş yönlü bıraktı."
Second paragraph: "On the hourly chart, a bearish trend line is forming with resistance at $2,120. That level, together with the $2,150 mark, has capped any upside attempts. The hourly MACD is showing bearish momentum, and the RSI remains below 50 — signals that buyers haven't regained control." -> "Saatlik grafikte, 2.120 dolarda direnç oluşturan bir düşüş trend çizgisi oluşuyor. Bu seviye, 2.150 dolar işaretiyle birlikte tüm yukarı yönlü girişimleri sınırladı. Saatlik MACD düşüş momentumu gösteriyor ve RSI 50'nin altında kalmaya devam ediyor — alıcıların kontrolü henüz ele geçiremediğine işaret ediyor."
Third paragraph: "Major support sits at $2,075, just above the recent swing low. If that gives way, the next downside targets are $2,020 and then $2,000. A break below $2,000 would mark a fresh low for the month." -> "Ana destek, son dönüş düşüğünün hemen üzerinde olan 2.075 dolarda bulunuyor. Bu seviye kırılırsa, sonraki aşağı yönlü hedefler 2.020 dolar ve ardından 2.000 dolar. 2.000 doların altına bir kırılım, ay için yeni bir dip seviyeye işaret edecek."
Fourth paragraph: "On the upside, ETH needs to clear the $2,120 trend line and then $2,150 to gain traction. The next major resistance cluster sits at $2,200 and $2,220. If $2,220 breaks, a run toward $2,300 becomes possible. But with momentum leaning bearish, the path of least resistance is lower for now." -> "Yukarı yönde, ETH'nin ivme kazanmak için 2.120 dolar trend çizgisini ve ardından 2.150 doları aşması gerekiyor. Bir sonraki büyük direnç kümesi 2.200 dolar ve 2.220 dolarda bulunuyor. 2.220 dolar kırılırsa, 2.300 dolara doğru bir yükseliş mümkün hale gelir. Ancak momentum düşüş yönlü olduğu için, şimdilik en az dirençli yol aşağı yönlü."
Fifth paragraph: "Traders are watching the $2,075 level closely. A daily close below that could accelerate selling pressure toward the psychological $2,000 handle." -> "Yatırımcılar 2.075 dolar seviyesini yakından takip ediyor. Bu seviyenin altında bir günlük kapanış, satış baskısını psikolojik 2.000 dolar seviyesine doğru hızlandırabilir."
Headings: "Trend Line Resistance at $2,120" -> "2.120 Dolarda Trend Çizgisi Direnci". "Key Support Levels in Focus" -> "Odaktaki Ana Destek Seviyeleri". "What Needs to Happen for a Reversal" -> "Bir Dönüş İçin Ne Olması Gerek?"
Meta description: "Ethereum consolidates below $2,120 after failing to hold above $2,150. Bearish trend line forms, key supports at $2,075, $2,020, and $2,000." -> "Ethereum, 2.150 doların üzerinde tutunamadıktan sonra 2.120 doların altında konsolide oluyor. Düşüş trend çizgisi oluşuyor, ana destekler 2.075, 2.020 ve 2.000 dolarda."
Proper nouns: Ethereum, MACD, RSI, Fibonacci (retracement). Keep as is. "Simple Moving Average" -> "Basit Hareketli Ortalama" (SMA but we can translate). "Bears" -> "Ayılar". "Traders" -> "Yatırıcılar" or "Tüccarlar" but "yatırımcılar" is better in crypto context.
Ensure HTML structure: with and
. No extra tags. Use double quotes for JSON. Escape quotes inside strings if needed but since we are using double quotes for JSON, we need to escape any double quotes inside the translated text. However, our translated text likely doesn't contain double quotes except maybe for price references? We write prices as "2.120 dolar" etc. No quotes needed. So fine.
Now construct JSON.
Note: For numbers, use period as decimal separator in Turkish? In Turkish, decimal comma is used, but in crypto context, often English format is kept. The requirement says "keep all facts, numbers, and data accurate". It's safer to keep the original number format with periods? But in Turkish, we might want to use comma? However, the original uses periods (e.g., $2,120 - that's a comma for thousands, period for decimal? Actually $2,120 is two thousand one hundred twenty, so comma is thousand separator. In Turkish, thousand separator is period, decimal is comma. But the original uses comma as thousand separator. To be consistent with Turkish locale, we should convert: 2.120 (with dot) for thousands? But that might confuse. Alternatively, keep as is? The requirement says "keep all facts, numbers, and data accurate" - the representation of numbers should be clear. I think it's acceptable to keep the same format as original (using comma for thousands) because it's a common practice in financial texts in Turkish as well? Actually in Turkish, it's more common to use dot for thousands (2.120) and comma for decimals (2,50). But here prices are whole dollars, so no decimals. To avoid confusion, I'll use the original format with commas for thousands, as that's how they are written in the original. However, in Turkish, "2,120" might be read as two point one two zero? No, because there is no decimal point. Actually in Turkish, comma is used as decimal separator, so "2,120" would be interpreted as two point one two zero (i.e.,
and
