Style combination · Pairs well
Machine-Age Simplified Arabic Type × Roman-like Thai Typography
A parallel machine-age simplification of another script; both strip traditional details to an even, rational line, and both stayed contested for long reading.
Mix them and make something Machine-Age Simplified Arabic Type Roman-like Thai Typography
01
What each style brings
Each part of the design comes from the style with the stronger say in it, and each style gives at least two.
Machine-Age Simplified Arabic Type Roman-like Thai Typography (modern loopless Thai)
- Type from Roman-like Thai Typography
- Colour from Roman-like Thai Typography
- Form from Machine-Age Simplified Arabic Type
- Composition from Machine-Age Simplified Arabic Type
- Surface from Machine-Age Simplified Arabic Type
02
The type
Open fonts standing in for each style’s own type, which is often hand-drawn or commercial.
Display · Roman-like Thai Typography
Orbit
Inter Tight, standing in for Helvetica, the Latin model for Manoptica
Text · Machine-Age Simplified Arabic Type
Arabic redrawn for the machine rather than the reed pen. From 1947 reformers cut down the four positional forms of each letter: Nasri Khattar's Unified Arabic gave every letter one shape, set apart like Latin type in its detached print form, and Linotype's Simplified Arabic (1959, made with Beirut's al-Hayat) mostly two, so a newspaper fount fitted one 90-channel magazine; ASV Codar in Morocco gave the vowels letters of their own. Flat-based, even and with few ligatures, it became the common face of Arab newspapers and lives on in Windows system fonts.
Newsreader; Machine-Age Simplified Arabic Type used Mrowa-Linotype Simplified Arabic (Kamel Mrowa, Nabih Jaroudi and Walter Tracy for Linotype & Machinery; Series 2 with 3, 1959) and its redesign by Jaroudi, Series 8 with 9 (1962), named Yakout in 1967 and Intertype Abridged Arabic
03
The colours
The ground and leading colours come from Roman-like Thai Typography, with a counter-accent from Machine-Age Simplified Arabic Type. The ink reads on the ground at 4.5:1 or more.
Machine-Age Simplified Arabic Type Roman-like Thai Typography (modern loopless Thai)
-
#f6f5f1ground · 36% -
#141414ink · 14% -
#f5b800accent · 18% -
#1d4f9eaccent · 14% -
#d6242aaccent · 10% -
#cfc6b0accent · 8%
As CSS
:root {
--ground: #f6f5f1;
--ink: #141414;
--accent-1: #f5b800;
--accent-2: #1d4f9e;
--accent-3: #d6242a;
--accent-4: #cfc6b0;
--font-display: "Inter Tight", sans-serif;
--font-text: "Newsreader", serif;
}
Use it with care
Machine-Age Simplified Arabic Type: Arabic is a living script and the script of the Qur'an, and simplified type was long resisted for books, government work and the Qur'an, so do not set Qur'anic verses, hadith or the names of God and the Prophet in reduced or detached forms, or use them as texture. Set Arabic right to left with correct joining, never pass off the disconnected letters of a software error as Unified Arabic, have every word read by a fluent reader, and do not present script reform as the correction of a deficient script: the Academy of the Arabic Language in Cairo rejected ASV Codar in 1958, and the type historian Titus Nemeth calls the survival of simplified forms in digital fonts a legacy of technical compromise that digital type no longer needs.
Roman-like Thai Typography (modern loopless Thai): Loopless Thai is contested inside Thailand. Researchers such as Rachapoom Punsongserm find it harder to read in small, bold or justified body text and less legible across viewing distances than a Thai universal-design face, with letters that can be taken for Latin (พ.ร.บ. can read as W.S.U.), so keep it mostly to display sizes and set body, legal and small interface text in a looped face. Critics also see it as eroding the looped forms that mark Thai identity, and Cadson Demak, which popularised it, has since turned back towards looped faces. Have every Thai word checked by a fluent reader, since image models invent or garble Thai letters, and never pass shaped Latin letters off as Thai.
04
The two styles
05
More combinations
With Machine-Age Simplified Arabic Type
- Contemporary Arabic & Dual-Script Type Design Pairs well · Its digital successor: dual-script families pair Arabic with a matched Latin while keeping the firm baseline, even colour and reduced stacking that simplification made familiar. 29LT's UA Neo (2013), detached revivals of Khattar's Unified Arabic, is where the two touch.
- Bulaq (Amiriyya) Naskh Book Printing Contrasts · The full calligraphic repertoire it gave up: a Bulaq-style Naskh title over simplified body text shows exactly what was traded for speed and economy.
- Cairo–Beirut Arab Modernist Book & Periodical Design Pairs well · Same cities and decades: hand-drawn Arabic titles and flat offset illustration give a warmer face to magazine and periodical pages whose body text was often set in simplified type (books were slower to accept it).
- Urdu Katib Lithography Contrasts · Urdu made the opposite choice, keeping the katib's hand because metal type could not carry Nastaʿlīq; set side by side they show economy against calligraphic fidelity.
With Roman-like Thai Typography
- Hand-Painted Signage & Vernacular Lettering Contrasts · A hand-painted shopfront sign, in looped letters or broad-nib Naris, beside a flat loopless headline shows the shift from the letterer's hand to dry transfer and digital type that Manop Srisomporn himself made.
- Out-of-Square Hangul Typography Pairs well · Both modernise an Asian script by dropping a defining convention, the square cell in Hangul and the head loop in Thai; set them together for a pan-Asian modern type specimen or festival identity.
- Thai Yantra (Yant) Diagrams Contrasts · Yantras keep hand-drawn Khom letters in sacred, protective diagrams; loopless Thai is secular, standardised and commercial, so never use a yantra as a decorative foil for it.
- Contemporary Arabic & Dual-Script Type Design Pairs well · Both redraw a non-Latin script to sit beside a Latin sans as an equal; dual-script Arabic keeps its calligraphic structure, while loopless Thai changes the letter itself, so pair them in a multiscript identity only with native readers for each script.