Search/Write and Edit Arabic Work Documents in Clear Standard Arabic

Write and Edit Arabic Work Documents in Clear Standard Arabic

Use when writing, translating, or checking Arabic letters, reports, or meeting notes. It asks about readers and region, then handles standard Arabic, spelling, punctuation, right-to-left layout, numbers, and dates, and checks in stages.

To use this AI rule
## Before Writing, Confirm Who Reads It and Which Arabic to Use Set the communication conditions before drafting. Arabic varies by audience, region, medium, and purpose, so do not apply a rule without understanding the context it serves. - Identify the document purpose, intended readers, desired action, channel, and publication risk. - Confirm the required Arabic variety, regional conventions, and any approved institutional terminology. - Determine whether the content is original Arabic, translation, localization, or bilingual material. - List facts, names, quotations, legal wording, and technical terms that require verification. - Separate mandatory house rules from linguistic preferences and writer choices. - Record unresolved questions and obtain a decision before they affect repeated wording. - Do not invent an organization-specific rule when no approved source exists. ## Write in Modern Standard Arabic Without Ornate or Slangy Wording Write in contemporary standard Arabic unless the assignment explicitly requires another variety. Aim for language that is correct and professional without becoming ornate, archaic, vague, or needlessly colloquial. - Match formality, directness, and technical depth to the readers and the communication goal. - Prefer familiar precise words over impressive but obscure alternatives. - Keep the institutional voice stable across headings, body text, captions, and calls to action. - Address readers respectfully without excessive ceremony or rhetorical inflation. - Avoid slogans, exaggeration, and emotional claims unless the genre genuinely requires them. - Preserve the writer's intended emphasis while removing ambiguity and unnecessary repetition. - If a deliberate register shift is useful, make it controlled and easy to justify. ## Put the Main Point First and Use Headings That Describe the Content Build a visible information hierarchy before polishing sentences. Arabic readers should be able to identify the purpose, main point, supporting evidence, and required action without reconstructing the argument. - Give each section one clear job and arrange sections in a logical progression. - Put the most important conclusion, request, or decision near the beginning when the genre permits. - Use informative headings that describe content rather than decorative labels. - Keep paragraphs focused on one main idea and connect them with explicit transitions. - Use lists when items are parallel, comparable, or procedural; do not fragment a continuous argument. - Place conditions, exceptions, and qualifications next to the statement they limit. - Remove duplicated background and details that do not change understanding or action. ## Keep Subjects, Verbs, and Agreement Clear in Long Arabic Sentences Make relationships between verbs, subjects, objects, modifiers, pronouns, and coordinated elements unmistakable. Correct individual words do not rescue a sentence whose structure obscures responsibility or scope. - Keep the subject and its verb easy to identify, especially in long or interrupted sentences. - Maintain appropriate agreement in gender, number, definiteness, and case where it is expressed. - Place modifiers close to what they describe and ensure pronouns have a single clear antecedent. - Use conjunctions and prepositions according to their actual grammatical relationship. - Distinguish alternatives, additions, causes, conditions, contrasts, and results explicitly. - Break sentences when nested clauses or parenthetical material overload working memory. - Read the revision as a whole to ensure a local correction did not change the intended meaning. ## Spell Hamza, Alif, and Ta Marbuta by One Standard Use one approved orthographic standard throughout the document. Treat spelling choices as meaning-bearing conventions, not cosmetic substitutions. - Distinguish the forms and positions of hamza according to the word and grammatical context. - Write initial and final alif forms, ya forms, ta marbuta, and related endings consistently. - Apply tanwin and case endings only where the publication standard requires them. - Add diacritics selectively to prevent ambiguity, guide pronunciation, or protect a proper name. - Do not over-vocalize ordinary prose when it would add visual noise without resolving meaning. - Verify easily confused roots, particles, attached forms, and conventional spellings in an approved reference. - Preserve intentional orthographic distinctions when editing imported or quoted material. ## Check Punctuation and Right-to-Left Display in the Final Layout Use punctuation to show logic, boundaries, and voice rather than to imitate the source language mechanically. Review the rendered right-to-left result, not only the underlying text. - End complete statements consistently and use commas to separate related units without chaining whole paragraphs. - Use colons for explanations or lists, semicolons for closely related independent units, and question marks only for genuine questions. - Pair quotation marks, brackets, and parentheses correctly and keep quoted content distinct from editorial additions. - Introduce quotations accurately, identify omissions or clarifications, and preserve the quoted meaning. - Check mixed Arabic and Latin text for ordering problems around punctuation, numbers, symbols, and links. - Keep list punctuation and capitalization conventions consistent within the chosen style. - Inspect headings, tables, captions, footnotes, and page breaks in the final layout. ## Write Numbers, Dates, and Currency Consistently Without Changing Values Choose numeric conventions for the audience and apply them consistently. Never change a value while changing its presentation. - Decide when to use words, Arabic-script digits, or Latin digits according to genre and locale. - Preserve decimal values, signs, ranges, percentages, ratios, and thousands grouping exactly. - Use an unambiguous date order and state the calendar system when confusion is possible. - Distinguish clock time from duration and include the time zone when readers may be in different regions. - Place currency codes or symbols consistently and retain the original monetary value. - Use approved measurement symbols and keep a consistent space between a value and its unit. - Recalculate or convert values only when authorized, and verify the conversion independently. ## Keep a Term List for How Names and Foreign Words Are Written Maintain an approved terminology record so the same concept is not translated, transliterated, or spelled differently across documents. Treat names and technical terms as controlled data. - Verify the official Arabic form of organizations, people, places, products, and standards. - When no official form exists, use a documented transliteration policy suited to the target locale. - Decide whether a foreign term should be translated, transliterated, retained, or paired with an explanation. - Keep related technical terms distinct even when everyday language treats them as synonyms. - Define abbreviations at first use unless the audience can reliably recognize them. - Record preferred terms, prohibited variants, context notes, and the evidence supporting each choice. - Escalate legal names, disputed terms, and high-impact terminology instead of guessing. ## Shape the Structure for Letters, Meeting Notes, or Reports Preserve the shared language rules while adapting structure to the document's function. A memo, letter, meeting record, and analytical report require different evidence and decision cues. - For correspondence, make the subject, recipient, purpose, requested action, and response path explicit. - For follow-up messages, reference the earlier communication and state what has changed. - For meeting records, distinguish attendance, discussion, decisions, owners, deadlines, and open issues. - For reports, define the question, scope, method, evidence, findings, limitations, and recommendations. - Separate observed facts from interpretation, and interpretation from proposed action. - Use forms of address and role titles that match the recipient and current approved convention. - Apply templates as structural aids; do not preserve irrelevant boilerplate or stale facts. ## Before Release, Check Meaning, Language, and Layout in Separate Passes Use a staged review that separates meaning, language, factual accuracy, and presentation. A single undifferentiated proofreading pass is not sufficient for high-impact content. - First verify purpose, completeness, factual claims, names, quotations, and numerical values. - Then review structure, logic, terminology, grammar, orthography, and punctuation. - Compare translated or localized text with the source for omissions, additions, and scope changes. - Inspect the final rendered artifact for directionality, typography, links, tables, and page flow. - Record material changes, reviewer decisions, approved exceptions, and unresolved risks. - Obtain the required subject, legal, or publication approval before release. - Update the style record from recurring decisions, but do not convert one exception into a general rule.