Wikipedia talk:Manual of Style/Arabic

From Wikipedia, the free encyclopedia
Jump to: navigation, search
edit·history·watch·refresh Stock post message.svg To-do list for Wikipedia:Manual of Style/Arabic:

To-do list is empty: remove {{To do}} tag or click on edit to add an item.

The apostrophe in Qur'an[edit]

The table at WP:Manual of Style/Arabic#Examples gives “Qur'an” as the standard transliteration, but the article itself is at Quran, the link in the title above being a redirect. (I notice that the {{Cite quran}} template lacks the apostrophe as well.) But titles are sometimes subject to special policies. What is the consensus for the spelling in articles, where current practice seems to be mixed? Should the example be changed, leaving the apostrophe only in the “strict” column?—Odysseus1479 (talk) 23:02, 10 November 2012 (UTC)

In article titles, the single apostrophe (') is often used for `ayn ع (e.g. Ta'awwudh, but in ordinary transcription style it would represent a glottal stop. Not sure that such de facto quasi-contradictions between article title practices and other transcription practices have been resolved. Notice that the "strict" column uses (’), not (')... AnonMoos (talk) 05:36, 11 November 2012 (UTC)
Though in Nastaʿlīq script an actual (ʿ) appears in the article title. AnonMoos (talk) 14:28, 14 November 2012 (UTC)
Removed the contentious example. --Francis Schonken (talk) 13:36, 14 September 2015 (UTC)

Preferred form where no Wikipedia article exists[edit]

For some reason I hadn't come across these guidelines before, but I'm finding them very helpful. I'm working on several articles about the history and architecture of southeast Anatolia and al-Jazirah between the time of the Muslim conquest of this area (638) and when it was added to the Ottoman Empire (around 1515). A lot of my sources for this period are historians writing in English, who themselves rely primarily on Arab sources. These accounts tend to have quite a lot of references to historical figures who don't currently have Wikipedia articles (and may never). As I don't read Arabic, I am taking personal and geographic names from these secondary sources, where they are typically rendered in a strict transliteration (e.g. al-Muwaḥḥid ʿAbd Allāh), rather than making my own transliterations from Arabic.

These MOS guidelines are pretty clear when dealing with the subject of an article, but I can't find a clear statement of how to handle transliteration of other names and terms that don't merit their own articles. My interpretation is as follows, but please correct it if I have misunderstood.

  • For any name or term taken from Arabic use the primary transcription where one exists.
  • In the absence of a primary transcription, use the standard transliteration (ALA-LC Romanization, no diacritics).
  • If the name or term merits its own Wikipedia article, list the strict transliteration (and original Arabic form) in the lead paragraph. In many cases this would be the only place we would use the strict transliteration. Direct quotations and titles of reference works might be the other places.

Assuming that my understanding above is correct, I will need to fix a number of articles to use standard transliteration in place of strict transliteration.

Would it be possible for someone to rewrite this MOS guideline to clarify this aspect? I think what's needed is to add a subsection for "Preferred form" within the "Proposed standard" section. It could be as simple as stating that where an Arabic name or term does not meet the criteria for its own article, it should still appear in other Wikipedia articles using the approach laid out in Wikipedia:Naming conventions (Arabic).

That does raise another question for me: A lot of the relevant historical figures during this period have pretty long names with chains of nasabs (e.g. Amir Saif al-Dīn Shīrbārīk Maudūd bin ʿAlī (bin Alp-Yaruq) bin Artuq). Where the person has their own article, it seems fine that I just refer (and link) to that form . Where there is no article for that individual, it would seem best to use the full name on first reference, and then use the most common form for subsequent references. Is there an MOS guideline that covers this area? Rupert Clayton (talk) 19:44, 5 January 2015 (UTC)

Guidelines for non-Arab people in Arabic sources[edit]

I have another transliteration question related to the one above. A lot of the historical figures who appear in the articles I'm working on are non-Arabs who operated in an Arabic-dominated culture, or whom we know about primarily from Arab historians. They seem to break into three main groups:

  1. Non-Arabs operating primarily in an Arab culture: e.g. Saladin (Salah ad-Din Yusuf ibn Ayyub)
  2. Non-Arab Muslims whose lives were primarily documented in Arabic, but who may have primarily spoken other languages: e.g. the Rum Seljuks, the Türkmen Artuqids and Aq Qoyunlu, Ilkhanid Mongols.
  3. Non-Arabs who only appear in Arab sources as the object of alliances, military campaigns, etc: e.g. Byzantine Emperors, Georgians, etc.

It seems clear to me that people in group 1 should follow the guidelines for Arabic names, and people in group 3 should follow separate guidelines. Is there any guidance for people in group 2? Rupert Clayton (talk) 20:22, 5 January 2015 (UTC)

Thinking this through a little further, the languages these dynasties used were something like the following (very roughly):
Dynasty Court/official language Lingua franca Military language Scholarly and literary language
Great Seljuks Persian Persian Oghuz Turkish Arabic
Artuqids Arabic? An oghuz language similar to Azeri?  ? Arabic
Rum Seljuks Persian Old Anatolian Turkish  ? Persian
Aq Qoyunlu Azerbaijani Azerbaijani Azerbaijani Arabic and Azerbaijani
Ilkhanids Persian Mongolian? Mongolian? Persian?
Most words that need transliteration are personal names of rulers and nobility, so in most cases, these can follow the transliteration style for Arabic or Persian as appropriate. In some cases, elements of names are clearly derived from a Turkic or Mongolian language. Where there is no primary transcription evident, I'm tempted to follow modern Turkish standards for Turkic names. I'll deal with the Mongols' names when I get to them. Thoughts? Rupert Clayton (talk) 01:51, 6 January 2015 (UTC)
Using Modern Turkish spelling to romanize Ottoman names is correct and standard in ALA-LC. That wouldn't extend as far back as Aq Qoyunlu or Seljuk names. For pre-Ottoman Turkic names, I think it would be best to either follow the prevailing form used by scholars or, failing that, a faithful transliteration from the Arabic alphabet. I doubt that modern Cyrillic orthography in Mongolian could be of any use for historical figures from centuries ago; you always see those names romanized from the original Classical Mongolian forms written in the vertical Uyghur script. Cyrillic Mongolian orthography is based on pronunciation changes that have taken place since the classical times and is sometimes very divergent from the original. Johanna-Hypatia (talk) 18:52, 8 February 2015 (UTC)

Misuse of the definite article[edit]

The lead of the article on the topic of the Arabic definite article states:

  • "Unlike most other particles in Arabic, al- is always prefixed to another word and it never stands alone. Consequently, most dictionaries will not list it as a separate word, and it is almost invariably ignored in collation." I am curious to know the implications of this especially as it applies to the representation of Arabic titles in English.

This comes in a context in which has a very clear policy / guideline on WP:THE and a content at WP:CRITERIA that presents:

  • Naturalness – The title is one that readers are likely to look or search for and that editors would naturally use to link to the article from other articles. Such a title usually conveys what the subject is actually called in English.

In many cases, unless the "al-" is familiar, it will just get in the way and further problems are raised in situations as when a name for the article is used "to link to the article from other articles". It may often be nonsensical for an article to present something like "... of the al-Link ...." and, in these cases, the problems of WP:THE seem to me to be exacerbated.

I am no great fan of WP:THE but I think that, if anything, there tendency has been to edit Arabic titles in a way that is quite contrary to this policy / guideline and am curious as to why this might be.

There is currently a discussion at Talk:Masjid al-Haram#Requested move 1 May 2015 in which I have presented quotes such as from the Encyclopaedic Dictionary of Religion: G-P which presents:

Masjid al-Haram : The Grand Masjid on Makkah. The Ka'bah (the Qiblah of the Muslims) is situated within it.
and I have invited editors there to present their own research and have suggested the use of searches such as:

(I mention this because I think there may be a perhaps related issue in regard to the presentation of the most commonly used name for a subject as it is used in English).

I would be grateful for any thoughts in regard to issues mentioned and on ways in which any potential issues might best be addressed.

I will also present content on other inappropriate or possibly inappropriate uses of related titling in a sub-thread below and, at editors discretion, suggest that any related discussion/response may continue in a "related discussion" section after that. Thanks. GregKaye 08:58, 5 May 2015 (UTC)

Examples and suspected examples of the misuse of "Al-" in title texts[edit]

Feel free to add examples of related articles:
GregKaye 08:58, 5 May 2015 (UTC)

Related discussion[edit]

Replies, thoughts, responses related to the above will be gratefully received: GregKaye 08:58, 5 May 2015 (UTC)

Sun letters, once again[edit]

The MoS has a statement in the section on definite articles "For this manual of style, assimilated letters will be used, as it aids readers in the correct pronunciation." This seems a bit strange. Is it stating that assimilated letters must be used? If so, it seems an unusually strict requirement which opens up quarrels and confusion. ALA-LC does not use assimilated letters, and the preponderance of ALA-LC transcription in English texts (certainly in the US) mean that most academic and other source material will not be using them. Are we requiring Wikipedia editors to know that the transcriptions they are coming across and using in articles are "wrong" by that policy statement? Most Wikipedia editors are not Arabic-speakers, and have no idea about assimilated letters or pronunciation, and will transcribe names as they read them (e.g. "Harun al-Rashid" rather than "Harun ar-Rashid"). This seems a very strange demand to make upon them. Particularly as it opens up quarrels between editors, between the few who insist on assimilated letters (unusual in the literature) and the bulk who insist on keeping it unassimilated (as they commonly read it). It will also likely introduce inconsistencies across articles, e.g. the main article being forcibly named "Harun ar-Rashid", but other editors continue to innocently write "Harun al-Rashid" in other articles, not imagining it might be inconsitent. It seems to me WP:MOSAR statement is being unproductive here, and imposing a rule that contradicts common usage, and will likely lead to quarrels between editors. I would like to propose a modification in the MoS which states that assimilated letters can be used, if shown to be the preponderant transcription, and eliminate the statement that "it will be used", which seems an anomalous imposition. Walrasiad (talk) 23:48, 1 June 2015 (UTC)

I’m inclined to agree. The premise quoted above seems flawed: pronunciations and native orthographies usually appear near the beginning of the lead, so I don‘t think promotion of correct pronunciation is generally an important consideration for our spelling norms, especially where the result would differ from the most frequent form. I confess, however, that I don‘t understand the rationale for many of our spellings (for example how we came up with the peculiar Quran, neither the commonly encountered fish Koran nor the more precisely transcribed fowl Qur’an, so to speak), and I‘m not familiar with the academic literature, so I may be missing something.—Odysseus1479 00:36, 2 June 2015 (UTC)
The project page explains that per Wikipedia's Manual of Style, if the title of an article is to be based on standard transliteration from Arabic, then assimilated letters will be used. I strongly disagree with your proposed modification. Thousands of article titles on Wikipedia, about place names, people, etc, use the assimilated letters per WP:MOSAR. Some of the titles (only where the assimilated definite articles occur at the start of the title) can be found in these lists: All pages with prefix at-, All pages with prefix ad-, All pages with prefix adh-, All pages with prefix ar-, All pages with prefix az-, All pages with prefix as-, All pages with prefix ash-, All pages with prefix an-. Khestwol (talk) 08:18, 2 June 2015 (UTC)
This is not about article titles. This is about common usage in article text. I've written hundreds of historical articles on Wikipedia, many of them relating to North Africa, with hundreds of Arabic names, and I assure you that not once did I use assimilated letters, for they were not used in my sources. This was not a conscious decision - I was simply following common usage in academic sources and other texts, and was blissfully unaware of this weird quirk in MOSAR. I presume a lot of editors are like me, in that they write based on sources, and wouldn't in a hundred years imagine that MOSAR has a tiny codicil which contradicts common usage. (Not least that a lot of editors simply don't know Arabic, and wouldn't know what a sun letter was if it hit them in the face, so wouldn't even imagine this to be a question; this codicil seems to expect that any articles that refer to an Arabic name are only going to be written by Arabic-speakers, aware of nuances of Arabic pronunciation?) In other words, articles will continue to be written with unassimilated letters. If this is a policy, then it is patently unenforceable, and will foster inconsistency and quarrels. Will Wikipedia establish a "sun letter task force" to comb through all these articles to ensure compliance with this bizarre requirement? Or is this going to remain a hidden weapon for sun letter warriors to surprise writers, contradict common usage, and provoke quarrels and acrimony between editors? This is an immensely unproductive codicil that needs to be rectified. If not rectified, then I would request that the statement at the top of MOSAR requesting editors to follow ALA-LC be corrected or removed entirely, as it is very deceptive. MOSAR statement at the top needs to be re-written to clarify that Wikipedia intends to promote pronunciation, not common usage. Walrasiad (talk) 12:29, 2 June 2015 (UTC)
Walrasiad, BTW, I personally find that most relevant titles on Wikipedia, especially those which are about the Arabian Peninsula or areas east of the Maghreb region, do assimilate al- before a sun letter. Also see the lists I provided above. You maybe right about the Maghreb, but I guess that is because the transliteration from that region are more under the French influence maybe? Many of the articles from that region do not use spelling normal in English. But I myself try to assimilate al- before a sun letter in titles. And BTW, this is coming from a non-Arabic speaker. Face-smile.svg I have very little knowledge of Arabic. However, I am aware of the correct pronunciation of the definite article so I always try to follow WP:MOSAR. Khestwol (talk) 13:10, 2 June 2015 (UTC)
I don't think it is a regional issue. It is a source issue. If articles are written based on written English sources, particularly academic or recent ones, ALA-LC will very likely be followed and sun letters will be unassimilated. While you may be aware of correct Arabic pronunciation, I don't expect most Wikipedia editors are. They write as they read. And they read unassimilated. Walrasiad (talk) 13:28, 2 June 2015 (UTC)
ALA-LC is not the only romanization. See Romanization of Arabic, there are also others in common usage. I think that most do assimilate al- before a sun letter. A change like what you are recommending won't be constructive to implement in the present. It will lead to incorrect, simplistic pronunciations which are not based on correct Arabic, and many many articles will have to be moved away from their present, correct titles. I think the MoS is fine as is. Khestwol (talk) 13:46, 2 June 2015 (UTC)
ALA-LC is, far and away, the most widely-used romanization in modern English sources, particularly academic ones, and increasingly in journalism and elsewhere. In short, it's what Wikipedia editors are reading, and the sources they will be using to write articles. If ALA-LC leads to incorrect Arabic pronunciation, so be it. This is not an Arabic language class, it is an encyclopedia. Communicating information, not teaching pronunciation, should be the paramount concern. The question of assimilation is evidently something that both the ALA and LC carefully weighed and decided upon, and one the bulk of academics agreed with. If you think they were all wrong-headed, and you know what is best, perhaps you should write a letter to the Library of Congress expressing your misgivings. I wish you luck. That said, I remind you that I am not requesting imposing ALA-LC in Wikipedia. What I am requesting is flexibility, removing that draconian codicil so as to to allow unassimilated spellings to also be used here, and ensure they aren't automatically and controversially overridden by MOSAR, regardless of common usage and causing edit wars and quarrels. Walrasiad (talk) 14:40, 2 June 2015 (UTC)
PS.- I am going to pause my commentary, to allow other editors to speak. While this is an outgrowth of Talk:Harun ar-Rashid#Requested move 19 May 2015, I do not want this to become a continuation of that. I would be interested in hearing what other editors, not involved in that particular page, think about the proposal. Walrasiad (talk) 14:50, 2 June 2015 (UTC)
Well I think that also allowing unassimilated spellings will gain for us nothing and will only cause a big WP:CONSISTENCY issue. Khestwol (talk) 15:13, 2 June 2015 (UTC)

"Dynastic Al"[edit]

As discussed above, "Al" when not the article means "family", not "dynasty" - even if dynasties take their family's name. Whenever the name of the ancestor is well-known, its descendant may be know as "Al ...". See for example Al ash-Sheikh. Naming it "dynastic" may let people think these are a reigning familyn which is not necessarily true.

Also, this section should also be part of Al (disambiguation) and arabic names - I copied it there--Df (talk) 20:56, 24 June 2015 (UTC)

In-line Arabic[edit]

Some articles require the use of the original word in Arabic script. It could be me, but I am coming across an increasing use of the big template for enlarging Arabic words. Personally, I don't like this since it increases the whitespace between lines, adds to a sometimes already complex syntax code, and I can't see much difference anyway (could be my browser settings). Is this the new standard for Arabic or does a normal font size suffice? - HyperGaruda (talk) 11:19, 8 August 2015 (UTC)

By the way, I recently compared this issue on Internet Explorer 11 vs Firefox 38 (my standard browser). It seems that Firefox currently uses a different character set for Arabic in the Arial font, a set which is larger/much more legible and Arial-like. IE11 on the other hand uses the illegible Arabic character set which I was used to until some time ago and which would justify the use of the Big template. - HyperGaruda (talk) 08:02, 9 August 2015 (UTC)
I agree, {{big}} is a kludge. The problem is that Arial is terrible for mixing Arabic with other scripts. It has a very large x-height for Latin letters, but a small dal-height for Arabic. (Cyrillic and Greek are matched to the Latin in x-height, weight, baseline and stroke taper, but its Arabic differs in all four.) I wonder if something could be done with an "Arabic-script" CSS class and the default stylesheets to select a different font? Pelagic (talk) 13:54, 18 September 2015 (UTC)
There is {{Script/Arabic}} which adds a script-arabic class, but it also has its own hard-coded font list, and sets the size to 125%. Pelagic (talk) 14:26, 18 September 2015 (UTC)
When using {{lang}}, most languages in the Arabic script be displayed in a more legible font on Chrome. Is there not a way to request a change for which default font is chosen for the Arabic script? Abjiklɐm (tɐlk) 17:51, 18 September 2015 (UTC)

The apostrophe (again)[edit]

Not sure if anyone's still watching this page, but there is some discussion going on about the standard transcription of ayin and alif. At least concerning the title. The Arabic naming convention only says to use the standard transcription method, but then there's also the convention to limit apostrophe usage to ' (straight apostrophe), so that ayin and alif would be transcribed identically instead of with ` and '. Any comments on that?

If we're going to use a straight apostrophe for both letters in the title, perhaps it's also an idea to extrapolate that to the standard transcription rules. It would not be completely absurd, considering that we're also writing ض/د and ص/س with the same letters. - HyperGaruda (talk) 14:24, 16 September 2015 (UTC)

The problem I see, with `ayn in Arabic, is that the sound is described as a vocalized fricative somewhere in the back of the throat. That makes it closer to h or gh in English, though I don't know of any transliteration schemes that use those for `ayn (c.f. ghayn).
Perhaps the symbol ʻ or or ʿ was chosen for its similarity to Greek polytonic spiritus asper / dasia ʽ (which we transliterate as "h" when dealing with Greek)? But most English-speakers when seeing an apostrophe-like character will either ignore it, or if between vowels treat it as a hiatus or stop rather than a fricative. Given that I can't pronounce the Arabic `ayn sound, is it worse for me to mangle it to "hayn" or "ayn"?
From a purely typographic perspective, I do find backtick/grave ` visually distracting in the simple/loose transcriptions. I was in favor of substituting straight-apostrophe ', until I learned how different the sounds are for `ayn and hamzah. (Funny that it's called hamzah and not 'amzah?) Now I just don't know which approach is best (or less worse).
According to the hamza article, the form of ء is derived from ع, so it's not absurd that we might choose to conflate the two.
Is there a Wikipedia standard for transcribing Hebrew ayin in running text and page titles? Hebrew alphabet#Transliterations and transcriptions says that the "Standard Israeli transliteration" uses apostrophe ' for both alef א and ayin ע in medial positions and omits them when initial and final. This might be appropriate for modern pronunciation, but do we also use that for ancient or medieval terms?
  • Good luck finding Tiberian Hebrew in running text and titles. As far as I understand, the Hebrew wikipedians always use the modern Hebrew pronunciation in the main text (save for the strict transliterations in leads, like us), so per definition you'll only find the standard rules you mentioned. - HyperGaruda (talk) 15:58, 21 September 2015 (UTC)
You're right. I found the Hebrew naming conventions document, which also covers running text, and recommends "general-purpose, diacritic-less transliteration" from SBL Handbook of Style. That seems pretty close to the transcription for modern Hebrew. I'm not sure how much it's followed in practice (many biblical and religious terms would have established common English names), but where applied would mean apostrophe-or-omitted for both ayin and aleph. Modern Arabic still distinguishes the two sounds, so it's a different situation; I mentioned Hebrew to compare what editors are doing with another Semitic language/script. Pelagic (talk) 21:19, 22 September 2015 (UTC)
Of course we need to be really careful not to use ` for ayin in other languages like Turkish or Persian.
  • I do not think that is going to be a problem, since these languages don't have the ayin sound except for in Arabic loanwords (which are covered by this MOS). It additionally seems that Persians pronounce ayin like hamza (glottal stop). - HyperGaruda (talk) 15:58, 21 September 2015 (UTC)
Pelagic (talk) 21:12, 20 September 2015 (UTC)
Although ayn is described as a fricative, it is virtually always approximated as a glottal stop or omitted when the speaker cannot pronounce it. For example, the names Ali and Omar both start with ayn. So to answer your question, it should definitely be 'ayn, not hayn since ignoring the ayn is a better alternative than to approximate it with an h. As for the hamza, the name starts with h because the actual Arabic name for this symbol also starts with h. But the sound it denotes is a glottal stop nonetheless.
  • I concur. I've always been taught that ayin is more like a difficult-to-pronounce hamza, rather than say ha. - HyperGaruda (talk) 15:58, 21 September 2015 (UTC)
About the symbol `, I also find it less than appealing. Since both the hamza and ayn are ignored in English, I think it is acceptable to transcribe both with an apostrophe within titles, and to use the strict transliteration in the lead. Abjiklɐm (tɐlk) 01:46, 21 September 2015 (UTC)
If it's acceptable for a foreigner to pronounce `ayn the same as hamza, or omit it altogether, then perhaps it is more like the situation with sīn س and sād ص than I had thought. Pelagic (talk) 21:34, 22 September 2015 (UTC)

So far it looks like we are heading towards ayin&hamza='. I propose to update the MOS on October 1st, unless someone objects in the meantime. - HyperGaruda (talk) 15:58, 21 September 2015 (UTC)

I agree with using a straight apostrophe (') for both ayn and hamza. The grave accent (`) is ugly, especially in the middle of words.--Axiom292 (talk) 04:55, 22 September 2015 (UTC)
In the original MOS discussion, Bgwhite cites some titles that might be changed including `Alya', the name of a village near Medina. Does that indicate a (maybe rare) example where conflating both ayn and hamza to the apostrophe character could increase confusion for an English-speaking reader? Doesn't 'Alya' (which is currently a redirect) look like we're using "scare quotes"? Rupert Clayton (talk) 00:09, 23 September 2015 (UTC)
That is a legitimate concern. However, after looking at that article in Arabic (ar:العالية (وادي الصفراء)), I should point out that the correct transliteration should actually be 'Aliya (al-ʻĀliyah). Abjiklɐm (tɐlk) 03:13, 23 September 2015 (UTC)
Also, the current convention says to omit alif/hamza in the initial position of a word. I think we should extrapolate that to ayin. - HyperGaruda (talk) 09:52, 23 September 2015 (UTC)
I was going to ask about the initial position. Had been expecting that initial 'ayn would have a leading apostrophe but initial hamzah would be omitted, and wondered if it would cause confusion with people mistakenly deleting apostrophes. (Though the looks-like-quotes problem hadn't occurred to me.) Pelagic (talk) 12:23, 23 September 2015 (UTC)
The initial hamza is omitted because that is specified in the ALA-LC transliteration scheme. Following these rules, we should not omit initial ʻayn. What confusion do you mean? Abjiklɐm (tɐlk) 18:32, 23 September 2015 (UTC)
Thanks, Abjiklɐm. As a non-speaker of Arabic, it didn't occur to me that there might be bigger problems with transliteration of `Alya' / 'Aliya / al-ʻĀliyah. I don't think a convention to render both 'ayn and hamza with the apostrophe character would cause confusion in this case. You point out that ALA-LC advises omitting an initial hamza, and retaining an initial 'ayn. Are there cases where the proposed rule would result in an apostrophe character for hamza or 'ayn at the end of a word or phrase that also starts with 'ayn? If so, it seems these titles could be confused with a name in quotes. Is that likely to be a significant problem? Rupert Clayton (talk) 23:32, 23 September 2015 (UTC)
I had a quick look in the Hans Wehr dictionary, and there are indeed words that start with ʻayn and finish with a hamza (ʻibʼ, ʻabāʼ). I've honestly no idea whether this will be an actual problem we're likely to run into. Is there a way to get a list of all articles starting with `?
While we're on the topic of apostrophes, I've noticed the Hawaiian ʻokina is shown with a curly ʻ even in titles. Is there any opposition to using ʼ and ʻ for Arabic titles instead of '? With a redirection from straight quotes of course.Abjiklɐm (tɐlk) 14:33, 24 September 2015 (UTC)
  • Re. Is there a way to get a list of all articles starting with `? – here they are
  • Re ...whether this will be an actual problem we're likely to run into – `Alya' is the example given above, and we ran into it.
  • Re. Is there any opposition to using ʼ and ʻ for Arabic titles instead of '? – yes, see "some discussion" link provided in the post opening this talk page section. Following the link you'll see I wrote: "Brought back some former guidance on this to WP:AT#Special characters, second bullet (this only applies to the article title, but as the discussion ... is on a page move this is rather AT than MOS matter)". Then you'd have to follow that link to the AT policy page and look at the content of the second bullet of that policy section. Sorry this discussion got a bit fractured.
  • Again, the "generally avoid apostrophe-like characters apart from the apostrophe itself and even use that one sparingly" is to make sure articles can be found by typing in the "search" box (upper right corner of any Wikipedia page) using only direct keys on a standard QWERTY/AZERTY keyboard and not knowing how to generate the other special characters there. Redirects can take care of the rest.
  • This is not about redirect pages, which, of course, can be created with all the exact characters in the article title, redirecting to the variant with the apostrophes (or without them if an even less strict transliteration or translation is chosen for the article title of the page where the content is).
  • Also, the AT policy allows ayn, hamza, okina and whatever in article titles of content pages, but considers it an exception that can only be allowed on a case by case basis, with a solid consensus for that particular case, and with all the redirects from less strict transliterations/translations in place like you can see here)
  • Also again, this is not about how such names are written in article text where exact transliterations can be used (which is MOS matter, not AT matter). --Francis Schonken (talk) 15:24, 24 September 2015 (UTC)
Thanks for breaking out the issues. Would redirects not also take care of the problem of typing special characters in the search box? I can type "Abdul-Baha" there and go straight to the `Abdu'l-Bahá article (by virtue of the redirect). Presumably that would work even if the article were titled ʻAbduʼl-Bahá. That would seem to indicate that ease of use of the search box is not by itself a strong reason to avoid special characters in titles. The policy at WP:TSC doesn't actually say why to avoid "apostrophe-like characters" in titles. Perhaps the prioritization of popular articles in the search box doesn't carry over to redirects? Perhaps external search indexing (e.g. Google) would be impacted? If there's no strong case that using ʼ and ʻ in article titles would cause harm, it's starting to look like AT policy is simply defending a convention from an earlier age, in the same way that some people insist on using two spaces after a period. Rupert Clayton (talk) 16:24, 24 September 2015 (UTC)
Answer is in 6th bullet. --Francis Schonken (talk) 16:33, 24 September 2015 (UTC)
Hmm, your 6th bullet says there's an option for case-by-case exceptions, which is not what I'm talking about at all. If "apostrophe-like characters" in titles cause no actual harm, then it would seem they should be allowed as standard and not require a special exception. Conversely, if the policy remains that there's needs to be solid consensus before an exception can be made to allow "apostrophe-like characters" in a title, then presumably there's some clear downside to allowing them. What that is has not been made clear. Rupert Clayton (talk) 18:59, 24 September 2015 (UTC)
See what you mean, the question at least. The problem is with the redirects not being created. --Francis Schonken (talk) 19:04, 24 September 2015 (UTC)
Redirects were surely not the problem in the case of Sha'ban, yet it got this whole discussion starting again. - HyperGaruda (talk) 05:31, 25 September 2015 (UTC)
Re. "redirects ... not the problem" – Correct, but lack of consensus was. Again, I draw your attention to the content of the 6th bullet in my list above: it mentions both aspects:
  1. "solid consensus"
  2. "all the redirects from less strict transliterations/translations in place"
Both conditions need to be met.
Re. "got this whole discussion starting again" – Let's face it: Wikipedia:Manual of Style/Arabic is a mess, so don't feel bad that a single example led to an invitation to shape it up. As long as that is not possible (like it has been for the last 10 years or so), the policy at WP:AT will have to make do. --Francis Schonken (talk) 08:03, 25 September 2015 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────Point taken, so back to the issue at hand: the initial apostrophe for ayin. So far there have been three opinions on that:

  • Use curly apostrophes (with redirects), distinguishing between ayin (‘) and hamza/alif (’); essentially this is the strict transliteration.
  • Use straight apostrophes, but only in the case of ayin and not for hamza/alif.
  • Leave the initial apostrophe out altogether.

I still stand behind the third option, not (only) because it is my own, but because primary transcriptions (i.e. common names used in the media) tend to do it that way. For example, names like Abdullah and Ali or nouns like Eid (as in Eid al-Fitr) tend to be written without initial apostrophes despite beginning with ayin. - HyperGaruda (talk) 08:55, 25 September 2015 (UTC)

Agreed with the third option. The current convention is to leave initial apostrophes (as in Asr prayer, Eid al-Adha, etc). Khestwol (talk) 09:00, 25 September 2015 (UTC)
  • I've no opposition against the third option. To be clear, does the proposition include using the same symbol for both hamza and ayn in non-initial position? Abjiklɐm (tɐlk) 16:19, 28 September 2015 (UTC)
    • Yes. As far as the standard -not strict!- transcription goes, hamza and ayn will be treated exactly the same. So straight apostrophes, and only in non-initial positions. - HyperGaruda (talk) 17:22, 28 September 2015 (UTC)
      • Thanks, Francis, for the explanation that AT policy avoids apostrophe-like characters because we can't rely on redirects being in place. HyperGaruda's argument from simplicity and media convention makes some sense. It looks like we're not at the point where WP can lead convention on Arabic transliteration, so options 2 and 3 (using apostrophes) seem like the best choices. So, the question is: Should WP follow ALA-LC in titles and omit the initial hamza and not the initial ʻayn? Rupert Clayton (talk) 16:43, 29 September 2015 (UTC)
I thought we had already reached consensus on "apostrophe vs apostrophe-like characters" in general, a couple of comments earlier... Anyway, regarding the initial apostrophe there are two (three including me, 3.5 including Rupert's 50/50 choice) editors in favour of leaving it out altogether and none against. "Should WP follow ALA-LC...?": yes in strict transliterations; no in standard transcriptions (which includes titles and general use in the main text), which already is the case currently. I'll edit MOS-AR this afternoon (UTC) so that there is at least a visual example of what we're discussing here. - HyperGaruda (talk) 07:38, 1 October 2015 (UTC)

The reason why none of these proposals are still going anywhere is imho very simple: they try to impose a rule across all articles and are still unsuccessful in dealing with the consensus that may arise around some article titles. These consensuses are real and won't be overthrown by would-be guidance. That's why the WP:TSC policy contains "If, exceptionally, other variants are used a redirect with the apostrophe variant should be created (e.g. 'Abdu'l-Bahá redirects to `Abdu'l-Bahá)." I don't think `Abdu'l-Bahá is going to change anywhere soon, so deal with it.

Another reason why these discussions progress so difficultly is that contributors don't pay much attention to what others write, they add something, apparently only half understanding what someone else wrote. E.g. above I read "...options 2 and 3 (using apostrophes)..." while "option 3" reads "Leave the initial apostrophe out altogether". So please stay focussed, and avoid fuzziness in the comments. How is someone supposed to be interested in your comment, if that comment is only paying half attention to the comments by others? --Francis Schonken (talk) 08:24, 1 October 2015 (UTC)

Updated ayn[edit]

And additionally made changes to the wording of some phrases. - HyperGaruda (talk) 14:46, 1 October 2015 (UTC)

Renaming suggestion[edit]

Perhaps we should rename the current standard transcription into something like basic transcription. I often get the feeling on other talk pages that people confuse standard transcription with strict transliteration. Although this might give problems with primary transcription, so maybe we should change that into common transcription Any better naming suggestions? - HyperGaruda (talk) 19:20, 1 October 2015 (UTC)

I think your choice of common transcription, basic transcription and strict transliteration describes well the different options. Abjiklɐm (tɐlk) 21:34, 1 October 2015 (UTC)
Works for me! Another thing I think we might need to (re)consider is whether or not we're going to say anything about translations... The first sentence of the "Definitions" section reads "For the purposes of this convention, an Arabic word is a name or phrase that is most commonly originally rendered in the Arabic alphabet, and that in English is not usually translated into a common English word...." and that's the last thing said about translations. Now if we're going to talk about article titles in a coherent way, translations would probably need to be part of the guidance (e.g. a concept that is under a translated article title, can be transliterated in the first paragraph of the lede). Or leave article titles out of this guidance alltogether? Which would mean reviving WP:Naming conventions (Arabic)... Don't know what would be best? --Francis Schonken (talk) 05:46, 2 October 2015 (UTC)
Thanks for mentioning translations. It's a bit odd that the broadly titled "MoS/Arabic" hardly says anything about using translations in the first place. Then again, to the original editors it might have been obvious, that the mother of all trans-language wiki conventions comes first. I'm really against treating the article title differently, since it just adds more complexity to an already complex situation. Instead, simply stressing the importance of WP:English might be enough. - HyperGaruda (talk) 10:41, 2 October 2015 (UTC)
Re. "...treating the article title differently...": well article titles are treated differently. That's basic MOS/AT distinction. The choice is whether we say something sensible about article titles in this guidance or whether we revive the derelict WP:Naming conventions (Arabic). Even if the last option is chosen WP:MOSAR should not contain guidance that is incompatible with article titling guidance, meaning: the complexities involving article titling need to be addressed anyway. That is, if we want this page to evolve from would-be guidance to an actual guideline. --Francis Schonken (talk) 11:48, 2 October 2015 (UTC)
I think the current convention for article titles is a clear enough summary: Article titles are written preferentially using a common English translation. If unavailable the common transcription is used. If neither is available, the basic transcription is used. The strict transliteration should never be used in article titles. This brevity does not really warrant a complete article of its own imho. The current common and basic transcription rules are MoS-compatible, so I am not sure what other rules you want to add for article titles; care to explain? - HyperGaruda (talk) 15:21, 2 October 2015 (UTC)
That ruleset could never account for Muḥammad ibn Mūsā al-Khwārizmī which has survived quite a number of WP:RMs (...and many other examples some of which have been mentioned above), so I attempted to rewrite in view of WP:AT compatibility, and removed the link to the failed naming convention. Hope this may work. --Francis Schonken (talk) 16:47, 2 October 2015 (UTC)
That looks great. And about al-Khwarizmi: wow, who permitted that title? Ok, I see some reason in keeping the first name over the common name, but the diacritics? It's got to be an absolute pain in the a** to keep using that name in the article. - HyperGaruda (talk) 17:36, 2 October 2015 (UTC)
Re current article title for al-Khwarizmi (and many others that show little coherence for how the Arabic name is rendered): shows the downside of not having had a coherent article titling guideline for Arabic names for the last ten years, so I'm happy we're going towards something that might fill the gap. If this becomes an acceptable naming convention probably some of the current article titles may benefit from being revisited. Don't want to rake up the dust though, before we're sure this is a convenient naming convention. --Francis Schonken (talk) 07:43, 3 October 2015 (UTC)

<big> and <large> tags[edit]

Since the guideline is being updated, what is your opinion on using the <big> and <large> tags, presumably to make the Arabic script more legible? I'm in favor of avoiding them since I'm hoping that, in the future, more browsers will support choosing an appropriate font. These tags are visually distracting and are a cheap fix for a temporary problem. Abjiklɐm (tɐlk) 15:44, 4 October 2015 (UTC)

I'm still against these ugly and static tags, especially since I've learned that the "lang" templates can take care of the problem more elegantly. Our conversation at #In-line Arabic shows that at least Firefox and Chrome adapt to Arabic script if indicated as such. Not sure about Safari, although the basic Arabic font on my iPad is already nicely legible without the "lang" template. If anyone wants to compare with/without template: Arabic diacritics#Alif waslah contains both cases. - HyperGaruda (talk) 16:33, 4 October 2015 (UTC)

Capitalizing the definite articles in templates[edit]

Should the definite article be capitalized in navigation templates where Arabic words are listed in horizontal and alphabetical order? I ask because I've been discussing the Template:Mosques in Palestine with another user who is arguing that because each article stands alone, the definite article should be capitalized. I believe, because the definite article is basically a formality, that it should not be emphasized and thus should be lowercase while only the main word should be capitalized. I think capitalizing the definite article for each item in the list muddies the alphabetical order because the emphasis becomes shifted to the definite article instead of the main word getting prioritized. For example: I think "Ibrahimi Mosque • al-Jawali Mosque • Nabi Yahya Mosque an-Nasr Mosque" is preferable to "Ibrahimi Mosque • Al-Jawali Mosque • Nabi Yahya Mosque • An-Nasr Mosque". The only time I think the definite article should be capitalized is for the first item in the list. I could not find a specific guideline in MoS Arabic for templates so I wonder what the policy should be here. --Al Ameer (talk) 05:24, 25 October 2015 (UTC)

Since each entry is basically a separate sentence, I'd say capitalise the first letter, regardless of being "al" or not. The same has been the case for the initial "The" in other templates such as Template:Andrew Lloyd Webber (forgive me for comparing to a musical writer, but this came up first in my mind). Of course any other "al" should not be capitalised. - HyperGaruda (talk) 07:39, 26 October 2015 (UTC)
@HyperGaruda: I see your point, but I still think only the first word of a particular row (section) should have its definite article capitalized for Arabic. With the English "The", the following word is not exactly attached to the definite article like "al-" is attached to the subject word because a hyphen is not used in the former. I also think the lowercase style takes less emphasis away from the main word, which is even more relevant for an alphabetically ordered list), and simply looks better (at least to my eyes). I'm not exactly sure what the process here is for amending or adding to the current guidelines, but it would be beneficial to MoS Arabic if a definitive policy could be set regarding the capitalization of the definite article in templates so that it could be applied throughout the encyclopedia. I understand the argument that my question is answered by the following guideline: "Al-" ... always written in lower case (unless beginning a sentence), and a hyphen separates it from the following word, but I think there should be clarification regarding stand-alone words in a list. Further input from more users like yourself who are active on MoS Arabic would be nice. --Al Ameer (talk) 03:46, 27 October 2015 (UTC)
Well, I am the other editor who thinks that list elements are like the beginning of a new sentence, see the discussion at Template_talk:Mosques_in_Palestine#Capitalization_of_the_definite_article. In this regards, list elements are like Wikipedia article titles, and are as a rule capitalized, see Al-Aqsa Mosque and all others. Debresser (talk) 22:07, 27 October 2015 (UTC)

Pinging Francis Schonken, Abjiklam and Khestwol for some more input. - HyperGaruda (talk) 06:00, 28 October 2015 (UTC)

Templates related to Arabic[edit]

I have tried to find templates related to Arabic, excluding navigation and message templates. It is probably a good idea to include these in the MoS, but I would like to hear your comments about them and if there are more which may need a mention in the MoS. - HyperGaruda (talk) 08:51, 3 November 2015 (UTC)


Already mentioned in MoS. - HyperGaruda (talk) 08:51, 3 November 2015 (UTC)


In combination with |ar. Already mentioned in MoS. - HyperGaruda (talk) 08:51, 3 November 2015 (UTC)


In combination with |ar. Same effect as {{lang}}, but used for entire paragraphs that need to be right-aligned.

  • I think its use should be discouraged, since entire texts in Arabic are prohibited per WP:USEENGLISH. - HyperGaruda (talk) 08:51, 3 November 2015 (UTC)


Gives IPA pronunciation.

{{Ar icon}}[edit]

For use after external links to indicate that the linked site is written in Arabic.

{{Infobox Arabic term}}[edit]

Infobox with all the possible renderings of an Arabic term.

  • Should only be used in articles whose titles are originally Arabic terms, such as madhhab. I'm not sure about this infobox's position in the text: lead or etymology? - HyperGaruda (talk) 08:51, 3 November 2015 (UTC)

{{Arabic name pattern}}[edit]

Infobox analysing the different parts of an Arabic name.

  • Should be used for articles about persons with Arabic names. In that case, it would be nice if it is possible to integrate it into {{Infobox person}}. Anyone with more experience? - HyperGaruda (talk) 08:51, 3 November 2015 (UTC)