hebrew-content-writer

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Hebrew Content Writer

希伯来语内容撰写工具

Instructions

使用说明

Step 1: Identify Content Type and Register

步骤1：确定内容类型与语体

Content Type	Register	Audience	Key Characteristics
Legal / Government	Formal (gvoha)	Officials, lawyers	Passive voice, complex sentences, traditional gendering
Business / Corporate	Business	Professionals	Clear, professional, moderate formality
Marketing / Ads	Business-Casual	General public	Persuasive, benefit-focused, concise
Direct / Dugri	Dugri	Israeli general public	Blunt, no softeners, short imperative sentences
UX / Interface	Direct	End users	Imperative mood, ultra-short, action-oriented
Social Media	Informal	Young adults	Casual, slang-friendly, emoji-compatible
Blog / Article	Business	Readers	Informative, SEO-aware, structured

内容类型	语体	受众	核心特征
法律/政府类	正式语体（gvoha）	官员、律师	被动语态、复杂句式、传统性别表述
商务/企业类	商务语体	职场人士	清晰专业、适度正式
营销/广告类	商务休闲语体	普通大众	具有说服力、聚焦利益、简洁凝练
直接语体（Dugri）	Dugri	以色列普通民众	直白、无软化表述、简短祈使句
UX/界面类	直接语体	终端用户	祈使语气、极简短、行动导向
社交媒体类	非正式语体	年轻人	随意、兼容俚语与表情符号
博客/文章类	商务语体	读者	信息丰富、适配SEO、结构清晰

Step 2: Apply Hebrew Grammar Rules

步骤2：应用希伯来语语法规则

Spelling Standard -- Use Ktiv Maleh (Full Spelling): Modern Hebrew content uses ktiv maleh (plene spelling) with vav and yod for vowels:

Correct: תוכנה (tochnah) not תכנה
Correct: שירות (sherut) not שרות
Follow Academy of Hebrew Language guidelines

Smichut (Construct State) Rules:

First noun loses definite article: "beit ha-sefer" (the school) not "ha-beit ha-sefer"
First noun may change form: bayit -> beit, yom -> yom (unchanged)
Adjectives agree with the LAST noun in the chain

Direct Object Marker (et):

Required before definite direct objects: "ra'iti ET ha-sefer" (I saw the book)
NOT used with indefinite objects: "ra'iti sefer" (I saw a book)
Common mistake: omitting "et" or using it with indefinite objects

Subject-Verb Agreement:

Verbs agree in gender and number with their subject
Past tense: also agrees in person
Present tense: only gender and number (no person distinction)
Future tense: gender, number, and person

拼写标准——使用Ktiv Maleh（完整拼写）： 现代希伯来语内容采用Ktiv Maleh（完整拼写），用vav和yod表示元音：

正确写法：תוכנה (tochnah)，而非 תכנה
正确写法：שירות (sherut)，而非 שרות
遵循希伯来语学院的指导规范

Smichut（结构态）规则：

第一个名词去掉定冠词："beit ha-sefer"（学校）而非 "ha-beit ha-sefer"
第一个名词可能变形：bayit -> beit，yom -> yom（不变形）
形容词与名词链中的最后一个名词保持一致

直接宾语标记（et）：

限定直接宾语前必须使用："ra'iti ET ha-sefer"（我看到了这本书）
非限定宾语前不使用："ra'iti sefer"（我看到了一本书）
常见错误：遗漏"et"或在非限定宾语前使用它

主谓一致：

动词在性别和数上与主语一致
过去时：还需在人称上一致
现在时：仅需性别和数一致（无人称区分）
将来时：需性别、数和人称一致

Step 3: Handle Gendered Language

步骤3：处理性别化语言

Option A -- Traditional (default for formal/legal): Use masculine plural for mixed groups. Standard in government, legal, academic writing.

Option B -- Slash Notation (for business/marketing):

משתמשים/ות יקרים/ות (dear users, m/f)

Option C -- Gender-Neutral Rewording (recommended for UX/tech):

Instead of	Use
המשתמש צריך ללחוץ (the user needs to click, m.)	יש ללחוץ על (click on)
אתה יכול לבחור (you can choose, m.)	ניתן לבחור (it is possible to choose)
הלקוחות שלנו מרוצים (our customers are satisfied, m.)	שביעות רצון הלקוחות שלנו (the satisfaction of our customers)

Ask the user which approach they prefer if not specified.

选项A——传统表述（正式/法律类默认）： 混合群体使用阳性复数形式。为政府、法律、学术写作的标准用法。

选项B——斜杠标记法（商务/营销类适用）：

משתמשים/ות יקרים/ות (亲爱的用户，阳性/阴性)

选项C——性别中立改写（UX/科技类推荐）：

原表述	替代表述
המשתמש צריך ללחוץ（用户需要点击，阳性）	יש ללחוץ על（点击）
אתה יכול לבחור（你可以选择，阳性）	ניתן לבחור（可以选择）
הלקוחות שלנו מרוצים（我们的客户很满意，阳性）	שביעות רצון הלקוחות שלנו（我们客户的满意度）

若用户未指定，请询问其偏好哪种方式。

Step 4: Common Hebrew Writing Mistakes to Avoid

步骤4：需避免的希伯来语常见写作错误

Mistake	Wrong	Correct	Rule
Smichut with ha- on first noun	הבית הספר	בית הספר	Only second noun gets ha-
Missing et	ראיתי הכלב	ראיתי את הכלב	Definite direct object needs et
Wrong gender agreement	הילדה הלך	הילדה הלכה	Verb must match subject gender
Mixed ktiv	תוכנה/תכנה in same text	Pick one consistently	Use ktiv maleh throughout
Incorrect vav ha-hipukh	ואז הוא הולך	ואז הוא הלך	Vav ha-hipukh is biblical, not modern
Colloquial in formal text	נגיד ש...	לדוגמה...	Match register to context

错误类型	错误写法	正确写法	规则
第一个名词带ha-的Smichut结构	הבית הספר	בית הספר	仅第二个名词加ha-
遗漏et	ראיתי הכלב	ראיתי את הכלב	限定直接宾语需要et
性别一致错误	הילדה הלך	הילדה הלכה	动词必须与主语性别匹配
混合拼写	同一文本中混用תוכנה/תכנה	统一使用一种拼写	全程使用Ktiv Maleh
错误使用vav ha-hipukh	ואז הוא הולך	ואז הוא הלך	vav ha-hipukh为圣经用语，不适用于现代希伯来语
正式文本使用口语化表达	נגיד ש...	לדוגמה...	语体需与语境匹配

Step 5: Hebrew SEO Optimization

步骤5：希伯来语SEO优化

Keyword Strategy:

Research keywords in Hebrew using Google Keyword Planner (region: Israel)
Account for morphological variations -- target root words and common forms
Example: "ביטוח" (insurance) also search "ביטוחים", "לבטח", "מבוטח"
Consider bilingual searches -- Israelis search English for tech terms

On-Page SEO for Hebrew:

Title tag: 50-60 Hebrew characters, primary keyword near beginning
Meta description: 120-150 characters, compelling call-to-action
H1: One per page, contains primary keyword
URL slug: Transliterated Hebrew ("bituach-briut") or English equivalent
Alt text: Descriptive Hebrew text for images
Internal linking: Use Hebrew anchor text

Content Structure:

Use short paragraphs (2-3 sentences) -- Hebrew text appears denser than English
Use headers (H2, H3) every 200-300 words
Bulleted lists improve readability in Hebrew
Bold key terms for scanning

关键词策略：

使用Google Keyword Planner（地区选择以色列）研究希伯来语关键词
考虑形态变化——针对词根和常见形式
示例："ביטוח"（保险）相关搜索还包括"ביטוחים"、"לבטח"、"מבוטח"
考虑双语搜索——以色列人会用英语搜索科技术语

希伯来语页面SEO：

标题标签：50-60个希伯来字符，核心关键词靠近开头
元描述：120-150个字符，包含有吸引力的行动号召
H1：每页一个，包含核心关键词
URL slug：希伯来语转写（如"bituach-briut"）或英文对应词
替代文本：图片的描述性希伯来语文本
内部链接：使用希伯来语锚文本

内容结构：

使用短段落（2-3句话）——希伯来语文本看起来比英语更密集
每200-300字使用标题（H2、H3）
项目符号列表提升希伯来语内容可读性
加粗关键术语便于快速浏览

Step 6: Write in the Dugri (Direct) Register

步骤6：使用直接语体（Dugri）写作

"Dugri" is the blunt, no-nonsense register Israelis use and expect in everyday speech and increasingly in product copy, support replies, and startup marketing. It is a distinct mode, not just "informal" - it can be polite and still completely direct. Use it when the brand voice is plain-spoken or when softening would feel evasive to an Israeli reader.

How to write dugri:

Drop English-style softeners. Cut "we would be happy to", "it might be worth considering", "please feel free to". Say the thing.
Short sentences, one idea each. Long subordinate clauses read as bureaucratic.
Second-person imperative is fine and friendly: "תשלחו לנו את המספר" (send us the number), "תבדקו את זה" (check this).
Lead with the point, then the reason - not the other way around.
Dugri is not rude. It still uses "תודה" and basic courtesy; it just refuses to pad.

Padded (avoid)	Dugri (use)
נשמח אם תוכלו לשקול לעדכן את הפרטים	תעדכנו את הפרטים
ייתכן שכדאי לבדוק את החיבור לאינטרנט	תבדקו את החיבור לאינטרנט
אנחנו מתנצלים על אי הנוחות שנגרמה	סליחה על העיכוב. תיקנו את זה

"Dugri"是以色列人日常对话中使用的直白、务实语体，如今也越来越多地用于产品文案、支持回复和初创企业营销。它是一种独特的语体，并非只是“非正式”——它可以礼貌且完全直白。当品牌风格为直言不讳，或软化表述会让以色列读者觉得回避时，使用该语体。

如何撰写Dugri风格内容：

去掉英语式软化表述。删掉“我们很乐意”、“或许值得考虑”、“请随时”等表述，直接说重点。
短句，每句表达一个想法。长从句会显得官僚化。
第二人称祈使句友好且合适："תשלחו לנו את המספר"（把号码发给我们）、"תבדקו את זה"（检查这个）。
先讲重点，再讲原因——不要反过来。
Dugri并不粗鲁。它仍会使用"תודה"（谢谢）等基本礼貌用语，只是拒绝冗余铺垫。

冗余表述（避免）	Dugri表述（使用）
נשמח אם תוכלו לשקול לעדכן את הפרטים	תעדכנו את הפרטים
ייתכן שכדאי לבדוק את החיבור לאינטרנט	תבדקו את החיבור לאינטרנט
אנחנו מתנצלים על אי הנוחות שנגרמה	סליחה על העיכוב. תיקנו את זה

Step 7: Handle Mixed Hebrew/English (Heblish)

步骤7：处理希伯来语/英语混合（Heblish）

Israeli writing routinely mixes Hebrew and English, especially in tech, marketing, and business copy. The decision for each English term is keep, transliterate, or translate:

Keep in English - established tech/product terms with no natural Hebrew equivalent in daily use: API, SaaS, deploy, dashboard (often), email (though "אימייל"/"מייל" is also common). Brand and product names always stay in English.
Transliterate - terms that have entered spoken Hebrew phonetically: "אימייל", "סטארטאפ", "פינטק", "באג", "פיצ'ר". Use when the transliteration is what people actually say.
Translate - terms with a well-established Hebrew word the audience uses: "תוכנה" (software), "משתמש" (user), "הורדה" (download), "עדכון" (update). Forcing English here reads as lazy.

RTL/LTR mixing in one line:

An English term inside a Hebrew sentence keeps its LTR run; the browser's bidi algorithm usually handles a single word, but wrap longer English strings, codes, or anything with punctuation in
```
<bdi>
```
or
```
dir="ltr"
```
so surrounding Hebrew punctuation does not reorder.
Keep a space on both sides of the English run.

English nouns taking Hebrew grammar:

Hebrew plural: Israelis routinely add Hebrew plural endings to English nouns - "באגים" (bugs), "לינקים" (links), "פיצ'רים" (features). This is natural; do not "correct" it to English plurals.
Definite article: the Hebrew "ה־" attaches to the English noun - "האפ" (the app), "הלינק" (the link), "הדשבורד" (the dashboard).
Gender: assign the English noun a Hebrew gender consistently (usually masculine by default) so verbs and adjectives agree - "הדשבורד נטען" not "הדשבורד נטענה".

以色列写作通常混合希伯来语和英语，尤其是在科技、营销和商务文案中。对于每个英语术语，需决定保留原文、转写还是翻译：

保留英文——日常使用中没有自然希伯来语对应词的成熟科技/产品术语：API、SaaS、deploy、dashboard（通常）、email（不过"אימייל"/"מייל"也很常见）。品牌和产品名称始终保留英文。
转写——已进入希伯来语口语的术语："אימייל"、"סטארטאפ"、"פינטק"、"באג"、"פיצ'ר"。当转写形式是人们实际使用的说法时采用。
翻译——受众普遍使用的成熟希伯来语对应词："תוכנה"（software）、"משתמש"（user）、"הורדה"（download）、"עדכון"（update）。强行使用英语会显得敷衍。

同一行中的RTL/LTR混合：

希伯来语句子中的英文术语保持LTR排版；浏览器的双向算法通常能处理单个单词，但较长的英文字符串、代码或带标点的内容需用
```
<bdi>
```
或
```
dir="ltr"
```
包裹，避免周围希伯来语标点错位。
英文内容两边保留空格。

英文名词适配希伯来语语法：

希伯来语复数：以色列人通常给英文名词加希伯来语复数后缀——"באגים"（bugs）、"לינקים"（links）、"פיצ'רים"（features）。这是自然用法，不要“纠正”为英文复数。
定冠词：希伯来语"ה־"附加在英文名词上——"האפ"（the app）、"הלינק"（the link）、"הדשבורד"（the dashboard）。
性别：为英文名词统一分配希伯来语性别（通常默认阳性），使动词和形容词保持一致——"הדשבורד נטען"而非"הדשבורד נטענה"。

Step 8: Nikud, Numerals, and Dates

步骤8：元音符号（Nikud）、数字与日期

When to add nikud (vowel points):

Children's content, early-reader material, songs, poetry.
A single ambiguous word where context does not disambiguate (e.g., to distinguish "סֵפֶר" from "סַפָּר").
Foreign names and unfamiliar loanwords on first mention.

When to omit nikud:

Modern body copy, UI text, marketing, articles - standard unvocalized Hebrew. Adding nikud throughout looks like a textbook and slows fluent readers.

Numerals and dates:

In running body copy, prefer digits for most numbers ("3 ימים", "תוך 24 שעות"); spelling out is reserved for formal/legal text or numbers that open a sentence.
Number-gender agreement for 1-10: Hebrew numbers take the OPPOSITE gender form of the noun they count (a known trap). With a masculine noun use the feminine-form number: "שלושה ימים" (three days, masc. noun). With a feminine noun use the masculine-form number: "שלוש שנים" (three years, fem. noun).
Dates follow Israeli convention
```
DD/MM/YYYY
```
and 24-hour time. See
```
israeli-ui-design-system
```
for formatting in UI components.
Hebrew quotation marks: Hebrew uses the same
```
"
```
for quotation in practice, but note that gershayim
```
"
```
and geresh
```
'
```
are reserved for acronyms (צה"ל) and abbreviations - do not let them double as quote marks in the same span.

何时添加nikud（元音符号）：

儿童内容、初级读物、歌曲、诗歌。
单义词存在歧义且语境无法区分时（例如区分"סֵפֶר"和"סַפָּר"）。
首次提及的外国名字和陌生外来词。

何时省略nikud：

现代正文、UI文本、营销内容、文章——标准无元音希伯来语。全程添加nikud会像教科书一样，减慢流利读者的阅读速度。

数字与日期：

正文内容中，大多数数字优先使用阿拉伯数字（"3 ימים"、"תוך 24 שעות"）；拼写数字仅用于正式/法律文本或句首数字。
1-10的数字性别一致：希伯来语数字与所修饰名词的性别相反（常见陷阱）。修饰阳性名词使用阴性形式数字："שלושה ימים"（三天，阳性名词）。修饰阴性名词使用阳性形式数字："שלוש שנים"（三年，阴性名词）。
日期遵循以色列格式
```
DD/MM/YYYY
```
，时间采用24小时制。UI组件格式请参考
```
israeli-ui-design-system
```
。
希伯来语引号：实际使用中希伯来语用
```
"
```
表示引号，但gershayim
```
"
```
和geresh
```
'
```
专用于缩写（צה"ל）和简称——不要在同一文本段中让它们同时充当引号。

Step 9: Literal-Translation Pitfalls

步骤9：直译陷阱

Calques from English produce text that is grammatical but unmistakably translated. Watch for:

Pitfall	Wrong (calque)	Natural Hebrew
"to make sense" translated word-for-word	זה עושה סנס / זה עושה שכל	זה הגיוני / זה מסתדר
Over-using generic "אתה" for impersonal "you"	אתה צריך ללחוץ, אתה יכול לראות	יש ללחוץ, אפשר לראות
"בכדי" used where plain "כדי" belongs	בכדי לשמור את הקובץ	כדי לשמור את הקובץ
Redundant "את ה־" stacking after a preposition	להתחבר את החשבון	לחבר את החשבון / להתחבר לחשבון
Literal "at the end of the day"	בסוף היום	בסופו של דבר / בשורה התחתונה

"בכדי" is not wrong in every context, but it is overused as a fancier-looking "כדי"; default to plain "כדי".

从英语直译会产生语法正确但明显是翻译腔的文本。需注意：

陷阱	错误直译	自然希伯来语表达
"to make sense"逐字翻译	זה עושה סנס / זה עושה שכל	זה הגיוני / זה מסתדר
过度使用泛指"אתה"对应非人称"you"	אתה צריך ללחוץ, אתה יכול לראות	יש ללחוץ, אפשר לראות
误用"בכדי"代替普通"כדי"	בכדי לשמור את הקובץ	כדי לשמור את הקובץ
介词后冗余叠加"את ה־"	להתחבר את החשבון	לחבר את החשבון / להתחבר לחשבון
直译"at the end of the day"	בסוף היום	בסופו של דבר / בשורה התחתונה

"בכדי"并非在所有语境中都错误，但它常被当作更“高级”的"כדי"过度使用；默认使用普通"כדי"即可。

Examples

示例

Example 1: Marketing Email

示例1：营销邮件

User says: "Write a Hebrew marketing email for a SaaS product launch" Result: Write business-register Hebrew email with compelling subject line, benefit-focused body, clear CTA. Apply SEO principles if it will be a web version. Use gender-inclusive language.

用户需求：“为SaaS产品发布撰写希伯来语营销邮件” 结果：撰写商务语体希伯来语邮件，包含吸引人的主题、聚焦利益的正文、清晰的行动号召。若为网页版本，需应用SEO原则。使用性别包容性语言。

Example 2: UX Error Message

示例2：UX错误提示

User says: "Write Hebrew error messages for a login form" Result: Write short, clear, action-oriented Hebrew text in imperative mood. Use neutral/inclusive phrasing. Examples: "הסיסמה שגויה. יש לנסות שנית" (The password is incorrect. Please try again).

用户需求：“为登录表单撰写希伯来语错误提示” 结果：撰写简短清晰、行动导向的希伯来语文本，使用祈使语气。采用中立/包容性表述。示例："הסיסמה שגויה. יש לנסות שנית"（密码错误，请重试）。

Example 3: SEO Blog Post

示例3：SEO博客文章

User says: "Write a Hebrew blog post about cloud security for Israeli businesses" Result: Research Hebrew keywords, write structured article with proper H2/H3 hierarchy, include meta description, use ktiv maleh throughout, business register.

用户需求：“为以色列企业撰写关于云安全的希伯来语博客文章” 结果：研究希伯来语关键词，撰写结构清晰的文章，设置合理的H2/H3层级，包含元描述，全程使用Ktiv Maleh拼写，采用商务语体。

Example 4: Gender-Inclusive Rewrite

示例4：性别包容性改写

User says: "Make this Hebrew text gender-inclusive" Result: Identify gendered forms, apply Option C rewording where possible, use slash notation where rewording is awkward, maintain readability and register.

用户需求：“让这段希伯来语文本具有性别包容性” 结果：识别性别化表述，尽可能应用选项C的改写方式，改写困难时使用斜杠标记法，保持可读性和语体一致。

Bundled Resources

配套资源

References

参考资料

```
references/hebrew-grammar-quick-ref.md
```
- Concise Hebrew grammar reference covering all 7 binyanim (verb patterns) with usage guidance by register, ktiv maleh vs. ktiv chaser spelling examples, common smichut (construct state) forms, and four gender-inclusive writing patterns with before/after examples. Consult when writing or editing Hebrew content and need to verify grammar rules, choose the correct register, or apply gender-neutral phrasing.

```
references/hebrew-grammar-quick-ref.md
```
——简明希伯来语语法参考，涵盖所有7种binyanim（动词模式）及语体使用指导、Ktiv Maleh与Ktiv Chaser拼写示例、常见Smichut（结构态）形式，以及四种性别包容性写作模式的前后对比示例。撰写或编辑希伯来语内容时，若需验证语法规则、选择合适语体或应用性别中立表述，可查阅此资料。

Gotchas

注意事项

Agents default to formal/literary Hebrew (safa gvoha) when writing marketing or UI text. Israeli users expect casual, conversational Hebrew. Use colloquial phrasing, not textbook Hebrew.
Hebrew punctuation differs from English: the geresh (') and gershayim (") are used for abbreviations (e.g., tsahal) and acronyms, not for quotation. Agents may strip these or replace them with standard ASCII quotes.
Agents tend to transliterate English idioms literally into Hebrew, producing unnatural text. "Think outside the box" does not translate directly; use native Hebrew expressions instead.
Hebrew has grammatical gender that must agree between nouns, verbs, and adjectives. Agents often use masculine defaults even when addressing a female user or a feminine noun.

工具默认使用正式/文学希伯来语（safa gvoha）撰写营销或UI文本，但以色列用户更偏好随意、口语化的希伯来语。请使用口语化表述，而非教科书式希伯来语。
希伯来语标点与英语不同：geresh (')和gershayim (")用于缩写（如tsahal）和首字母缩略词，而非引号。工具可能会删除这些符号或替换为标准ASCII引号。
工具倾向于将英语习语直译为希伯来语，导致文本不自然。例如“Think outside the box”不能直接翻译，需使用希伯来语本土表达。
希伯来语有语法性别，名词、动词和形容词必须保持一致。工具常使用阳性默认形式，即使针对女性用户或阴性名词也是如此。

Reference Links

参考链接

Source	URL	What to Check
Academy of the Hebrew Language	https://hebrew-academy.org.il	Official spelling rules, loanword decisions, new terms
Milog online dictionary	https://milog.co.il	Modern Hebrew usage, register, common phrasing
Ravmilim online dictionary	https://www.ravmilim.co.il	Synonyms, collocations, grammatical info
Kotar HaKeshet	https://hebrew-academy.org.il/topic/hahlatot/	Academy decisions on grammar and terminology
Hebrew style guide (Wikipedia)	https://he.wikipedia.org/wiki/ויקיפדיה:מדריך_הסגנון	Community-maintained modern Hebrew style conventions

来源	URL	查阅内容
希伯来语学院	https://hebrew-academy.org.il	官方拼写规则、外来词判定、新术语
Milog在线词典	https://milog.co.il	现代希伯来语用法、语体、常见表述
Ravmilim在线词典	https://www.ravmilim.co.il	同义词、搭配、语法信息
Kotar HaKeshet	https://hebrew-academy.org.il/topic/hahlatot/	学院关于语法和术语的决议
希伯来语风格指南（维基百科）	https://he.wikipedia.org/wiki/ויקיפדיה:מדריך_הסגנון	社区维护的现代希伯来语风格规范

Troubleshooting

故障排除

Error: "Text mixes formal and informal registers"

错误：“文本混合正式与非正式语体”

Cause: Inconsistent tone throughout the content Solution: Identify the target register at the start and apply it consistently. Common issue when multiple writers contribute or when translating from English.

原因：内容语体不一致解决方案：一开始就确定目标语体并保持一致。多作者撰稿或从英语翻译时常见此问题。

Error: "SEO keywords don't match Hebrew search patterns"

错误：“SEO关键词不符合希伯来语搜索模式”

Cause: Direct translation of English keywords to Hebrew Solution: Use Google Keyword Planner with Israel region. Hebrew search patterns differ from English -- Israelis may search differently than direct translations suggest.

原因：将英语关键词直接翻译为希伯来语解决方案：使用地区为以色列的Google Keyword Planner。希伯来语搜索模式与英语不同——以色列人的搜索方式可能与直译结果不同。