This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
Microsoft owns the copyright to some fonts, including Traditional Arabic, and, quite unreasonably, refuses to let this font be embedded in a PDF file. If you make a PDF file out of a Word file that has some or all text in Traditional Arabic, you will be able to open the file and display it properly on your computer, because you already have the font installed. This font comes as part of the MS Office package, but it does not install by default. The easiest way to make sure this font is installed... See more
Microsoft owns the copyright to some fonts, including Traditional Arabic, and, quite unreasonably, refuses to let this font be embedded in a PDF file. If you make a PDF file out of a Word file that has some or all text in Traditional Arabic, you will be able to open the file and display it properly on your computer, because you already have the font installed. This font comes as part of the MS Office package, but it does not install by default. The easiest way to make sure this font is installed is to install Office in toto and then to have Arabic added in the Language Settings (in Office Tools).
If you send the PDF file to someone who has the Traditional Arabic font installed on their computer (such as another Arabic translator with a full Office installation), they will likewise be able to display the Arabic text in the PDF file. But if you send the file to someone who does not have that font installed (such as most translation agencies, virtually all clients, and even some Arabic translators), they will not be able to display the Arabic text in the PDF file, because the font is not embedded. What I normally do in these situations is switch to the second best font (Deco Type Naskh) before I make the PDF file. Line spacing adjustments (down to about 75%) may be called for because Deco Type Naskh uses oversized line spacing.
The situation is somewhat comical: On the one hand, Microsoft takes extreme measures to protect the Traditional Arabic font, indicating that Microsoft knows that this is a superior font. On the other hand, Traditional Arabic is not made the default Arabic font. Instead, some inferior Arabic font (Times New Roman or what not) is set as the default font. This is like making HYShortSamuel the standard font for English!
The part that escapes my understanding is how preventing the font from embedding in a PDF file protects the font. But that is Microsoft! ▲ Collapse
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Stephen Franke United States Local time: 00:04 English to Arabic + ...
Re traditional Arabic TTF: Microsoft strikes again
Aug 9, 2004
Greetings... taHaiya Tayyiba wa b3ad...
Fuad gives an excellent treatment of the vaguaries of some Arabic fonts and their compatability and embedded display (nor not) inside PDF.
(Re the proprietary MS "Traditional Arabic" font: Microsoft strikes again.)
Khair, in sha' Allah.
Regards,
Stephen H. Franke
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Exclusive discount for ProZ.com users!
Save over 13% when purchasing Wordfast Pro through ProZ.com. Wordfast is the world's #1 provider of platform-independent Translation Memory software. Consistently ranked the most user-friendly and highest value
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.