Collected Precedents of the S.C.A.: Non-Roman Alphabets / Transliteration

Name Precedents: Non-Roman Alphabets / Transliteration

Laurel:	Date: (year.month.date)	Precedent:
Shauna of Carrick Point	2004.05	The element al-Mãkdukht had several problems. First, al-Jamal states that Mãhdukht is a transcription error for M{a-}hdukht The name M{a-}hdukht is a Persian name; combining it with the Arabic al mixes Persian and Arabic in a single name phrase, in violation of RfS III.1.a. The byname al-Zarqá has a transcription error as well; the correct form is al-Zarqa'. In order to register the name, we have dropped the problematic elements and corrected the transcription of the remaining parts, giving M{a-}dukht al-Zarqa'. [M{a-}hdukht al-Zarqa',05/04, A-Trimaris]
François la Flamme	2003.11	Submitted as Zebeebah al-Kharqaa, the spelling of the given name has been changed to match the transcription of the byname. Questions were raised in commentary as to whether al-Kharqaa is a reasonable form meaning 'clumsy.' As the name is documented from Hans Wehr's Dictionary of Modern Written Arabic, a well-regarded dictionary of Arabic, we will give the submitter the benefit of the doubt. [Zebeeba al-Kharqaa, 11/2003, A-Meridies]
François la Flamme	2003.10	An additional issue noted by al-Jamal is that diacritical marks are not used throughout the name. They are included in the byname al-Raqq{a-}sa and omitted elsewhere. Diacritical marks must be used or omitted consistently. As they are omitted from the rest of the name, we have dropped from al-Raqq{a-}sa. [Masala al-Raqqasa, 10/2003, A-Atenveldt]
François la Flamme	2003.10	The question was raised as to whether Harofeh is a reasonable transliteration of the period Hebrew byname meaning 'the physician'. A more typical period transliteration would be ha-Rofe. In the cases of languages that do not use Roman alphabets (such as Chinese, Russian, Arabic, Hebrew, etc.) we register transliterations using period transliteration systems and modern standard transliterations systems. The form Harofeh is a modern transliteration of this period name element, as for example in the names of the Assaf Harofeh Hospital (http://www.assafh.org/) and the Shmuel Harofeh Hospital (http://www.us-israel.org/jsource/Politics/healthmin.html), both hospitals located in Israel. As it is a modern standard transliteration of a period name, it is registerable. [Avraham Harofeh, 10/2003, A-Atlantia]
François la Flamme	2003.09	Submitted as Waldemar Stanislav of White Mountain, the submitter requested authenticity for Czech and allowed minor changes. Nebuly provided information regarding authentic forms of this name: Waldemar is not, nor has it ever been a Slavic name. Contrary to claims made in the LoI, Waldemar does not appear in Wickenden. It certainly doesn't appear under the header Valdimar, because there is no such header in that book. Neither does the name appear in the SSNO (Dictionary of Old Polish Names). It turns out that Waldemar is a Danish royal name circa 1200, and the name of a Margrave of Brandenburg circa 1300 (Bahlow, s.n. Waldemar). Since the name is documented from eastern Germany, and since German names were frequently used among the Poles and Czechs, Waldemar is a fine given name. The second element Stanislav can be documented to Poland by the beginning of the 13th century (SSNO s.n. Stanis{l/}aw), but the name is probably older. To be orthographically consistent, the spelling should be changed to Stanislaw, since v and w represent the same sound in this name. Before 1500, Czech spelling was closer to Polish, so I would use the 13th century Polish spelling Stanislaw. To meet the client's desire for a more authentic Czech name, we should convert this second element into a patronym Stanislowow or Stanislawsky (the second form is more common for patronyms formed from -ow names). This conversion makes the name more authentic by eliminating the double given name. [Waldemar Stanislaw of White Mountain, 09/2003, A-Trimaris]
François la Flamme	2003.09	This submission is being returned for lack of evidence of Shiao as a valid transliteration. Languages that do not use Roman character sets are registerable so long as a single transliteration system is used throughout the entire name. The transliteration Shiao 'small, tiny, insignificant' uses no transliteration system that we were able to identify. Yin Mei Li, Golden Pillar, explains: [T]his name appears to mix Romanization systems, using an as-yet-unidentified convention for the given name's first syllable, and either Wade-Giles or Pinyin for the surname and the given name's second syllable. The Chinese character for Shiao, the first syllable of this submitted given name is relatively easy to identify because there appears to be only one Chinese character with the intended meaning that a typical American might spell as Shiao. However, this character is Romanized as Hsiao in Wade-Giles (Mandarin dialect), Siao in a common modified Wade-Giles, Xiao in Pinyin (Mandarin dialect) and Siu in Yale (Cantonese dialect). Among the five conventions and two modified conventions used in her books, Yin could not find any convention that Romanizes the subject Chinese character as shiao. Even the submitter's cited documentation, identified in the LoI, uses standard Pinyin and Yale Romanizations, rather than whatever convention the submitter used. [...] The other two syllables, Lin and Mei, are Wade-Giles or Pinyin Romanizations. These two Romanizations are identical for these two Chinese characters partially because, in Mandarin, these syllables involve sounds that are more common in European languages. However, dialects can vary enough that both of these syllables can have very different Romanizations for other dialects. For example, depending on which Chinese character is used for surname Lin, its Yale Romanization is Lam or Leun. Mui is the Yale Romanization for the Chinese character that is the given name's second syllable. From the information provided by Golden Pillar, forms of this name using a single transliteration system throughout the entire name would be Lin Hsiao Mei using Wade-Giles, Lin Xiao Mei using Pinyin, and Lam Siu Mui or Leun Siu Mui using Yale. Since the submitter allows no changes, we were unable to change this name to use a consistent transliteration system in order to register this name. [Lin Shiao Mei, 09/2003 LoAR, R-Outlands]
François la Flamme	2003.08	Listed on the LoI as 'A'isha bint Rashid al  Andalusi, this name appeared on the forms as A'ishah bint Rashid al Andalusi. She requested an authentic name for the Middle East. There are a variety of different ways to transliterate Arabic into English. We register any of them, only requiring that a single transliteration system be used for the entire name. al-Jamal observed: Common transliterations of the name of Muhammad's daughter include: 'A'isha A'isha, Ayisha, and Ayesha. A'ishah should be equally acceptable. We have therefore returned the name to its submitted form. As submitted, the byname al Andalusi says that Rashid is from al-Andalus, not A'ishah. If she is the one from al-Andalus, the correct form is al-Andalusiyyah. We have not made this change, as either meaning is acceptable. However, we have added a hyphen between the article and the byname, as it is generally used in transcriptions of Arabic. [A'ishah bint Rashid al-Andalusi, 08/2003 LoAR, A-Caid]
François la Flamme	2003.08	Listed on the LoI as Aminah al-Zarqua, the form and the documentation listed the byname as al-Zarqa. The submitted form of the given name and byname use different transliteration systems. When registering Arabic names, a single transliteration system must be used consistently throughout the name. Therefore, registerable forms of this name are Amina al-Zarqa and Aminah al-Zarqah. As the latter tranliteration retains the submitted spelling of the given name, we have used that form when registering this name. [Aminah al-Zarqah, 08/2003 LoAR, A-West]
François la Flamme	2003.08	The submitted yobina Genkur� uses a non-standard transliteration. The term romanji is used to describe Japanese words rendered using a Roman character set. There are several standard transliteration systems used in writing romanji. Any of these transliteration systems may be used in an SCA name, but one transliteration system must be used throughout the entire name. Genkur� uses the Hepburn system for transliteration. However, the Hepburn system uses a macron over letters rather than a caret. Therefore, this name is correctly written as Genkur{o-} using the Hepburn system, not Genkur�. As macrons can be difficult to render in publishing, they are often left off. Hence T{o-}ky{o-} is rendered as Tokyo. Solveig Throndardottír, in her book Name Construction in Medieval Japan (NCMJ) uses a modified Hepburn system that would render this name as Genkurou. Therefore, this yobina is registerable as Genkur{o-}, Genkuro, or Genkurou, depending upon which transliteration system the submitter chooses to use. [Minamoto Genkur� Tanekagé, 08/2003 LoAR, R-Artemisia]
François la Flamme	2003.06	Submitted as Lán Ying, we have removed the accent from the byname. Pinyin and Wade-Giles are the two main systems for transliterating Chinese names using the Roman alphabet. Golden Pillar provided information regarding the accents and diacritical marks used in these transliteration systems: First, Yin strongly recommends that Pelican and Laurel not register accent marks, or most other diacritical marks, with Chinese names. In Pinyin, and in many Wade-Giles, Romanizations, these marks are, in some sense, similar to the marks in deFelice, providing pronunciation information without being part of the actual characters in the name. With a few exceptions in Wade-Giles, the marks are one of two modern methods for conveying pronunciation tones, and the other method (numbers at the end of each syllable) is much more common. Further, both numbers and marks are most frequently omitted when Romanizing Chinese characters for Western readers from the general public. Please note that, if accent and diacritical marks are registered in Romanized Chinese names, then the much more common number-at-end-of-syllable should be likewise registerable. (By the way, if the number convention is registerable, this name would more frequently be Romanized as Lan2 Ying1 than as Lán Ying). Given this information, we will omit diacritical marks and tonal indicators (numbers at the end of each syllable) when registering Chinese names. We have changed Lán to Lan in this name to remove the accent, which is used as a pronunciation indicator. [Lan Ying, 06/2003 LoAR, A-Middle]
François la Flamme	2002.12	This name was submitted as Aíbinn ingen Senáin hui Néill with a punctum delens (it looks like a dot) over the S in Senáin. When Gaelic is being represented using the Roman alphabet, letters with the punctum delens are rendered with an appended h; thus, S with a punctum delens becomes Sh in standard transliteration. For registration purposes, we use this standard transliteration method and so have registered this name using the standard form Shenáin. The submitter is welcome to use the form Senáin with the punctum delens over the S when writing her name, if she wishes. [Aíbinn ingen Shenáin hui Néill, 12/2002, R-Outlands]
François la Flamme	2002.10	Submitted as Vizlaw Ivanovitch Nevsky, the submitter requested authenticity for 11th to 13th C Russian. As submitted, this name mixed transliteration systems, which has previously been cause for return. Wickenden (3rd ed., p. 399 s.n. Voislav) dates the forms Vojslav to 1071 and Voyslav to 1174. Thus, the alternate transliteration Voislav is also authentic for this time period. Wickenden (3rd ed., p. 73 s.n. Donskii) gives an example of a byname derived from the name of a river. This entry says that Donskii means "from the river Don region" and dates Dmitrii Donskii to c. 1375. From this example, Nevskii would be a form of the submitted byname Nevsky, 'from the river Neva region', appropriate for c1375. Using the name elements cited above as a guideline for the submitter's desired time period, we have changed this name to use a consistent transliteration system in order to register this name. [Voislav Ivanovitch Nevskii, 10/2002, A-Atenveldt]
François la Flamme	2002.09	Listed on the LoI as F{a-}'izah al-Zaqra, we have corrected the typo in the byname. The given name was submitted as Faizeh and changed at Kingdom to a form documented from a modern name book, as no documentation could be found for Faizeh. The form Fa'iza is dated to period in Juliana de Luna's article "Jewish Women's Names in an Arab Context: Names from the Geniza of Cairo" (http://heraldry.sca.org/laurel/names/geniza.html). Fa'izah is an alternate transliteration of Fa'iza. We have added the glottal stop to the end of the byname, al-Zarqa', for consistency, as it is included in the given name. [Fa'izah al-Zarqa', 09/2002 LoAR, A-Caid]
François la Flamme	2002.09	Submitted as Fatimah al-Zarga' al-Rakkasa, we have corrected the typo in the byname al-Zarqa'. When registering names from languages that do not use the Roman alphabet, a consistent transliteration system must be used throughout the name. Therefore, we have modified the second byname to the form al-Rakkasah so that it uses the same transliteration system as the given name Fatimah. [Fatimah al-Zarqa' al-Rakkasah, 09/2002 LoAR, A-Caid]
François la Flamme	2002.08	Submitted as Chavah bat Mordecai, we have modified the name to use a consistent transliteration system. [Chavah bat Mordechai, 08/2002, A-Outlands]
François la Flamme	2002.07	An additional issue is that this name uses inconsistent transliteration. Al-Jamal wrote: Okay, first off, either drop the final "h" from Hameedah (which we can't do if she's applying the legal name allowance, which only permits the exact legal name) or add it to Farisa and Ramia. "Submitted as Khadijah bint Mika'il al-Zarqa, it combines two different forms of transliteration. We have changed the spelling of the byname to make the entire name consistent." (Elsbeth Anne Roth, LoAR September 2000, p. 12) [Farisa Ramia Hameedah bint Kathoum, 07/2002, R-Atenveldt]
François la Flamme	2002.07	al-Jamal provided commentary regarding other issues with this name: Abdul Majeed is more usually transliterated 'Abd al-Majid. [Mu'Alim Rami Kathoum ibn Abdul Majeed, 07/2002, R-Atenveldt]
François la Flamme	2002.06	From Pelican: Capitalization of Gaelic Particles: mac versus Mac A submission this month raised discussion regarding whether capitalization of particles in Gaelic bynames carried a particular meaning or not. Given the amount of discussion and varying opinions, a clarification is in order. Capitalization of name elements in period Gaelic documents was less consistent than it is now, but it was not completely random. Most sources that reference Irish Gaelic names use standardized transliteration rules for rendering Gaelic text. For example, John O'Donovan, Annals of Ireland, by the Four Masters, is a facing page translation. Each left-hand page is a transcription which preserves capitalization as it appears in the original work. Each right-hand page is a 19th C translation of the corresponding left-hand page. The examples listed below (with 19th C translations) are taken from the year 1400 (vol. 4). A period after a letter indicates a punctum delens (which looks like a dot that appears above the preceding letter). A punctum delens is usually transliterated as an h following the letter in question. For example, {m.} is transliterated as mh. The notation e represents a "long e" character. In some cases, it is transliterated as e. In other cases, it is transliterated as ea. hoiberd mac Emainn mic hoiberd a burc ("Hubert, the son of Edmond, son of Hubert Burke", pp. 768-769) cathbarr {m.}ág aon{g.}usa ("Caffar Magennis", pp. 768-769) Con{c.}o{b.}ar mac Do{m.}naill mic néill {g.}air{b.}, mic aoda, mic do{m.}naill �icc uí {d.}o{m.}naill ("Conor, the son of Donnell, son of Niall Garv, son of Hugh, son of Donnell Oge O'Donnell", p. 770) Modern transliteration standards render literal bynames with non-capitalized particles and family names with capitalized particles. For example, mac Néill would indicate that this man's father was named Niall, while Mac Néill would indicate that Mac Néill was his family name. In a period document, mac Néill could indicate that either that his father was named Niall or that his family name was Mac Néill. [Cover Letter for the 06/2002 LoAR]
François la Flamme	2002.05	The question was raised during commentary regarding whether no is registerable as a written element in a Japanese name. In the case of languages that do not use a Roman alphabet (Japanese, Arabic, Hebrew, et cetera) registerable forms of the name are not based on pronunciation, but rather on transliteration standards for the language in question. In this instance, this issue is made more complicated because Japanese uses multiple character sets. Of these, kanji is pictographic while hiragana and katakana (collectively referred to as kana) are phonetic. Standards exist for transliterating kana using the Roman alphabet. The term used to refer to this representation of kanji or kana words using the Roman alphabet is romanji. As an example, in Japanese a man's name is properly written in kanji. However, there is also a kana equivalent for his name. Using transliteration standards, his name also has romanji equivalents. Adding yet another level of complexity for this issue is the existence of furigana. Furigana is made up of kana and is written alongside of kanji characters in a text to clarify the pronunciation of the kanji in question. Since kanji is written vertically and furigana is written alongside of the kanji characters, furigana serves somewhat the same purpose as a pronunciation notation would be if written above a sentence in an English document. In the case of no, we know that it is not written in the kanji form of a name, though it is included when the name is spoken. Solveig Throndardottir notes that The no will often show up in the furigana gloss to classic texts. It does not normally appear in the original text even when the original text contains extensive kana. [...] [T]he evidence to support no usage is much more dependent on scholarly or traditional glosses than the main formation of the name. Basically, we are on much more better footing if we leave no out of most formations. Given that no is included in furigana glosses in classical texts, though not in the original texts (and so it is not appropriate for those submitters desiring authenticity), no can be viewed as a modern transliteration standard. As such, it is registerable, so long as it is not used in a construction that could be viewed as presumptous. Solveig explains: [I]nserting -no- can at times be presumptuous indicating a specific rank or office not actually posessed. For example, Iguchi no Tarou might indicate a specific authority over Iguchi by lord Tarou. This sort of analysis is supported by the floating postion of -no- in various names in Heike Monogatari. Use of -no- in women's names tends to be less problematic. -no- appears in common use names where someone is described as the mother, wife, or daughter of some other person. This name is a woman's name of the type described above by Solveig. As it is not presumptuous, it is registerable. [Fujiwara no Aoi, 05/2002, A-East]
François la Flamme	2002.05	Listed on the LoI as Sofya Chiusdkaya Smolnyanina, the name was originally submitted as Sofia Chiudskaya Smolyanina and changed at kingdom to follow a documented form. Wickenden (third ed., p. 336 s.n. Smol'nianin) dates Petr Somolianin Prokosha to the 14th C, which demonstrates that a period variant spelling omits the 'n' after the 'l'. Therefore, we have removed this 'n', which was added at kingdom. We have also corrected the transposed letters (-sd- was mistakenly written for -ds-) in the first byname. The documentation supports the spelling Sofia Chiudskaia Smolianina, and Sofya Chiudskaya Smolyanina was put forth as a form of this name using a variant transliteration system. When registering Russian names, we require that a single translation system be used for the entire name. There are multiple valid transliteration systems for Russian names; we simply require that a single system be used consistently throughout the name. In this case, the documented name elements used a single consistent transliteration system. The documented elements were then modified with the intention of following a different transliteration system, which is a valid option. However, no explanation was provided to address why only some of the 'i's switch to 'y's and others do not. Without that support, the College has no way of knowing if the name was properly converted between transliteration systems. We have modified the name to follow the documented forms that were provided, since they consistently use a single transliteration system. [Sofia Chiudskaia Smolianina, 05/2002, A-Middle]
François la Flamme	2002.05	Submitted as Mikhail Kurganovic, the documentation cited Kurgan as a masculine given name from Wickenden (s.n. Kurgan) and -ovi{cv} from B. O. Unbegaun's Russian Surnames (p. 105). We have modified the byname to conform to the transliteration system used in the rest of the name. [Mikhail Kurganovich, 05/2002, A-An Tir]
François la Flamme	2002.04	This name has a number of problems that are all reasons for return. The surname Ryuusaki was submitted as a constructed surname intended to mean 'future dragon'. No documentation was presented and none was found that such a meaning is plausible in a Japanese surname. No documentation was presented that any Kanji with the transliteration saki is used to mean 'future'. The only Kanji character documented as being pronounced as saki was documented as meaning 'slope'. No documentation was presented that 'dragon slope' is a reasonable Japanese surname, either. Additionally, the Kanji used to construct Ryuusaki mix Chinese and Japanese pronunciations in the same word, which was not done in period and is cause for return. The nanori Raiden was documented from P. G. O'Neill's Japanese Names. However, no photocopies were provided from this source, and O'Neill is not on the "No Photocopy" list. As the College was unable to document this name element to period, it is being returned for lack of documentation. [Ryuusaki Raiden, 04/2002, R-Caid]
François la Flamme	2002.04	Submitted as 'Ijliyah al-Qurtabiyah, the byname was a submitted as a theorized locative byname referring to Cordoba. Juliana de Luna's article "Andalusian Names: Arabs in Spain" (http://www.s-gabriel.org/names/juliana/andalusia/) lists the feminine form of this locative byname al-Qurtubiyya, dating this name to the time period 700 to 1200. As this provides documentation for this construction, we have the byname to this form, adding the 'h' to match the transliteration system used for the given name. ['Ijliyah al-Qurtubiyyah, 04/2002, A-Caid]
François la Flamme	2002.03	Submitted as Nastas'ia Rosenzweig, this name mixes Russian and German, which was ruled registerable, though a weirdness, in the August 2001 LoAR (s.n. Tatiana Heinemann). RfS III.1 states that "Each name as a whole should be compatible with the culture of a single time and place". Therefore, we have modified the given name to a transliteration that is consistent with German orthography. [Nastasiia Rosenzweig, 03/2002, A-Atlantia]
François la Flamme	2002.03	This name was originally submitted as Aminah bint Mujelid Kitab. The byname, intended to mean 'the book-binder's daughter', was changed at kingdom on the advice of Sion Andreas to correct the grammar: The word for bookbinding is "tajliid al-kutub". Kutub is the plural of kitaab [...] The word tajliid is the nominal form of the Form II verb jallada. Therefore, Mujallid al-Kutub is a phrase constructed to have the meaning 'bookbinder'. Al Jamal found that a word meaning 'bookbinder' already exists: Elias' English-Arabic Dictionary Romanized (Edward E. Elias, 3rd ed.), p. 15, under "bind", gives megal'lid for "bookbinder". And in Jaschke's English-Arabic Conversational Dictionary (Richard Jaschke, Hippocrene Books, New York, 1987), p. 165, under "bookbinder" gives mjellid as the Syrian form and megal'lid as the Egyptian form of "bookbinder". I'd recommend modifying the name to Aminah bint al-Megal'lid (pronounced, roughly, ah-MEE-nah bint ahl-meh-JAHL-lid) for the desired meaning, using the shorter defined term rather than the longer construction for the patronym. Occupational bynames used in patronymic constructions are well documented. A byname with this meaning is registerable since bookbinding is a period occupation. As an Arabic word meaning 'bookbinder' has been found and it does not match the constructed phrase, this name is registerable as Aminah bint al-Megal'lid. We would have made this change. However, the submitter did not allow major changes, and changing the byname from Mujallid al-Kutub to al-Megal'lid is dramatic enough that it is a major change. Therefore, we must return this name. The submitter also requested authenticity for "1100 Middle East". Since no documentation was found dating megal'lid, we do not know if it is authentic for her desired time period. [Aminah bint Mujallid al-Kutub, 03/2002, R-Æthelmearc]
François la Flamme	2001.12	Submitted as Rurik Levushka Ul'yanov, the name mixed transliterations systems, which has been cause for return in the past: The submitted form mixes two different transliteration systems, which has the effect of changing the pronunciation of the names. The name in its entirety should adopt a single system of transliteration; either Katya Stesnaya (as already registered), Katia Stesnaia, or Katja Stesnaja. (Da'ud ibn Auda, LoAR September 1994, p. 21 [returned]) We have changed the name to use one transliteration system in order to register the name. There is one weirdness for using two Slavic given names in Russian. [Rurik Levushka Ul'ianov, 12/01, A-Atenveldt]
François la Flamme	2001.09	The submitted byname as-Sadafiyyah was documented as a laqab from an Arabic-English dictionary. This documentation gives no indication of whether it is a plausible laqab in period. al-Jamal found the masculine form of this laqab al-Sadafi in period and gives the feminine form as al-Sadafiyyah. Depending upon which transliteration conventions you are using, the terminal 'h' is retained or not. Therefore, registerable forms of this name are Khalilah al-Sadafiyyah and Khalila al-Sadafiyya. The submitter allows major changes and her "primary interest is in the final name element, Sadafi". As such, we have have registered the form of the name which uses the form of the final name element closest to her submitted form. [Khalila al-Sadafiyya, 09/01, A-Caid]
François la Flamme	2001.09	This name is being returned for a number of problems. The first problem is lack of documentation of the combinations of Kanji characters (rendered here in the Romaji transliteration) included in each element (clan name, clan branch, yobina, and nanori) of the name. Though we only register the Romaji transliteration of a Japanese name, the underlying Kanji characters give the meaning to each element of the name. Japanese is a pictographic language. As such, elements only combine in groups that make conceptual sense to the medieval Japanese mind. A second problem with this submission is that it mixes onyomi (Chinese) and kunyomi (Japanese) readings of the Kanji characters in a single name element. The elements Kentsuki and Kaito have this problem. The third problem is that some of the underlying Kanji used in this name are only documented as deuterothemes (used in the last half of a name element), but they are included in this submission as prothemes (used in the first half of a name element). Documentation of a Kanji character as a deuterotheme does not serve as documentation for the same Kanji as a protheme. The elements Ujitora and Tamashi both use prothemes and deuterothemes in undocumented locations. The submitter constructed the clan name Ujitora, the clan branch Kentsuki, the yobina (common name) Kaito, and the nanori (official given name) Tamashi by choosing elements from Solveig Throndardottír's Name Construction in Medieval Japan (NCMJ) and combining them. Solveig details some issues with this submission (all references from NCMJ): [Kentsuki] The problem with KEN on page 310 is that it is an ONYOMI reading used as a prototheme in [a] yobina. All of the examples except for Takebe use the ONYOMI reading and are yobina. Takebe is one of the special occupational -be names. Consequently, Kentsuki just does not work for a surname, a clan name, a nanori or as a yobina. It also fails as a place name. Tsuki does appear as a deuterotheme in precisely one attested surname on page 240. It is taking a kunyomi reading as indicated by the lower case reading. I am pretty sure that I told people in the text to avoid mixing onyomi and kunyomi readings in single names. Regardless, there is precisely one name in the entire pamphlet which uses the tsuki theme. [Ujitora] Uji on page 185 is a kunyomi reading and shows up pretty much exclusively as an element in a yobina. The only other example is the female name Ujiko which can not be used to justify other forms except possibly forming a masculine yobina which is incompatible with a nanori form. He is slotting [Ujitora] in in a place which suggests that he is trying to make a yobina. [...] Tora would pretty much have to slot as a prototheme in a yobina. The one possibility is that he is trying to construct a yobina which would be slotted as the last part of his name and not the second and would not be prefixed by the no. Tora does appear as a deuterotheme for nanori as shown on page 169. The problem with Ujitora as a nanori is that it does not make a whole lot of sense from the standpoint of meaning. If you look at the various attested modifiers for -tora on page 169, you will notice that the protothemes tend to give attributes rather than being nominal. Uji on page 185 is clearly nominal and with the sole exception of the female name already mentioned is strictly a deuterotheme. Thus, a strict deuterotheme is being misapplied as a prototheme. So what we have here is a case where someone has tried to combine two deuterothemes to construct a name of unknown type. If he had given a name type, I might be able to be more helpful. However, this time he did succeed in combining two kunyomi readings. [Kaito] KAI on page 251 shows up in a single name which happens to be a Homyo (Buddhist religious name). to [on p. 279 - the LoI typoed the page number as 219] appears only in the surname Aoto. TO [also on p. 279] appears only in ancient feminine names ending in -me. [Tamashi] [Solveig did not comment on TA] ma- appears only as a prototheme for the surname Makabe. SHI (notice the ONYOMI reading) only appears as a middle theme in very early feminine names ending in -me. Thus, its position in this name can not be supported. Additionally, though no is included in the spoken name, it is not included in the written name. As there are four editions of NCMJ, simply citing a page number is not useful. The header needs to be included in the documentation as well. We would like to thank the submitter for including with his documentation, the specific Kanji characters that were combined in the elements of this name. We do not register the Kanji characters; instead we register the Romaji transliteration. But as multiple Kanji characters have the same pronunciation, it made researching the name easier to know which Kanji were used to create the submitted name. [Kentsuki no Ujitora Kaito Tamashi, 09/01, R-Caid]
François la Flamme	2001.08	The byname the Butcher is registerable in this instance via the lingua Anglica allowance. The Greek form of this name (transliterated) would be Xenos Mageiros. [Xenos the Butcher, 08/01, A-Ansteorra]
Elsbeth Anne Roth	2000.06	The standard transliteration for a byname of an Arab man from Seville would be al-Ishbili; a transliteration using x seems odd. Moreover, al-Ixbily has an i and a y for the same sound. This kind of mixing transliteration systems within a single name has been grounds for a return in the past. [Tahira bint Ibrahim al-Ixbily, 06/00, R-East]
Elsbeth Anne Roth	1999.11	Submitted as Ghazelleh al-Badriyyah, valid transliterations of the name lack the double "l" and either have all "e"s or all "a"s. [Ghazalah al-Badriyyah, 11/99, A-East]
Elsbeth Anne Roth	1999.08	No evidence was presented that Jasmina was a reasonable transliteration of Yasmin. [Jasmina Salazar, 08/99, R-East]
Jaelle of Armida	1997.04	Submitted as Aryel Ramsey of Skye, the standard transliteration of Ariel is with an "i", not a "y". (Jaelle of Armida, LoAR April 1997, p. 12)
Da'ud ibn Auda (2nd tenure, 2nd year)	1995.12	No Room for Runes. The submission of Thyra Thorkilsdottir (Middle) raised another interesting question. The submitter justified some unusual spellings on the grounds that she was transliterating Scandinavian runes. On the face of it this should be acceptable enough, since we allow a variety of transliterations of Arabic, Hebrew, and Cyrillic writing, among others. On further investigation, however, this proved to be a rather different situation. It's true that transliterations of runic inscriptions are often quite different from the usual forms of the same words and names when they are written in Roman letters. The most common Scandinavian runic alphabets had fewer letters than the Roman alphabet, and as a result several runes can represent more than one letter or combination of letters. For example, a single rune was used for o and u. But when a word was written in the Roman alphabet, the distinction between the two was maintained; we do not find simple transliterations from the runic futhark to the Roman alphabet. Thus, for example, the name Gormr, when written in Roman letters, is written Gormr, even though the runic version is generally transliterated kurmR. We record a Roman alphabet version of registered names; when necessary, we transliterate. In the case of Arabic names, say, transliteration is necessary, though we may use either ours or some mediæval version. But in the case of Old Norse names, transliteration is unnecessary, because there was already a standard way to write these names in the Roman alphabet. Therefore we will follow period usage and write Old Norse names as they would have been written in the Roman alphabet. Of course, just as Demetrios, Vasilii, and Haroun are welcome to write their names in Greek, Cyrillic, and Arabic script, respectively, Steinólfr and Ingrí r may surely write theirs in runes; but for documentary purposes we will use only the Roman alphabet forms. (CL 12/95)
Da'ud ibn Auda (2nd tenure, 2nd year)	1994.09	The submitted form mixes two different transliteration systems, which has the effect of changing the pronunciation of the names. The name in its entirety should adopt a single system of transliteration; either Katya Stesnaya (as already registered), Katia Stesnaia, or Katja Stesnaja. (Da'ud ibn Auda, LoAR September 1994, p. 21)
Bruce Draconarius of Mistholme	1992.08	[Ingiriðr] As we've learned to our sorrow in trying to read the numerous formats of the disks sent to us, non-Roman characters are hard to handle, for us and for the Armorial. We register names in the Roman alphabet, not in Cyrillic, kanji, Greek, or runes --- including edhs and thorns. She may certainly spell it with an edh, once the name is registered; but for the record, we have substituted a standard transliteration of the edh [d]. (Ingiridr Hikri Fridriksdottir, August, 1992, pg. 16)
Da'ud ibn Auda (2nd year, 1st tenure)	1991.12.11	"There was a little commentary regarding a request for a 'standard transliteration' for the benefit of those without all of the 'fancy characters' in their word processors. It was noted that 'the only ones who really need to have printers that can do all the strange stuff are Laurel and Free Trumpet Press West'. {Laurel wants to know if that commenter plans on buying the Laurel office a printer that will do all those fancy characters, then since his printer will not do them all?} Laurel does not feel any overwhelming need to dictate a 'standard' transliteration for each non-standard character from Norse or any other language. We do not require a standardized transliteration system for Chinese, Japanese, Mongol, Persian, or Arabic; I fail to see why we should mandate one for Norse. As a general rule I will use the 'fancy characters' if my word processor will do them, but for some, particularly thorns and edhs, will generally use 'th' or 'd', depending on the specific name." (CL 11/12/91 p.2).
Da'ud ibn Auda (2nd year, 1st tenure)	1991.10	"The transliteration as submitted of the patronymic was not reasonable, combining as it did two different transliteration systems in a single name element, which serves only to distort the pronunciation." [It was modified to a consistent transliteration] (LoAR 10/91 p.1).
Da'ud ibn Auda (1st year of 1st tenure)	1990.10	"Lord Yale's discussion of the Wade-Giles and Pinyin transliteration systems for Chinese convinced us that the name would be better if spelled in only one or the other rather than a hybrid which used parts of each. Accordingly, we have used the Pinyin transliteration system as that was closest to the form submitted." (LoAR 10/90 p.9).