Page 77 - CyberSecurityEssentialsEnglish
P. 77
• Mistake to avoid: Assuming that one example represents every case, or that an
impressive role grants real expertise.
2.7 Language, Media, Decisions, and Stability
◆ Key idea: language, medium, and settings are part of the specification.
Working in Arabic, working with images and files, supporting a decision, and controlling
how much the output varies between runs are not stylistic extras. Each is a decision that
belongs in the prompt, and each has its own way of being checked.
Prompting in Arabic
State clearly whether you want standard Arabic or a specific dialect, and identify the
geographic and professional audience. If the text mixes Arabic and English, define a
terminology policy: “Write the Arabic term followed by the English term at first appearance”,
or “Keep product names in English.” This reduces inconsistent translation and disruption of
text direction.
The instruction “write in Arabic” may produce language that is correct but unsuited to the
context. Ask for a reading level, a sentence length, and whether specialist terms need
explanation. When tables or lists are produced, ask explicitly for full right-to-left layout with
list numbers on the right, then inspect the final file, because good text does not guarantee
that the application or the export preserved the direction.
For dialects, give a short example of the required tone instead of a general description such
as “write in Egyptian dialect.” A dialect varies by region, by register, and by age. Mocking
imitation and expressions unsuited to the sector should be avoided. In professional texts,
simple standard Arabic with a local touch is often safer than a full dialect.
76

