Ælfwine Mischler
Much of my early editing experience was in trade books on Islamic topics. Later, I started working for a large Islamic website, where I was asked to write a style guide and eventually became the head of the copyediting unit. Recently, I heard that an Islamic institute that produces videos and podcasts wanted to move into book production and was looking for editors. A perfect match! But when they offered me a book project, I had to reply with “Yes, but . . .” followed by a list of questions for them to answer before I — or anyone — could copyedit for them.
My questions were about author guidelines — that is, a style guide.
What Is a Style Guide?
If you have ever written a research paper, thesis, company report, or book, you most likely were given a style guide to follow. A style guide is a list of preferences for how things should appear in print. It includes such things as when to write numbers as words or numerals; when to use single or double quotation marks; when to use italics; how to cite sources.
Style guides such as The Chicago Manual of Style, New Hart’s New Rules, APA, MLA, and Turabian are quite general. There are more-specialized style guides for science, music, medicine, computer science, and Christian books, etc. While I have seen author guidelines from publishers of Islamic materials, I have not seen a larger style guide for Islamic topics. It should be enough to tell authors or editors to follow Chicago or Hart’s with the addition of paragraphs addressing the style questions below (and perhaps others that arise).
Much of what I have written here is specific to Islamic books, but many items can be adapted to other special subjects. If you are writing a style guide for a publishing house, this essay presents some items you need to decide on. If you are an author, you might have guidelines from your publisher, but I raise some questions that you should consider as a writer.
Style Guides for Special Subjects
Many of the author guidelines provided by publishers who deal with Islam or the Middle East are for academic books, and they deal mostly with how (or whether) to transcribe Arabic names and terms. Pious formulae, honorifics, and common expressions in Arabic are not likely to appear in such books.
But for Muslim authors writing trade books about Islam for either Muslim or non-Muslim audiences, pious formulae, honorifics, and common Arabic expressions often appear, and style issues arise about their use.
Transcription
I have written a lot about this in parts 1 through 4 of this series. For Arabic, some of the choices to be made are whether to use diacritics and:
- how to represent Arabic letters, especially those that have no equivalent in English (Part 1 and Part 2)
- whether or when to show assimilation with the article al- (lam shamsiya) (Part 3)
- how the a in al- will be dealt with when there is elision (Part 3)
- whether or when to omit or capitalize the article, and how to alphabetize names beginning with the article (Part 4).
Part 5 and Part 6 show how to insert special characters in Word.
Keep your audience in mind when you make style decisions. If you are writing an introductory text, do you really need to use diacritics? Readers unfamiliar with Arabic will probably find diacritics off-putting and meaningless.
Names of the Deity
Will you use Allah or God? Your decision might depend on the intended audience. Allah has 99 names. If you use any of them, will you use only the transcribed Arabic, only the English translation, or both? If you are writing a style guide, standardize the translation for use in all of your publications.
Capitalization
Will you capitalize pronouns referring to Allah/God? When I was in Catholic primary school in the 1960s, we were taught to capitalize all pronouns referring to God and Jesus, but the preferred style in most circles now is to lowercase the pronouns. However, many Christian and Muslim writers prefer to capitalize the pronouns (although Muslims lowercase pronouns referring to Jesus). If you do capitalize pronouns, remember to also capitalize relative pronouns who, whom, and whose when they refer to God.
What about throne, hands, eyes, etc. when referring to Allah’s? Many Muslim writers want to capitalize them.
Citing Qur’an
Will you cite Qur’an verses by the name of the sura or by its number? If you choose to use the name, will you transcribe it or translate it? The sura names vary from one translation to another, and some suras have more than one Arabic name, so if you choose to use the name, it is best to also provide the sura number. Standardize the names of the suras of the Qur’an across your publications.
Most Islamic publishers allow quotations only from published translations. Which translation will you use?
Honorifics and Common Expressions in Arabic
Will you include honorifics, pious formulae, and common Arabic expressions? If so, will you write them in English or transcribed Arabic?
Some examples of these and their translations (taken from the Style Guide of the Islamic Foundation and Kube Publishing) are:
- ʿazza wa jall = Mighty and Majestic (used after Allah)
- bismillah al-rahman al-rahim = In the name of God/Allah, most Compassionate, most Merciful
- insha’Allah = if God/Allah wills
Ṣalawāt
The Qur’an instructs Muslims to extend prayers for Allah’s blessing and peace (ṣalawāt) on the Prophet, but whether ṣalawāt has to be in print is another matter. Academic books outside Islamic studies do not use it.
Islamic publishers may have different styles. In academic texts within Islamic studies proper, Islamic Foundation and Kube, for example, place ṣalawāt in the foreword or introduction with a note to Muslim readers to “to assume its use elsewhere in the text.”
Ṣalawāt is more accepted in devotional texts, but publishers might restrict its use to after Muhammad, the Prophet, Messenger (of Allah/God), disallowing it in genitive constructions and after pronouns.
If you will use ṣalawāt in your book, will you write it in transcribed Arabic, translate it to English, abbreviate it (usually as pbuh for “peace be upon him” or ṣaw for the Arabic “ṣallallahu ʿalayhi wa-sallam”), or use an Arabic script glyph?
A word to the wise: If you use ṣalawāt spelled out, you are going to run up your word count. Write a code that will count as one word instead, for example [pbuh]. The copyeditor can still check whether the code is properly placed, and you can use Find and Replace at the end to change it to the form you want.
Technical Terms
Remember your audience. If you’re writing an introductory-level book, keep foreign technical terms to a minimum.
When you do introduce a technical term in the text, will you write the Arabic transcription or the English translation first? Will you put the translation in double quotation marks, single quotation marks (a common practice in linguistics), parentheses, or parentheses and quotation marks? Will you also show the Arabic script? After the initial use, will you use the Arabic term or the English translation? If the former, will you italicize the word only on the first use or on all uses? Will you put a glossary in the back of your book?
Create a list of words that have been accepted into English and that will not be treated as foreign words (that is, not written with diacritics or italics).
Conclusion
Obviously, questions about ṣalawāt are specific to Islamic books, but if you are writing about other religions or other cultures, you can adapt many of the questions about styling technical and foreign terms and expressions to your subject. Keep your audience in mind when making your decisions. Make things easy for your readers.
Ælfwine Mischler is an American copyeditor and indexer in Cairo, Egypt, who has been the head copyeditor at a large Islamic website and a senior editor for an EFL textbook publisher. She often edits and indexes books on Islamic studies, Middle East studies, and Egyptology.
Lyonizing Word: Some Favorite Features from Editor’s ToolKit Plus 2018
Tags: "maggie" a document, 2018, comments, Editor's Toolkit Plus, Editorium, efficient, endnotes, FileCleaner, footers, footnotes, headers, Jack Lyon, Macintosh, macors, MacroVault, Maggie, Maggie Secara, main text, new, NoteStripper, PC, power, pseudo-VBA, revolutionary, speed, text boxes, VBA, Word 2016
Jack Lyon
Making new macros with powerful features!
Bright-colored icons for all happy creatures!
Searching for typos with fresh wildcard strings!
These are a few of my favorite things.
(Apologies to Rodgers and Hammerstein.)
The new Editor’s ToolKit Plus 2018 has a wealth of new features, but I’d like to alert you to a few of my favorites, some of which are not immediately obvious but can be enormously useful.
Title-case all headings
If I had to pick a favorite out of all the new features, it would be this one. The previous version of Editor’s ToolKit Plus made it possible to select a heading, press a key (or click the mouse), and properly title-case the selected text. For example, a heading like this one—
THE GHOST IN THE MACHINE
or this one (Word’s default)—
The Ghost In The Machine
instantly became capitalized like this—
The Ghost in the Machine
with commonly used articles, prepositions, and conjunctions lowercased. That was great as far as it went, but why not make it possible to properly title-case all of a document’s headings without having to select them? That’s what this new feature does, for any text formatted with a heading style (Heading 1, Heading 2, and so on—or your own custom heading styles).
But this feature takes things even a step further, allowing you to automatically title-case headings in the active document, all open documents, or all documents in a folder — your choice. Now, rather than painstakingly capping and lowercasing by hand, you can have this feature do it for you, in seconds rather than hours.
But wait — there’s more, as they say on TV. This feature references a list of words so it knows what to lowercase, and you can edit that list to fit your needs. Obviously you’re going to want such words as and, the, of, and an, but what about beyond? How about through? Add or remove words to meet your own editorial style.
In addition, you can add text that you want to remain in all caps: USA, NASA, AARP, and so on.
Finally, you can even specify mixed case, with words like QuarkXPress and InDesign.
In my opinion, this feature alone is worth the price of admission. It will save you many an hour of editorial drudgery.
AutoMaggie
As you almost certainly know from hard experience, sometimes Microsoft Word documents become corrupted. (The technical term for this is wonky.) The standard fix, known as a “Maggie” (for tech writer/editor Maggie Secara, who has made it widely known to colleagues, although she did not invent the technique), is to select all of a document’s text except for the final paragraph mark (which holds the corruption), copy the text, and paste the text into a new document, which should then be free of wonkiness.
That’s simple enough, but section breaks can also hold corruption, so if your document has several of those, you have to maggie each section separately. Paragraph breaks also can become corrupt, in which case they need to be replaced with shiny new ones. The AutoMaggie feature in Editor’s ToolKit Plus takes care of all this automatically.
MacroVault batch processing
If you’re fond of using macros that you’ve recorded yourself or captured online, you’ll find MacroVault a truly revolutionary feature of the new Editor’s ToolKit Plus 2018. It was included with the previous version of the program as a way to easily access the macros you use the most, including automatically set keyboard shortcuts to run those macros. Now it takes your macro use to the next level, allowing you to run any of your macros on the active document, all open documents, or all documents in a folder.
Not only that, but you can specify which parts of a document you want to use — the main text, text boxes, footnotes, endnotes, headers, footers, and comments. This brings enormous power and flexibility to your macro collection.
FileCleaner saved settings
FileCleaner has lots of new (and useful!) cleanup options — so many, in fact, that I’ve had to put each kind of option on its own tab, one for each of the following:
But I think the slickest new feature in FileCleaner is the ability to save entire sets of options for future use.
Just enter a name for a set of options (for a certain client, a certain kind of manuscript, or whatever). Then click OK to clean up those options. The next time you use FileCleaner, you can activate that set of options again by clicking the drop-down arrow on the right. When you do, all of the options for that saved setting will become selected. You can save up to 20 different sets of options.
Speed!
My final favorite thing isn’t actually a feature. Instead, it’s the speed of nearly all the features in Editor’s ToolKit Plus 2018.
I originally wrote many of my programs back in the 1990s, using the clunky, old-fashioned WordBasic language. When Microsoft Word 97 was released, it featured a new language — VBA (Visual Basic for Applications), but it would also convert WordBasic macros into pseudo-VBA so the macros would continue to work in the new software. That pseudo-VBA has been the basis for my original programs ever since.
Now, in Editor’s ToolKit Plus 2018, I’ve rewritten most of the code from the ground up in native VBA. It took a long time to do that (nearly 28,000 lines of code!), but the resulting software is fast. NoteStripper, for example, used to strip notes to text by selecting, copying, and pasting each note. It worked, but if a document had lots of notes, it took a long time. Now, NoteStripper strips notes to text without selecting, copying, or pasting anything. Everything is done using the built-in text ranges of the notes and the document itself, and wow, what a difference!
For purposes of comparison, I just used NoteStripper on a document with 100 notes. The old version took 25 seconds — not bad. The new version took 2 seconds — making it more than 10 times faster than the old one. If you’re working on a big book with a short deadline, that kind of speed can make a real difference in your ability to get the job done.
In conclusion
I hope you’ll try the new Editor’s ToolKit Plus 2018 (which runs in Word 2016 on Macintosh, and in Word 2010, 2013, and 2016 on PCs), and that it will become one of your favorite things! If there are any features you particularly like, I’d love to hear what they are. If there are any features you would like to work differently, I’d love to hear about that as well.
Finally, if there are any features you think needed to be added, please let me know. I’d like to make Editor’s ToolKit Plus as useful as possible.
By the way, I continue to make improvements to the program almost daily. For that reason, if you’ve already installed Editor’s ToolKit Plus 2018, I strongly recommend that you download and install the most-recent version. You can download it here.
Share this:
Like this: