Jump to content

Template talk:Lang-ar

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

definition

[edit]

Please stop using this template. Replacing very simple links like Arabic saves a minimum of time and puts unnecessary strain on the servers. Worst of all, people use this template to replace existing links, which is unbelievably pointless.

Peter Isotalo 20:21, 15 October 2005 (UTC)[reply]

Use {{ar}} instead, please. dab () 12:52, 7 January 2006 (UTC)[reply]

I guess I'm not really getting it but I'm not really getting it! I dont see the diff. on either of them. how should the arabic names then be formatted? (ar هيان بن بيان) as such? let me know please. Wilis.azm 06:02, 31 January 2006 (UTC)[reply]

deprecate

[edit]

use {{lang|ar|...}}, we don't want the clutter of a separate template for every language on earth. dab () 11:42, 3 October 2006 (UTC)[reply]

That would be an okay replacement if it adds the correct CSS classes and language name. The replacement that was suggested on the template was much longer, so I don't think anybody is going to use it. Anyway, I can't see a good reason not to have these specific templates for major languages. Kusma (討論) 06:41, 14 February 2007 (UTC)[reply]
indeed, there is nothing wrong with using both {{lang|ar|...}} and {{lang-ar|...}} except for the unsatisfactory situation that we'll have two standards of marking up the very same thing. If we could agree that we prefer {{lang|ar|...}}, people could still use {{lang-ar|...}} as much as they like, but we could send in a bot that will subst: occurrences. For the purposes of entering Arabic, nothing will change, but we'll end up with more standardized markup. dab (𒁳) 06:56, 14 April 2007 (UTC)[reply]
Well, {{lang-ar|...}} and {{lang|ar|...}} do different things. {{lang-ar|...}} (adding the language name with correct links) does something visible to newbies, while {{lang|ar|...}} doesn't do anything obvious. I think it is likely that people will write just [[Arabic]]: blah instead of [[Arabic language|Arabic]]: {{lang|ar|blah}}, which will not add the language attribute and cause another page that needs disambiguation. Having a template for every language on earth is an easy way around these problems. Kusma (talk) 07:24, 14 April 2007 (UTC)[reply]

Enlarging the script

[edit]

Could we automatically enlarge the Arabic script so that it reads clearer in articles. --Al Ameer son (talk) 21:15, 5 October 2008 (UTC)[reply]

Is there a way to include a transliteration?

[edit]

I noticed on Jesus in Islam that {{lang-ar|عيسى عليه السلام|`Īsā Alayhi As Salam}} is being used, and I'm guessing the second parameter is supposed to be a transliteration. However, it has no effect: Arabic: عيسى عليه السلام, romanized`Īsā Alayhi As Salam does not display the second parameter at all. Is this a bug, or was it designed not to have any transliteration? Thanks,

-- Joren (talk) 02:48, 26 September 2010 (UTC) (P.S. - I know pretty much nothing about Arabic, so please forgive my ignorance)[reply]

Right now the article uses {{lang-ar|عيسى}} ''{{transl|ar|DIN|ʿĪsā}}'', producing Arabic: عيسى ʿĪsā, if anyone else came here wondering. Shrigley (talk) 18:42, 7 October 2012 (UTC)[reply]

Badr al-Jamali

[edit]

Hi. Can someone take a look at Badr al-Jamali for me? Every time I try to add (1015-1094) after the {{Lang-ar}} template some sort of auto-correct feature jumps in and absorbs the text into the middle of the template.

original text: ({{lang-ar|بدر الجمالى}})
auto-corrected edit: ({{lang-ar|بدر الجمالى}}) (1015-1094

When I then try to rearrange the text the auto-correct feature jumps in again and makes things even messier. Road Wizard (talk) 10:15, 29 September 2012 (UTC)[reply]

I have found that adding the {{lrm}} template fixes the problem:
({{lang-ar|بدر الجمالى}}{{lrm}}, 1015-1094)
According to Template talk:Lang it is a problem with switching between right-to-left and left-to-right unicode character sets. The {{lrm}} template inserts an invisible character that restores the text flow to normal. Road Wizard (talk) 10:51, 29 September 2012 (UTC)[reply]

Edit request on 16 August 2013

[edit]

This template needs to be brought up to date to be in line with other Lang-xx templates. The new source, before the <noinclude> section, should read: {{Language with name|ar|Arabic|''{{{1}}}''|links={{{links|yes}}}}} See Template:Lang-fr for an example. Ibadibam (talk) 22:28, 16 August 2013 (UTC)[reply]

We don't italicise Arabic. It should be
{{Language with name|ar|Arabic|{{{1}}}&lrm;|links={{{links|yes}}}}}
Lfdder (talk) 11:19, 23 August 2013 (UTC)[reply]
Good catch! Why does the ampersand in the LRM need to be coded? Ibadibam (talk) 16:23, 23 August 2013 (UTC)[reply]
That's because otherwise the lrm mark would be rendered, and would disapper when the code was copied and pasted. And the request is Done. :) Sorry about the wait. — Mr. Stradivarius ♪ talk ♪ 09:36, 25 August 2013 (UTC)[reply]

Edit request on 12 September 2013

[edit]

lrm needs to go outside:

{{Language with name|ar|Arabic|{{{1}}}|links={{{links|yes}}}}}&lrm;

Lfdder (talk) 18:19, 12 September 2013 (UTC)[reply]

DoneMr. Stradivarius ♪ talk ♪ 21:55, 12 September 2013 (UTC)[reply]

'Amiri' font

[edit]

Why does this template (or one of its transcluded templates) hardcode the Amiri font. It's nearly illegible, and my default font, DejaVu Sans, is perfectly capable of rendering legible Arabic text. While Amiri has some aesthetic value, it's not suitable for an online encyclopedia.

Since it's hardcoded in the element style, I can't even override it in my user style, not even with the !important tag. This is extremely frustrating, and isn't it bad practice to hardcode fonts (which are downloaded to the user!) into span tags anyway? Why not use a css class I could then override?

Moszczynski (talk) 13:17, 29 October 2013 (UTC)[reply]

it's the Universal Language Selector to blame, not this tpl. — Lfdder (talk) 15:44, 29 October 2013 (UTC)[reply]

LIPIA

[edit]

For the article LIPIA, I use the template {{lang-ar-at|a=the arabic text| t=the transliterated text here}}, for example: ([undefined] Error: {{Lang-xx}}: no text (help)) so we can put the transliteration directly in the template)

 Comment: The |a= and |t= are currently being deprecated, since templates of other languages are using this scheme. For now, call {{Lang-ar-at}} without specifying |a= or |t=. Ex. {{lang-ar-at|the arabic text|the transliterated text here}} Cheers, — Andy W. (talk ·ctb) 05:01, 21 May 2016 (UTC)[reply]

Add lit. parameter per parent template

[edit]

To allow making use of Template:Language with name's {{{lit}}} parameter, I created a sandbox version. While for many related articles, a {{{translit}}} parameter would be helpful, for now we should start with the current Template:Language with name. Please also change full protection to template protection per WP:TEMP-P. Regards, --PanchoS (talk) 17:00, 23 March 2015 (UTC)[reply]

Template-protected edit request on 30 April 2015

[edit]

This template written "ar: " without "()", Fix it by making it "(ar: )" عمار الوائلي (talk) 10:10, 30 April 2015 (UTC)[reply]

Not done: The Lang-x templates are also used in places where brackets are not required, or as part of a longer parenthesis. Alakzi (talk) 17:20, 30 April 2015 (UTC)[reply]

Template-protected edit request on 29 May 2015

[edit]

Please replace the current code with this revision. The &lrm; is no longer needed since it is now being automatically included for all {{lang}}-derived templates using the rtl field. I've also replaced the documentation with the lang-x documentation which better describes the available fields. — Quoth (talk) 09:52, 29 May 2015 (UTC)[reply]

Done Alakzi (talk) 11:21, 29 May 2015 (UTC)[reply]

@HyperGaruda and PanchoS: Template has been merged with Template:Lang-ar-at per closed TfD consensus. Lang-ar-at has been redirected here. Documentation page has been recreated, and documents the extra parameters.

HyperGaruda, are there any Arabic WikiProject MOS guidelines that need updates? PanchoS, thanks for the suggestion. If you see any issues with this template, submit an edit request. Thanks!!! :) — Andy W. (talk ·ctb) 18:10, 24 May 2016 (UTC)[reply]

The template looks as good as it always was, maybe even better since you added "lrm". Adding birth dates was a pain in the a back then, but no more, so kudos to you. I'll take care of MOSAR ;) - HyperGaruda (talk) 18:25, 24 May 2016 (UTC)[reply]
How do you get the script isolated, it is big enough to read but not bold enough to bother the other words. Alexis Ivanov (talk) 23:10, 1 July 2016 (UTC)[reply]
Never mind Alexis Ivanov (talk) 23:13, 1 July 2016 (UTC)[reply]

“Translit.” should be Transcribed

[edit]

The alleged Arabic “transliterations” are actually almost always transcriptions. How can I change the template so it says “transcribed” rather than transliterated?

Kilo77 (talk) 21:19, 25 April 2019 (UTC)[reply]

The layout of the language templates is set in Module:Lang. You'll need to make a proposal at Template talk:Lang to get the process going. In the meantime, note that some cases of transcription of standard Arabic to account for regional variation can be covered as proper transliteration using specialized templates, specifically {{Lang-arq}}, {{Lang-ary}} and {{Lang-arz}}. Ibadibam (talk) 22:13, 25 April 2019 (UTC)[reply]
Ibadibam, Thank you. I posted in the talk page of Module:Lang. Kilo77 (talk) 02:36, 26 April 2019 (UTC)[reply]

Main article has been moved

[edit]

It's "Arabic" now, not "Arabic language". Is there a way to change the link on this template accordingly? Charles Essie (talk) 20:01, 26 July 2019 (UTC)[reply]

doc reverts

[edit]

Editor Mahmudmasri made this edit to the doc page with the edit summary less confusion. I objected to that edit because of the first character in the transliteration positional parameter:

{{lang-ar|عربى|ʕarabī|lit=Arabic|links=no}}

I reverted with an edit summary: IPA is not romanization.

Editor Mahmudmasri objected to my revert and reverted with the edit summary: Who said that was IPA? And you reverted a disambiguation for the visually difficult samples.

Who said that was IPA?:

The first character in {{{2}}} above is U+0295 ʕ LATIN LETTER PHARYNGEAL VOICED FRICATIVE; see IPA Extensions Unicode chart.
In the {{lang-??}} templates, {{{2}}} (and when used, |translit=) identifies the transcription of a non-Latin alphabet to a Latin alphabet – the writing of a word or phrase. IPA is about how a word or phrase is pronounced. Pronunciation is not romanization. The {{lang-??}} templates do not support pronunciation and IPA. For editors who wish to include IPA representations of Arabic pronunciation in articles there is {{IPA-ar}}.

And you reverted a disambiguation for the visually difficult samples:

Disambiguation? Not clear to me what that refers to. Perhaps 'definition' was the intended word.
Documentation can always be better and this doc page has had its basic form for a long time. That 'thing' that I deleted was Editor Mahmudmasri's change in capitalization of an example that doesn't actually work. The original:
{{lang-ar|Arabic|transliteration|lit=literal|links=no}} → Arabic: Arabic, lit.'literal'
Editor Mahmudmasri's change:
{{lang-ar|ARABIC|TRANSLITERATION|lit=LITERAL|links=no}} → Arabic: ARABIC, lit.'LITERAL'
Notice in the actual rendering, there is no 'transliteration' or 'TRANSLITERATION'. This is because in both cases {{{1}}} ('Arabic' and 'ARABIC') are composed of wholly Latin characters. There is no need to romanize text that is already using Latin script so Module:Lang ignores {{{2}}} in these cases.
Perhaps to identify the positional parameters, something like this should be added under Template:Lang-ar § Syntax:
{{lang-ar|<Arabic text>|<transliteration>|<literal>}}
Certainly, the non-functioning example should be removed from the examples table.

Trappist the monk (talk) 11:17, 15 August 2019 (UTC)[reply]

So, your objection is basically to the ʕ symbol. But, did you realize that it could also be used in transliteration? It was just an example and the symbol is often used in linguistic literature. You should have also realized that the transcription was not in IPA, since it contained i-macron.
The last example had some words capitalized to emphasize from the first sight that they were not part of the template's syntax. --Mahmudmasri (talk) 11:55, 15 August 2019 (UTC)[reply]
According to our article Macron (diacritic): "In the International Phonetic Alphabet, the macron is used to indicate a mid-tone"... so pronunciation (though perhaps not IPA compliant). Our article Romanization of Arabic does not appear to support your claim that ʕ ... could also be used in transliteration. Assuming that i-macron is not IPA, the Comparison table suggests that the IPA ʕ symbol should be replaced with one of the several 'accent-like' characters depending on the romanization standard:
Mixing IPA with romanization is not a good idea.
Yeah, I got that the ALL-CAPS was used to distinguish the terms from syntax but that does not change the fact that capitalized or not, a template example using either form does not work so the example itself is pointless.
Trappist the monk (talk) 13:34, 15 August 2019 (UTC)[reply]
I'm not here in a tirade trying to prove I'm right. If you were familiar with Semitic languages, you'd realize that there are no tones in them, so apparently it wasn't a transcription of tones, and IPA is normally written inline, between slashes or squared brackets. --Mahmudmasri (talk) 23:04, 17 August 2019 (UTC)[reply]

Can anyone help me with the lang-ar template in Catalan wikipedia?

[edit]

The lang-ar template in Catalan wikipedia enlarges the word in Arabic. I asked for help to solve this (that the Arabic word use the same font of the Catalan text), but on Catalan wikipedia team no one controls enough over the templates language to correct it. There is also a problem when transcription is added: the order of the words is reversed and the transcribed word is placed before the Arabic word. Could anyone knowing how templates language works give me a hand? Or could you direct me where someone could help me? Thank you very much. --CarlesVA (talk) 19:11, 20 February 2021 (UTC)[reply]

I suspect that you have to change ca:Mòdul:Llengua/script particularly this line:
s["Arab"] = { 	-- àrab
	style = "font-family: 'Iranian Sans', Arial Unicode MS, Code2000, Traditional Arabic, sans-serif; font-size: 133%; direction: rtl; unicode-bidi: embed; font-style: normal; font-weight: normal;"
}
If you haven't already, you might want to talk to ca:Usuari:Vriullop. They might be the best person to talk to because they are the author of ca:Mòdul:Llengua and its supporting modules.
You might ask if it is possible to add the equivalent of en.wiki's |size= parameter so that the default fontsize in the style attribute can be overridden when needed. Apparently some styling support is available in the module if you can get template support for |sc=; see lines 24–32.
It isn't obvious to me that {{lang-ar}} at ca.wiki supports transcriptions; see the output code at lines 34–43.
I note that there is a bug in line 10 of the module...
Trappist the monk (talk) 20:05, 20 February 2021 (UTC)[reply]
Thank you, @Trappist the monk:. --CarlesVA (talk) 20:11, 21 February 2021 (UTC)[reply]

Template-protected edit request on 20 July 2021

[edit]

Currently, "Arabic" links to Arabic language, which is a redirect to Arabic. It should directly link to Arabic. Nehme1499 22:22, 20 July 2021 (UTC)[reply]

No. To avoid having to maintain a list of exact article titles, all of the {{lang-??}} templates link to their respective articles through '<language-name> language' redirects.
Trappist the monk (talk) 22:46, 20 July 2021 (UTC)[reply]
To editor Nehme1499:  Not done: Some language links that do not have "language" in the title do not go to the language, for example, see English, which is a dab page. That is why these redirects exist, so there can be consistency in the Lang templates. Whether it's the English language or the Arabic language, the links get readers where they expect to be. There doesn't seem to be anything at WP:R that would prohibit usage of redirects in templates (or modules) for this purpose. P.I. Ellsworth  ed. put'r there 07:39, 21 July 2021 (UTC)[reply]

Font stays the same?

[edit]

On my MacBook, the Arabic font with or without the template stay the same. Is there any way to solve this? This is also the case with other non-Latin scripts. Nehme1499 13:51, 25 November 2021 (UTC)[reply]

{{lang-ar}} does not manipulate font. This example from the template doc:
{{lang-ar|عمّون}}
produces this output:
[[Arabic language|Arabic]]: <span lang="ar" dir="rtl">عمّون</span>[[Category:Pages using Lang-xx templates]]
nothing in that styles the font. It is common for browsers to select a font to render non-Latin-script text that is different from the font it uses to render Latin-script text. For example, my browser renders these three lines using two distinctly different fonts:
this is text ← plain text
this is text{{lang|ar|this is text|italic=no}}
this is text ← decomposing the above to its minimum: <span lang="ar">this is text</span>
Did you recently update your browser? What happens when you view the Arabic text using a different browser? Do you have custom font settings in your css here or in your browser?
Trappist the monk (talk) 14:11, 25 November 2021 (UTC)[reply]
Changing browser doesn't do anything. On my PC, having Arabic text "naked" or inside this template produce different fonts (the one in this template is "clearer", if it makes sense). On my Mac, even your three examples produce the same text. Nehme1499 14:40, 25 November 2021 (UTC)[reply]
Hence my question, Did you recently update your browser? The 'problem' is not with {{lang-ar}}.
Trappist the monk (talk) 14:42, 25 November 2021 (UTC)[reply]
No, I didn't do anything to this (or any) browser. I just got this Mac, and noticed the difference in how Arabic text is displayed here compared to how it is displayed on my old PC when inside this template. If lang-ar shouldn't change the font, why does it do so on my other PC? I assumed that was the intended use of this template, to display Arabic text in a "clearer" font. Nehme1499 14:44, 25 November 2021 (UTC)[reply]
The template doesn't change anything as I demonstrated above. Your PC browser (and my browser) are correctly reacting to the lang="ar" attribute in the <span>...</span> html tag that wraps the Arabic text. Your MacBook is ignoring that attribute. The purpose of this template and all of the other templates supported by Module:Lang is to tell browsers and screen readers that the wrapped text is not English so may require special handling to display correctly and, for screen readers, to be pronounced correctly. Proper display/pronunciation is the responsibility of the browser/screen reader. This template's responsibility is to correctly format the Arabic text so that browsers and screen readers understand that the Arabic text is Arabic. There is no evidence that the template is failing in its duty (if there were such evidence, you would not be the only editor making note of it).
Trappist the monk (talk) 15:12, 25 November 2021 (UTC)[reply]
I'm not asserting that it's this specific template's "fault". I'm just trying to understand if there was a way for my Macbook to adapt the font the same way my PC does. Nehme1499 15:35, 25 November 2021 (UTC)[reply]

How to transliterate?

[edit]

I recently wrote the article for the video game Special Force and wanted to include its native Arabic name (القوة الخاصة) plus transliteration. Since I do not speak the language, I was looking at online transliteration tools, but they produce wildly different results. Crucially, not one of them correctly reproduce the examples from this template's documentation. Please see the table below.

Online transliteration results
Input Per docs Google Translate Arabic Alphabet Academy Arabic Transliteration Tool Branah.com Lexilogos MyLanguages.org
عمّون ʻAmmūn emmwn ʿm̃wn ʿmūn ʿmmwn ʿmwūn emwn
الصديق Aṣ-Ṣiddīq alsadiq ạlṣãdīqu ālṣdīq ʾalṣdyq al-ṣdīq alsdyq
عربى ʿarabī eurabaa ʿarabiy̱uⁿ̃ ʿrb ʿrbỳ ʿrbi 'erba
القوة الخاصة alquat alkhasa ạl̊qūãẗu ạl̊kẖāṣãẗa ālqūt l-khāṣt ʾalqwẗ ʾalẖʾṣẗ al-qūẗ al-ẖāṣẗ alqwh alkhash

Any help on getting this right would be greatly appreciated. Regards, IceWelder [] 10:57, 27 September 2023 (UTC)[reply]

This might not be the best place to ask that question. Have you considered asking at Wikipedia:WikiProject Arabic or Wikipedia:WikiProject Intertranswiki/Arabic? Perhaps someone at one of those two projects can help.
Trappist the monk (talk) 12:00, 27 September 2023 (UTC)[reply]
Thanks for the hint. I posted a referral on those two projects' talk pages, as well as at Wikipedia talk:WikiProject Arab world. IceWelder [] 16:00, 27 September 2023 (UTC)[reply]
You might also want to ask at Wiktionary's Information desk or Tea room (long page). 115.188.126.180 (talk) 23:05, 29 September 2023 (UTC)[reply]

@IceWelder: The transliteration is Al-Quwwa al-Khassa and/or Al-Quwwah al-Khassah.

PS: The letter s must be doubled (ss) in the second word "الخاصّة" because there is a shadda on the Arabic letter "sād".--TheEagle107 (talk) 20:19, 1 October 2023 (UTC)[reply]

@TheEagle107: Thank for these references! I found another spelling, "Al Quwwa el-Khassa", in a paper. Do you know why there are that many different interpretations of the source word? IceWelder [] 20:36, 1 October 2023 (UTC)[reply]
@IceWelder: The prefix "al-" or "el-" in Arabic means "the". "Al" is the more formal "standard" pronunciation and "el" is more how normal people actually say it when they're talking. For example, in the Arabic language, the word "Allah" is an Arabic name used in Islam to refer to God, which being a grammatical derivative of "al-Ilah", meaning "the God" or "the Only God"—the prefix "Al" in Arabic is defined as "the" and is connected to the suffix "ilah," which means “god.”

For more detailed information, see:

I hope this helps. All the best.--TheEagle107 (talk) 21:48, 2 October 2023 (UTC)[reply]

Thank you for the clarification, @TheEagle107! When I was about to implement this, @Sheila1988 added a transliteration directly to the article: "al-quwwa al-khāṣṣa". I suppose this is also correct? IceWelder [] 19:48, 3 October 2023 (UTC)[reply]
yes, Wiktionary is a good source for clarification. The dot under the S shows that it is the letter Sad and not Sin. Sheila1988 (talk) 19:56, 3 October 2023 (UTC)[reply]
@IceWelder: The only problem is that some letters need to be capitalized, especially Q & K. Source: "ヒズブッラー" [Hizbullah] (PDF). CMEPS-J.net (in Japanese). Contemporary Middle East Political Studies in Japan.net. p. 10.

Kind regards.--TheEagle107 (talk) 20:45, 3 October 2023 (UTC)[reply]

Roger that. It's a shame that we still do not have a good online tool for this, but at least it is correct for this particular article (which, by the way, is on DYK today). Thanks everyone. IceWelder [] 21:00, 3 October 2023 (UTC)[reply]
Hi @IceWelder,
اَلْقُوَّة اَلْخَاصَّةِ = Al-qwaut al-kash OR Al-qwauh al-kash Gerges (talk) 23:25, 14 December 2023 (UTC)[reply]