ትርጉም
AR HE
የቅርብ ጊዜ ውጤቶች
የተገኘ
እንዴት መተርጎም Arabic ወደ Hebrew
1
ጽሑፉን አስገባ
የእርስዎን Arabic ርዕስ በላይ ባለው የመግባት መስኮት ውስጥ ይጻፉ ወይም ይጣጡ። እስከ 10,000 አሃዞች ድረስ መግባት ይችላሉ፣ ወይም ሰነድ ፋይልን መላክ ይችላሉ።
2
ትርጉም
በትርጉም ቁልፍ ላይ ጠቅ ያድርጉ ወይም በቀላሉ ተጠባበቁ - ራስ-ሰር-ትርጉም ከመጻፍዎ በኋላ ይጀምራል. AI ጽሑፍዎን በሚሊሴኮንዶች ውስጥ ይሠራል.
3
ትርጉሙን ቅጂ
የእርስዎ Hebrew ትርጉም በፍጥነት ይታያል. ወደ ክሊፕቦርድዎ ለማስቀመጥ ቅጂውን ጠቅ ያድርጉ፣ ወይም ከAPI ጋር ይቀላቀሉ.
የተለመዱ Arabic ቃላት
በፍጥነት ለመተርጎም ማንኛውንም ቃል ጠቅ ያድርጉ
ቀጥተኛ ትርጉም
Arabic ወደ Hebrew ትርጉሞችን በመቶ ሰከንዶች ውስጥ ማግኘት
ሰነዶች
Word, PDF, SRT ርዕሶች እና ለ batch ትርጉም የበለጠ ይጫኑ.
API መዳረሻ
ይህ ትርጉም እኩል ወደ REST API ጋር መተግበሪያዎችዎ ውስጥ ማካተት.
curl -X POST https://api.translateapi.ai/api/v1/translate/ \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text": "Hello", "source_language": "ar", "target_language": "he"}'ስለ Arabic ወደ Hebrew ትርጉም
TranslateAPI ፈጣን እና ትክክለኛ Arabic ወደ Hebrew ትርጉም በከፍተኛ AI ኃይል ይሰጣል. አገልግሎትችን ይደግፋል:
- የጽሑፍ ትርጉም - ማንኛውንም ጽሑፍ እስከ 10,000 አርእስቶች በፍጥነት ይተረጉሙ
- ሰነዶች - የWord, PDF እና የጽሑፍ ፋይሎችን ለመተርጎም ይጫኑ
- አቀማመጥ - Arabic ወደ Hebrew ትርጉም ወደ ፕሮግራሞችዎ ጨምር
- ትርጉም - በአንድ ጥያቄ ውስጥ ብዙ ጽሑፎችን ይተረጉሙ
ጥቅሞች:
- ሰነዶችን ከ Arabic ወደ Hebrew ለቢዝነስ ተርጉም
- ድረ ገጾችንና ፕሮግራሞችን ከ Arabic ወደ Hebrew ያስተካክሉ
- ፋይል (_F)
- ከ Hebrew ተናጋሪዎች ጋር መገናኘት
ትርጉም
- ምንጭ
- ዐረብኛ (
ar) - ዓላማ
- ዕብራይስጥ (
he)
ብዙ ጊዜ የሚጠየቁ ጥያቄዎች
When both source and target are right-to-left, the model translates without inserting any left-to-right segments unless the source had Latin content (brand names, URLs) — those islands keep their original direction and are bracketed with the appropriate bidi control codes.
No — Arabic, Hebrew, Persian, and Urdu use related script families but the languages themselves are unrelated. Arabic to Hebrew is a full neural translation, not transliteration. The model is trained on bilingual corpora that pair the two languages directly where available, with English as a fallback bridge for rarer pair combinations.
Loanwords are translated to their native equivalent in Hebrew (e.g. "kitab" → the Hebrew "sefer" when going Arabic → Hebrew) unless the source clearly used the loanword as a name or quotation. Brand names always stay phonetic.
Hebrew is unicameral and uses block letterforms; Arabic and Urdu are cursive with contextual shaping (initial/medial/final/isolated). The output uses the correct script with its native rendering rules — your editor or browser handles the shaping automatically as long as the font supports it.
Vowel marks tend to be lost in translation between RTL languages because each script encodes them differently and the target writing convention often omits them. If you need fully-vocalized output for Hebrew, post-process with a vocalizer specific to that language.
Both RTL languages default to the literary / formal register (MSA for Arabic, Modern Israeli Hebrew literary, Persian rasmi, Urdu adabi). Conversational output between two RTL targets often needs a native review pass because each language has independent register conventions.
Output between two RTL languages uses the standard literary form of the target — dialect-to-dialect translation (e.g. Egyptian Arabic colloquial → spoken Persian Tehrani) is not directly supported. Translate to MSA / standard target first, then localize.
Quoted scripture (Qur'anic verses, Hebrew Bible, hadith) is preserved verbatim with original orthography when wrapped in quotation marks. Surrounding commentary is translated normally.
Calendar terms translate to the Hebrew convention (Gregorian month names if Hebrew commonly uses them, Hijri / Hebrew calendar terms where contextually appropriate). Numerals default to Latin digits in the output.
Up to 10,000 characters via the web translator and 50,000 via the API. Long-form documents in RTL pairs benefit from paragraph-sized chunks (300-1000 characters) because the model maintains discourse coherence within a chunk.
Yes — Latin segments inside an RTL document keep their left-to-right direction and Latin spelling. The model only translates the RTL prose; embedded URLs, emails, code blocks, and Latin brand names pass through unchanged.
Yes — upload an image or PDF of Arabic text and the OCR pipeline applies script-aware preprocessing so right-to-left column-and-line order is detected before translation to Hebrew. Vowel marks usually do not survive OCR; expect un-vocalized output.