Proposal to encode an Arabic honorific used in Christian texts · Proposal to encode an Arabic...
8
1 L2/20-081 Proposal to encode an Arabic honorific used in Christian texts Roozbeh Pournader (WhatsApp) and Lorna Evans (SIL International) March 10, 2020 Background The Unicode Technical Committee, in its recent meetings, has accepted eighteen Arabic honorifics proposed by the first author and others. Only characters for which we could find examples in running text in published material were proposed. Since, we have found another honorific in published material, this time in Christian religious texts. Proposal Encode the following character in the Unicode Standard: Glyph Codepoint Name FDCF ARABIC LIGATURE SALAAMUHU ALAYNAA The main character properties should be as follows: FDCF;ARABIC LIGATURE SALAAMUHU ALAYNAA;So;0;ON;;;;;N;;;;; The script property for the character should be Arabic. All other properties should be similar to U+FDFD ARABIC LIGATURE BISMILLAH AR-RAHMAN AR-RAHEEM. Notes 1. The phrase ﺳ ﻼ ﻣ ﻪ ﻋ ﻠ ﻴ ﻨ ﺎ(“his blessing on us”) appears to have originated among Egyptian Copts, to later spread among other Arabic-speaking Christians. 2. The character name matches the existing patterns in Unicode character names. The Arabic phrase has been transcribed with a key similar to that used in U+FDFD ARABIC LIGATURE BISMILLAH AR-RAHMAN AR-RAHEEM and the Quranic characters accepted at U+08D5..U+08D2 (see L2/14-105), as opposed to U+FDF0..U+FDFB and U+0610..U+0613. This is because the former pattern is more common among Arabic speakers. 3. The following twenty-three forms exist in some honorific fonts, but we haven’t yet found evidence for their usage in published material. They may be proposed later:
Transcript of Proposal to encode an Arabic honorific used in Christian texts · Proposal to encode an Arabic...
1
L2/20-081ProposaltoencodeanArabichonorificusedinChristiantextsRoozbehPournader(WhatsApp)andLornaEvans(SILInternational)March10,2020
BackgroundTheUnicodeTechnicalCommittee,initsrecentmeetings,hasacceptedeighteenArabichonorificsproposedbythefirstauthorandothers.Onlycharactersforwhichwecouldfindexamplesinrunningtextinpublishedmaterialwereproposed.Since,wehavefoundanotherhonorificinpublishedmaterial,thistimeinChristianreligioustexts.
ProposalEncodethefollowingcharacterintheUnicodeStandard:
Glyph Codepoint Name
FDCF ARABICLIGATURESALAAMUHUALAYNAA
Themaincharacterpropertiesshouldbeasfollows:FDCF;ARABIC LIGATURE SALAAMUHU ALAYNAA;So;0;ON;;;;;N;;;;;
ThescriptpropertyforthecharactershouldbeArabic.AllotherpropertiesshouldbesimilartoU+FDFDARABICLIGATUREBISMILLAHAR-RAHMANAR-RAHEEM.
Notes1. Thephrase انيلع همالس (“hisblessingonus”)appearstohaveoriginatedamongEgyptian
Copts,tolaterspreadamongotherArabic-speakingChristians.2. ThecharacternamematchestheexistingpatternsinUnicodecharacternames.TheArabic
phrasehasbeentranscribedwithakeysimilartothatusedinU+FDFDARABICLIGATUREBISMILLAHAR-RAHMANAR-RAHEEMandtheQuraniccharactersacceptedatU+08D5..U+08D2(seeL2/14-105),asopposedtoU+FDF0..U+FDFBandU+0610..U+0613.ThisisbecausetheformerpatternismorecommonamongArabicspeakers.
3. Thefollowingtwenty-threeformsexistinsomehonorificfonts,butwehaven’tyetfoundevidencefortheirusageinpublishedmaterial.Theymaybeproposedlater:
2
Glyph Spelledoutform Glyph Spelledoutform
! % مالس
01/عمجا مهيلع % اهمحر
% ناوضر
01/عمجا م8يلع % امهمحر
ه;لع % تاولص " % نهمحر
ا8يلع % تاولص ! مهA سدق
ام8يلع % تاولص " امهA سدق
مهيلع % تاولص # # ەA سدق فEFGلا
$ مهيلع % تاولص01/عمجا Lاعت % لجع
فEFGلا هجرف
3
% ه;لع % ةمحر
% هظفح
ا8يلع % ةمحر
% ا8ظفح
م8يلع % ةمحر % م8ظفح
ام8يلع % ةمحر $ العو لج
ن8يلع % ةمحر
4
Sampleofusage
Figure1.Exampleofusagefromal-Nasrī2019,p.653.
Figure2.ExampleofusagefromJatlāwī2017,p.264.
5
Figure3.Thehonorificinspelled-outcalligraphicform,fromal-Nasrī2019,p.641.
Bibliography1. Al-HādīJatlāwī.2017.al-Ma’nīal-sahīhli-Injīlal-Masīh( حيسملا ل7جنإل حيحصلا 0/عملا ).Āfāq,
Tunis.ISBN978-614-430-068-8.2. Fathīal-Nasrī.2019.Adwā’unalāSiyaral-’Anbiā’:al-’Anbiā’al-’Awwalūn( :ءاB7نألا @?س <ع ءاوضأ
نولوألا ءاB7نألا ).Al-Furāt,Beirut.ISBN978-0-9566897-6-4.
6
ISO/IECJTC1/SC2/WG2PROPOSALSUMMARYFORMTOACCOMPANYSUBMISSIONSFORADDITIONSTOTHEREPERTOIREOFISO/IEC10646
A.Administrative
1.Title:ProposaltoencodeanArabichonorificusedinChristiantexts2.Requester’sname:RoozbehPournaderandLornaEvans3.RequesterType:ExpertContribution4.Submissiondate:March10,20205.Requester’sreference,ifapplicable:N/A6.Chooseoneofthefollowing: Thisisacompleteproposal:Yes (or)Moreinformationwillbeprovidedlater:No
B.Technical–General
1.Chooseoneofthefollowing: a.Thisproposalisforanewscript(setofcharacters):No Proposednameofscript:N/A b.Theproposalisforadditionofcharacter(s)toanexistingblock:Yes Nameofexistingblock:ArabicPresentationForms-A2.Numberofcharactersinproposal:13.Proposedcategory:A-Contemporary4.Isarepertoireincludingcharacternamesprovided?Yes
a.IfYES,arethenamesinaccordancewiththe“characternamingguidelines”inAnnexLofP&Pdocument?Yesb.Arethecharactershapesattachedinalegibleformsuitableforreview?Yes
5.Fontsrelated:a.WhowillprovidetheappropriatecomputerizedfonttotheProjectEditorof10646forpublishingthestandard?LornaEvansb.Identifythepartygrantingalicenseforuseofthefontbytheeditors(includeaddress,e-mail,ftp-site,etc.):SILInternational
6.References:a.Arereferences(toothercharactersets,dictionaries,descriptivetextsetc.)provided?Yesb.Arepublishedexamplesofuse(suchassamplesfromnewspapers,magazines,orothersources)ofproposedcharactersattached?Yes
7.Specialencodingissues:Doestheproposaladdressotheraspectsofcharacterdataprocessing(ifapplicable)suchasinput,presentation,sorting,searching,indexing,transliterationetc.(ifyespleaseendorseinformation)?Yes
8.Additionalinformation:SubmittersareinvitedtoprovideanyadditionalinformationaboutPropertiesoftheproposedCharacter(s)orScriptthatwillassistincorrectunderstandingofandcorrectlinguisticprocessingoftheproposedcharacter(s)orscript.Examplesofsuchpropertiesare:Casinginformation,Numericinformation,Currencyinformation,Displaybehaviourinformationsuchaslinebreaks,widthsetc.,Combiningbehaviour,Spacingbehaviour,Directionalbehaviour,DefaultCollation
7
behaviour,relevanceinMarkUpcontexts,CompatibilityequivalenceandotherUnicodenormalizationrelatedinformation.SeetheUnicodestandardathttp://www.unicode.orgforsuchinformationonotherscripts.AlsoseeUnicodeCharacterDatabase(http://www.unicode.org/reports/tr44/)andassociatedUnicodeTechnicalReportsforinformationneededforconsiderationbytheUnicodeTechnicalCommitteeforinclusionintheUnicodeStandard.
C.Technical-Justification
1.Hasthisproposalforadditionofcharacter(s)beensubmittedbefore?NoIfYESexplain:N/A
2.Hascontactbeenmadetomembersoftheusercommunity(forexample:NationalBody,usergroupsofthescriptorcharacters,otherexperts,etc.)?Yes
IfYES,withwhom?TheusercommunityhascontactedSILInternationaltohelpgetthecharacterencodedinUnicode
IfYES,availablerelevantdocuments:N/A3.Informationontheusercommunityfortheproposedcharacters(forexample:size,demographics,informationtechnologyuse,orpublishinguse)isincluded?Yes
Reference:Seeabove4.Thecontextofusefortheproposedcharacters(typeofuse;commonorrare):Rare
Reference:N/A5.Aretheproposedcharactersincurrentusebytheusercommunity?Yes
IfYES,where?Reference:Seeabove6.AftergivingdueconsiderationstotheprinciplesintheP&PdocumentmusttheproposedcharactersbeentirelyintheBMP?Yes
IfYES,isarationaleprovided?Yes.Needtobenexttosimilarcharacters.IfYES,reference:N/A
7.Shouldtheproposedcharactersbekepttogetherinacontiguousrange(ratherthanbeingscattered)?N/A8.Cananyoftheproposedcharactersbeconsideredapresentationformofanexistingcharacterorcharactersequence?Yes
IfYES,isarationaleforitsinclusionprovided?YesIfYES,reference:Similaritytoalready-encodedcharactersanddifferentusage.
9.Cananyoftheproposedcharactersbeencodedusingacomposedcharactersequenceofeitherexistingcharactersorotherproposedcharacters?Yes
IfYES,isarationaleforitsinclusionprovided?YesIfYES,reference:Seeabove
10.Cananyoftheproposedcharacter(s)beconsideredtobesimilar(inappearanceorfunction)to,orcouldbeconfusedwith,anexistingcharacter?No
IfYES,isarationaleforitsinclusionprovided?N/AIfYES,reference:N/A
11.Doestheproposalincludeuseofcombiningcharactersand/oruseofcompositesequences?No
IfYES,isarationaleforsuchuseprovided?N/AIfYES,reference:N/A
Isalistofcompositesequencesandtheircorrespondingglyphimages(graphicsymbols)provided?N/A
IfYES,reference:N/A12.Doestheproposalcontaincharacterswithanyspecialpropertiessuchascontrolfunctionor
8
similarsemantics?NoIfYES,describeindetail(includeattachmentifnecessary):N/A
13.DoestheproposalcontainanyIdeographiccompatibilitycharacters?NoIfYES,aretheequivalentcorrespondingunifiedideographiccharactersidentified?N/AIfYES,reference:N/A
