Ebre pou Pèsik Tradiksyon
HE FA
Resultats instantanés
API disponib
Tradiksyon...
Tradiksyon an ap parèt isit la...
Enskri pou Tradwi Fichye
Kreye yon kont gratis pou tradui dokiman, sous-titres, ak plis ankò.
Enskri pou gratis KoneksyonKijan pou tradui Hebrew nan Persian
1
Enter Your Text
Tape oswa kole tèks Hebrew ou nan bwat antre ki anwo a. Ou ka antre jiska 10,000 karaktè, oswa telechaje yon dokiman.
2
Klike Tradwi
Klike sou bouton an Tradiksyon oswa jis tann - oto-tradiksyon kicks nan apre ou sispann tape. AI ap trete tèks ou nan milisèk.
3
Kopye Tradiksyon ou
Tradiksyon ou a Persian ap parèt imedyatman. Klike sou bouton kopi a pou kopye li nan bwat resepsyon ou, oswa enkòpore li via API nou an.
Fraz komen Hebrew
Klike sou nenpòt fraz pou tradui li imedyatman.
Tradiksyon imedyat
Get Hebrew to Persian translations in milliseconds.
Sipò Dokiman
Upload Word, PDF, SRT sous-titres ak plis ankò pou tradiksyon batch.
Akses API
Intégrer sa a pè tradiksyon nan aplikasyon ou ak REST API nou an.
Hebrew to Persian API
Ajoute konbinezon tradiksyon sa a nan aplikasyon w lan ak yon apèl API senp.
View API Docs Obtenir la clé APIcurl -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": "he", "target_language": "fa"}'Sou tradiksyon Hebrew a Persian
TranslateAPI bay yon tradiksyon rapid ak egzat de Hebrew a Persian ki sipòte pa AI avanse.
- Tradiksyon tèks - Tradwi nenpòt tèks jiska 10,000 karaktè imedyatman
- Tradiksyon Dokiman - Upload Word, PDF, ak dosye tèks pou tradiksyon
- Entègrasyon API - Ajoute tradiksyon Hebrew a Persian nan aplikasyon ou yo
- Tradiksyon - Tradwi plizyè tèks nan yon sèl demann
Ka itilizasyon:
- Tradiksyon Hebrew dokiman nan Persian pou biznis
- Lokalize sit entènèt ak aplikasyon soti nan Hebrew nan Persian
- Konvèti Hebrew sous-titres pou Persian
- Kominike ak Persian pale
Pair Tradiksyon
- Fonksyon
- Ebre (
he) - Target
- Pèsik (
fa)
Kesyon ki poze souvan
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. Hebrew to Persian 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 Persian (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 Persian, 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 Persian convention (Gregorian month names if Persian 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 Hebrew text and the OCR pipeline applies script-aware preprocessing so right-to-left column-and-line order is detected before translation to Persian. Vowel marks usually do not survive OCR; expect un-vocalized output.