|
OS X Update: check here.
| The Jaghbub font packageThis is a set of fonts for use in Middle Eastern languages transliterated to the Latin script. They have the most common diacritics used in transliteration of Arabic and Persian in various transliteration / transcription formats. The fonts are modifications of standard Times, Helvetica and Palatino, and will print on any printer in a quality similar to those fonts. Included in the package are keyboard layouts to facilitate typing in these fonts, and various tools based on them.
A sample of the Jaghbub font: There are three TrueType fonts in the normal range of Roman, Bold, Italics and BoldItalics. They are:
In the following the complete set is described as the "Jaghbub package". The three fonts share the same characters, so that a text written in one of them can be changed to any other of the three with all diacritics intact. Unicode or not Unicode The font package comes in two versions. One follows the font standard called Unicode. This is a standard shared with Windows, so it makes exchanging documents with Windows users easier. It can be used with Mac OS X programs that support Unicode, such as Microsoft Word 2004, Nisus Writer Express, AbiWord, and others, but not with older Mac applications. It is called JaghbUni. The other, called Jaghbub, does not follow Unicode, and can thus be used with any Mac application, Classic, OS 9, or OS X. Each of these packages is accompanied with a keyboard layout for easy typing in each type of fonts. There is no absolute answer to which version you should pick. Unicode
is certainly the format of the future, and if you use mainly e.g. Microsoft
Office 2004, JaghbUni is probably the best alternative.
But many other Mac applications still cannot display Unicode diacritics,
so for these the "classic" Jaghbub fonts are
the only option. You can also install both, for different purposes. DownloadsThe fonts are packaged in the following files:
For Windows versions, see below InstallationThe files are packed as .zip files, and should open directly into a folder. (*) Install the fonts using either FontBook or by placing them in their appropriate
Fonts folder. Remember to make Jaghbub available to Classic, if you use
this. For more details, see the ReadMe files of each package -- (*) Older versions of StuffIt Expander have problems with zip files. If you find e.g. that the folder you downloaded appears to be empty, upgrade StuffIt Expander to version 9 or higher. (Safari may also download correctly) -- Details on the packageThe fonts contain these characters:
These last diacritics are simply characters without spacing. Thus their placement under / above another character will be approximate and often off-centre. It is thus advisable to use the complete characters above for optimal quality. With the fonts follows a keyboard layout that places the diacritics in relatively logical places. E.g., for typing emphatic s, press the Option key + s; for long a, press Option + a, etc. Similar keyboards exist for other nationalities, in the "JaghbAdd" supplementary package. (See also the enclosed table showing the Jaghbub diacritics with the Arabic characters they may correspond to.) These fonts are provided free from all restrictions in both directions: anyone (with a Mac) may use them to whatever purpose s/he wants (short of selling them!), and I take no responsibilty for them -- they are presented "as is".
"Old" and "new" versions of JaghbubThe two versions of Jaghbub - the Unicode JaghbUni and the "classic Jaghbub" - are mutually incompatible, that is: an s/dot under in classic Jaghbub will appear as ß in JaghbUni; a JaghbUni s/dot under as nothing in Jaghbub. They do not follow the same system for their diacritics. "Classic" Jaghbub works everywhere on the Mac, so for simplicity you can simply choose this and be done with it. End of problem. However, the newer JaghbUni has some advantages that you will then forgo: Because Windows also uses the Unicode standard, a text written in JaghbUni will move effortlessly to Windows, while classic Jaghbub will not. Also, there are a number of other Unicode fonts on the Mac which contain some or all of our characters, and these can easily be integrated with JaghbUni, less so with classic Jaghbub. That is why we provide both versions; it lets you have a choice. But you may also want to change from one to the other; if you e.g. have written a document in old Jaghbub and want to "convert" it either to JaghbUni on the Mac, or for a Windows user. I have made some tools (for Word 2004 and NisusWriter) that help in this: Changing Jaghbub characters to Unicode, so that you can send e.g. your existing manuscript to a PC-based publisher with diacritics in place. You will see more detail in the Additions package. If you are an existing Jaghbub user, and are interested in the upgrade only, check here for more detail. Although the fonts were originally made for Macintosh, you will also find versions in the PC .ttf format, which Windows users may install on their machines. The Jaghbub package also provides some tools for typing it in MS Word, for JaghbUni, use the regular Unicode methods [e.g. "Insert Symbol" shortcuts].
Caveats and restrictionsNotice that I say the fonts are "based" on Times etc. They are in print quality identical to their origin fonts, within the limits of the font generation programs. Very discerning eyes may notice that one font is marginally thicker, or spaced just a bit tighter or looser than the origin font. An absolute copy is probably today impossible, but the difference between Jaghbub and Times are of the same order as the difference between Times and Times New Roman. On the whole, the diacritic and origin fonts may thus be used interchangeably.One difference I have noticed, is that Word, in particular, gives less line spacing for these fonts than for the original versions. This is not in the font file, the leading there is set to be identical to the original fonts, but something Word does. If you are going to mix these fonts and the originals in Word, you should be aware of this and set the line spacing manually. Helvetica does not have a separate italic style, only boldface, thus Bairut and BairUni are only Roman and Bold. The styles of the three fonts are "merged", so that only the basic font name appear in the Fonts menu, not "Jaghbub Italics" etc. Choosing the Italic style in your word processor will select the italics printer font (if your program supports this). The fonts should cater for normal Persian and Turkish. Of the "classic" fonts, however, only Jaghbub has yumushak g (all the -Uni fonts have it), in Koufra and Bairut you must use g/caron. Germans users should notice that u-U/umlaut and sharp s (ß) in "classic" Jaghbub are different from the standard fonts, although they are produced by the same key. In the Unicode fonts they, of course, follow the standard. What do the names mean? I made these fonts originally for my own use, when I was writing on the Sanusiyya brotherhood. Mac fonts often use city names, and the Sanusi capital was the oasis of Jaghbub in Libya; later the brotherhood moved to Kufra (a font name must have six letters, so "Koufra"). Why Helvetica became Bairut? Figure it out! Postscript files These fonts are made in TrueType, which is now standard for Macintosh OS. If you must for some reason have PostScript versions, contact me with details. OS 9 and earlier versionsIf you use OS 9 and are interested in information about earlier versions of Jaghbub, and tools for it that no longer work in OS X, you will find some more "legacy" information here.Enjoy.
|