Submitted as Barbary Rose of the Endless Hills, the second byname was documented as a registered branch name. However, the branch name is registered as Endless Hills, Barony of without the article the. While the submitter will not accept major changes, she specifically allows dropping the article if this is necessary for registration. We have changed the name to Barbary Rose of_Endless Hills in order to register it.
The submitter requested an authentic Elizabethan name. The name Barbary Rose is a lovely late 16th C English name, but it conflicts with the registered Barbary atte Rose. Therefore, we are unable to register the fully authentic form to her.
Submitted as Gunnarr of the Endless Hills, the byname was documented as a registered branch name. However, the branch name is registered as Endless Hills, Barony of without the article the. While the submitter will not accept major changes, he specifically allows dropping the article if this is necessary for registration. We have changed the name to Gunnarr of_Endless Hills in order to register it.
Submitted as Black Antelope, this title lacked the required designator. The kingdom submitted a timely correction noting that the designator should be Herald. Given this, we have registered this title as Black Antelope Herald.
Submitted as Black Falcon, this title lacked the required designator. The kingdom submitted a timely correction noting that the designator should be Herald. Given this, we have registered this title as Black Falcon Herald.
Submitted as Black Talbot, this title lacked the required designator. The kingdom submitted a timely correction noting that the designator should be Herald. Given this, we have registered this title as Black Talbot Herald.
Submitted as Demi-Lion, this title lacked the required designator. The kingdom submitted a timely correction noting that the designator should be Herald. Given this, we have registered this title as Demi-Lion Herald.
Nice 12th C Irish name.
The submitter requested a name authentic to 14th-16th C, but this request was not mentioned on the LoI. Fortunately, the issue is implicitly addressed in the commentary. Albion notes:
...the <Coryn> cited in the Petty Custom book is a Dutch merchant. The typical Dutch spelling of the name is <Corijn> this can be found in my "15th Century Dutch Names" (<http://www.ellipsis.cx/~liana/names/dutch/dutch15.html>). My and Kymma's "Names from Antwerp, 1443-1561" (<http://www.ellipsis.cx/~liana/names/dutch/plaiser.html>) has <van den Bossche> 'of the forest' dated to 1447, 1460, 1544, 1547, and 1550. (I don't actually have any examples of any bynames containing <Woud> 'wood' in any of my articles.)
Add to this the citations in R&W s.n. Wood and <Coryn of the Wod> [sic] becames a plausible English form of a Dutch <Corijn van den Bossche>.
Had this name not been substantially authentic already, and had the information above not been present in the commentary, we would have been forced to pend this for further research.
The submitter requested an authentic name for 14th C Hamburg. However, we have no example of the byname Weissbaum that isn't modern. While the submitter provided an argument that the name followed German byname patterns appropriate for the 14th C, without an example of the name in period, we cannot recommend it as an authentic name. We note that weissbaum is a possible Middle High German (mittelhochdeutsch) word, but the language or dialect of German spoken in Hamburg in the 14th C is Middle Low German (mittelniederdeutsch). For that region, we would expect the byname to have a form starting with Wit or Witte; Brechenmacher, Etymologisches Woerterbuch der deutschen Familiennamen, shows several examples of Low German bynames starting with Wit and Witte that are cognates of High German starting with Weiss. It is unclear exactly what the appropriate form of Weissbaum would be in Low German, but it is probably similar to the modern Dutch surname Witboom.
Nice badge.
There was question whether the name Odinsdottir was registerable. The answer is that it depends on the rest of the name. Odinsdottir was declared unregisterable as an Old Norse name, as no documentation has been found to support the use of the name Odin by ordinary humans during the time when Old Norse is appropriate:
There was some discussion whether the use of Odin in this name was presumptuous. Indeed, the byname Odinsson was ruled unregisterable long ago:
Of course he can't be "Odinsson" without proof of his parentage. (KFW, 17 Aug 78 [21], p. 9)
[N. Odinsson.] Let him submit a history form documenting whose son he is, or change his name. (HB, 5 Aug 72 [56], p. 1)
In this case, the submitted documentation shows that Odin is found as "a man's name found once in Nicolaa de Bracton's article, 'A Statistical Survey of Given Names in Essex Co., England'" (http://members.tripod.com/nicolaa5/articles/names.html). Sommelier also found that Reaney & Wilson (pp. 327-328 s.n. Oden, Othen) "date Oudon 1066, Odin Goldeberd 1327, and Thomas Oden 1332 (among others)." These examples are sufficient to support the use of Odin as a rare name used by humans in English. As such, it is registerable in the patronymic form FitzOdin so long as there are no additional references to the mythological Odin or a child of Odin.
Note, though, that no documentation was found of Odin used by humans in period in Old Norse. Lacking such evidence, it is continues to be unregisterable in an Old Norse patronymic byname. [Alan Fitz Odin, February 2003]
However, the "Diplomatarium Norvegicum" (http://www.dokpro.uio.no/dipl_norv/diplom_field_eng.html) has an Odin Redulf sson in 1460 (document 240) and Nykolas Odin sson in 1468 (document 355). The name Katrin is found in 1468 (document 843) in the same source. Given this, Odin is a name used by normal humans in late period Norwegian, hence this name is registerable as a 15th C Norwegian name.
Submitted as Marie-Helene von Bremen, the submitter requested an authentic name. The name Helene is documented as a French name, but the rest of the name is German. The submitted documentation notes that Helena can be dated to 1364 and the 16th century in Germany. In addition, no evidence has been found for hyphenated given names in German in period. We have changed the name to Marie_Helena von Bremen in order to register it and to fulfill the submitter's request for an authentic name. As registered, this is a reasonable 16th C German name.
Nice late 16th C English name!
Registered May 2005 with the blazon, Sable, two lightning bolts argent and a base wavy barry wavy Or and vert, this has been reblazoned to specify the orientation of the lightning bolts.
The submitter has permission to conflict with the device for Adalasia Serena, Per bend sable and gules, a bend bevilled argent.
Nice 15th C Italian name!
Submitted as Nyfain of Brigantia, the submitter requested a name authentic for 6th century Britain. The name Nyfain is a standard modern form of a name found in the 6th C. The bearer of this name is found in genealogies written between the 10th through the 14th C. The name is not a saint's name. Early names found in later genealogies that are not saint's names are not registerable in standard modern (or standard later medieval) forms unless documentation is provided that the name was in use when such a spelling would be appropriate. Barring documentation that this name was in use in later period, the form Nyfain is not registerable. The article used to document the name, Heather Rose Jones, "Names of Women of the Brythonic North in the 5-7th Centuries" (http://heatherrosejones.com/names/welsh/brythonicnorth/5th-7thbrythonicwomen.html), notes that a Latinized Nemania would be appropriate to this period. With a Latinized given name, we would expect a Latinized form of the byname; Harpy suggests that Brigans is an appropriate Latin adjectival form. We have changed the name to Nemania Brigans in order to register it and to partially address the submitter's request for authenticity.
There was some discussion on whether the crown was a co-primary charge or a secondary charge. Given the central location of the torch, and the placement of the crown clearly in chief, the crown is a secondary charge.
Owen commented "I would argue, though I expect others would disagree, furthermore that coronets are a special case. It is a perfectly correct, period depiction of a crowned charge for the crown to hover above the charge. See da Bara: crowned charges are routinely emblazoned so. Under this interpretation, Nyfain's coronet is not merely not co-primary, it is insignificant." While this may be a period usage, it is not an interpretation used in the SCA. This is purely pragmatic - we grant a CD for secondary charges. While we protect mundane armory in both crowned and uncrowned forms, we do not wish to do so for SCA armory at this time. This inconsistency is an artifact of the way our rules are applied.
The submitter is a countess and thus entitled to display a coronet.
Please advise the submitter to draw the wolf larger.
Registered in November 1991 with the blazon Vert, in pale a stag's head cabossed Or and a stone well argent, the type of well was not specified. Please see the Cover Letter for a discussion on blazoning wells.
Nice 16th C Scots name!
This device is clear of the important non-SCA arms for the Counts of Toulouse, Gules, a cross of Toulouse Or. There is a CD for the number of crosses, and another for the difference between a cross moline disjointed and a cross of Toulouse.
Submitted under the name Rosmerryn Carew de Courcelles.
Registered in February 1999 as (Fieldless) A dragon's talon erect Or maintaining a roundel, overall in saltire two rapiers inverted azure, the default posture for dragon's feet is with claws to chief (as with lion's jambs, and as opposed to bird's legs with claws to base). Also, the talon is only a claw, while this shows the full foot and some of the leg. We have corrected the blazon, while keeping the term "talon" as a reference to the Order name
Submitted as Tamar Oqropiri of Black Sea, no documentation was submitted and none found by the commenters to suggest that Georgian locative bynames were formed from names of bodies of water. Therefore, we have dropped the locative and registered the name as Tamar Oqropiri_.
Effric Neyn Ken3ocht Mcherrald makes a comment about the spelling/pronunciation of this locative that might be of interest to the submitter:
Note that the <z> in <Velzian> is an editorial convention used to represent the letter yogh <3>. In the original manuscript, the name would have appeared as <Vel3ian> (Da'uded: <Vel{gh}ian>; non-Da'ud ASCII: <Vel3ian>). That this is the case is confirmed by other spellings given by Black that illustrate that the pronunciation involved a "y" (or fricative "gh") sound, not a "z" sound: <Awelgeing>, <Wailyom>, and <Vilyean>.
Registered in January 1973 with the blazon Per pale azure and argent, in canton a sun in his splendour and in the fly a Serpent (bass cornetto) azure, the tincture of the sun was omitted. We have corrected the omission and reblazoned this in accordance with standard SCA heraldic practice.
This is currently listed in the O&A as a flag, and continues to be so listed.
Submitted as Aubrée Duquesne de Bellemare, the only documentation for the accent in Aubrée was a citation from a genealogy website. An examination of the website revealed that it is unlikely that the names were preserved in their original forms. Without a dated citation for the spelling Aubrée, it is not registerable. The submitter has provided sufficient documentation to support Aubree; we have changed the given name to this form in order to register it.
The submitter requested an authentic 13th C French name. However, we have found no form of Duquesne before the mid 15th C and none of Bellemare before the 16th. Both bynames are found in Cateline de la Mor, "Sixteenth Century Norman Names" (http://www.s-gabriel.org/names/cateline/norman16.html). If Aubree were documented to the 16th C, this would be an authentic 16th C French name, but we doubt it is authentic for the 13th C.
Her old name, Cyneburg Thorisdohter, is released.
The use of a bird displayed, other than an eagle, is a step from period practice.
The use of pawprints is a step from period practice.
Registered in October 1976 with the blazon Vert, two winged serpents erect counter-respectant, their tails nowed in a Wake knot, argent, a winged serpent has feathered wings. These monsters have bat-wings, which is the standard for pithons.
Linnet is the submitter's legal given name.
Nice device.
In registering Vanya Popovitch's device in March 1984, Laurel ruled that the lowermost cross bar on a Russian Orthodox cross should be bendwise. In registering Monenka Romanyak's device in July 1985, Laurel ruled that it should be bendwise sinister. At this point we are declaring that the orientation of the lowermost cross bar is an unblazoned detail worth no difference. In other words, it doesn't matter if it is bendwise or bendwise sinister.
The submission history of this device is difficult to determine. It is currently listed in the Armorial as registered January 1973 with the blazon Vert, a bend sinister argent between a hawk close and a lightning bolt, both Or; however this does not appear in the January 1973 LoAR. There is a letter sent by Wilhelm von Schlüssel, Laurel, in September 1980 indicating this blazon and the January 1973 registration. This appears to be the same armory that appeared in the July 1972 LoAR with the blazon Vert, bend sinister between a hawk close and a lightening-flash bendwise sinister, singly fracted, both Or. The charge is a lightning flash, not a lightning bolt, though the emblazon in his file does not show the fracting mention in the July 1972 LoAR. This device has been reblazoned to correct the charge and to specify its orientation. A lightning flash, like a lightning bolt, does not have a default orientation.
Her old name, Meliora Gwinear, is released.
Registered December 1995 with the blazon, Azure, on a pale argent between two lightning bolts Or a dexter gauntlet clenched sable, this has been reblazoned to specify the orientation of the lightning bolts. A dexter gauntlet is the default gauntlet.
Registered April 1998 with the blazon, Sable, a lightning bolt Or and in chief a cloud argent, this has been reblazoned to specify the orientation of the lightning bolt.
This does not appear to be period heraldry: Mullets of four points are vanishingly rare in period armory, secondary charge groups of with two different kinds of animate charges are very uncommon, and per bend an A between a B and a C in bend sinister is a very uncommon arrangement. However, this is registerable under our rules.
Registered July 1993 with the blazon, Vert, an owl affronty perched atop a branch fesswise argent between three drop spindles inverted sable, threaded argent, the branch is significantly longer than the owl is wide. We have reblazoned this device to make it clear that the owl and the branch are co-primary charges.
Registered in July 1983 with the blazon Or, a winged serpent, wings displayed, a base embattled gules, a winged serpent has feathered wings. This monster has bat-wings, which is the standard for a pithon.
The submitter requested that the augmentation be blazoned as a cross of Caid. Please see the Cover Letter discussion for the reasons why we decline to do so at this time.
Registered in July 1999 as (Fieldless) A dragon's jamb inverted couped Or sustaining an orb azure, this does not match the period definition of an orb as a charge; it is simply a roundel. An orb has banding and a cross on top, as shown in Livro da nobreza and in Parker's A Glossary of Terms Used in Heraldry.
The submitter's previous device, Argent crusilly formy, a bordure sable, is retained as a badge.
Submitted as Conchobhar Mac Cionaioith, the documentation shows the correct spelling of the patronymic is Mac Cionaoith. We have changed the name to match the documentation.
This submitter requested an authentic 14th C English name; this is already an authentic 14th C English name.
This submitter requested an authentic 14th C English name; this is already a authentic 14th C English name.
Submitted as Eveleen Kavanaugh, both parts of the name were documented as modern. Without documentation showing that these names are period or at least consistent with period spelling, they are not registerable. Rowel provides documentation for Evelin Kavanagh as a late 16th/early 17th C name:
I've found one Anglicized Irish form of this given name in 1603-1604. Here's the info:
Source: a list of names from Patent Rolls of James I (1603-1604) listed in Ewen, C. L'Estrange, A History of Surnames of the British Isles (Originally pubished: London, 1931. Reprinted for Clearfield Company, Inc. by Genealogical Publishing Co., Inc. Baltimore, Maryland, 1993, 1995). pp. 210-211.
In a footnote on p. 210, Ewen notes that his source was: "Cal. of Irish Patent Rolls, vol. ii, p. 17 et seq."
In this list, appears the name:
Evelin ne Morishe, spinster
I've found <Kavanagh> as an Anglicized Irish form dated to 1570. Here's the info:
O'Donovan (Annals of the Four Masters, volume 5, pp. 1648-1649) includes a transcription of an indenture dated to 15 March 1570. In this transcription is listed:
Bryane Mc Cahir Mc Art Kavanagh of Ballyan, in the county of Wexford, gent. cheife of his name and cept called Slaght Dirmod Lawdarage
We have changed the name to Evelin Kavanagh in order to register it.
Submitted as Faoileann inghean Dhaibhead, no evidence was presented and none found to suggest that the spelling Daibhead is found in period. The name was documented from Ó Corrain and Maguire, Irish Names as a secondary (post colon) header form. Post colon header forms, are, according to the authors, modern forms, not Early Modern Irish forms. For more on this, see the next paragraph. An examination of the various annals at the CELT site (http://www.ucc.ie/celt) suggests that the most common Early Modern Irish form for this patronym is Dauidh. This is also the appropriate form for the patronym in a feminine name, as names beginning with the letter d do not lenite when the last letter of the previous word is n. However, as this significantly changes the appearance of the name, and the submitter will not accept major changes, we cannot change the name to this form. Luckily, the standardized Early Modern Irish form of this patronym, Daibhídh, is much closer in appearance to the submitted form. We have changed the name to Faoileann inghean Daibhídh in order to register it and to correct the grammar.
The documentation for the given name was not adequately presented on the LoI. The statement "Faoileann is a feminine Irish given name found in OCM (pg. 93, header)" was the only information submitted for the given name. Giving a book title and page number is not adequate; you must also summarize what the source says about the name. This is particularly important with Ó Corrain and Maguire, Irish Names, as this work includes modern names, legendary names, and a variety of other unregisterable items. In addition, care must be taken in using this work. While it is a common belief within the SCA that most secondary header forms in this work are Early Modern Irish forms, this is not the case. The authors say in their introduction: "Generally, in the case of each entry, the name is first given in its early Irish form. This is followed by a colon, after which the modern Irish form is given." We encourage submitters who wish Early Modern Irish names and who use this work for documentation to provide additional documentation for their names (for instance, find forms in the various Irish annals at http://www.ucc.ie/celt). Had the commenters not provided the necessary information and additional documentation for this name, we would have been forced to return it.
Registered in May 1970 with the blazon Or, semy of strawberry plants slipped, leaved and fructed proper, a unicorn couchant reguardant vert, the primary charge is not a unicorn as it lacks a beard, cloven hooves, or a lion's tail. While this emblazon is grandfathered to the submitter, the blazon is not. The College has a responsibility to amend incorrect blazons that have been registered in the past. We have thus reblazoned this as a unicornate horse.
The submitter requested that the augmentation be blazoned as a cross of Caid. Please see the Cover Letter discussion for the reasons why we decline to do so at this time.
A unicornate horse is grandfathered to the submitter.
Guendolen is an SCA-compatible Welsh name.
The submitter requested an authentic 13th C Welsh name. However, we have no evidence that the name Guendolen was used in the 13th C (or, in fact, anywhere except Geoffrey of Monmouth's History of the Kings of Britain). If the submitter is interested in a similar sounding name, we suggest Gwen uxor Alexander. Tangwystyl verch Morgant Glasvyrn, "A Simple Guide to 13th C Welsh Names" (http://www.s-gabriel.org/names/tangwystyl/welsh13.html) dates Gwen to the 13th C.
Submitted as Isibéal inghean Dhaibhead, no evidence was presented and none found to suggest that the spelling Daibhead is found in period. The name was documented from Ó Corrain and Maguire, Irish Names as a secondary (post colon) header form. Post colon header forms, are, according to the authors, modern forms, not Early Modern Irish forms. An examination of the various annals at the CELT site (http://www.ucc.ie/celt) suggests that the most common Early Modern Irish form for this patronym is Dauidh. This is also the appropriate form for the patronym in a feminine name, as names beginning with the letter d do not lenite when the last letter of the previous word is n. The standardized Early Modern Irish form of this patronym, Daibhidh, is much closer in appearance to the submitted form. We have changed the name to Isibéal inghean Daibhídh in order to register it and to correct the grammar.
A search of the LoARs shows that this device was originally registered to John of Griffin in February 1970 with the blazon Vert, a griffin rampant countournee Or. The name became John ap Griffin at some point (and has consistently been used in that form since at least March 1978 when his badge was registered). In September 1980 a letter was sent by Wilhelm von Schlüssel, Laurel, indicating that the May 1970 blazon was Vert, a griffin counter-segreant Or. At some point the blazon was changed and the Armorial currently lists a single blazon, Vert, a griffin segreant to sinister Or. We see no reason not to accede to the submitter's wishes to use contourny, rather than to sinister in the blazon.
The submitter requested that the augmentation be blazoned as a cross of Caid. Please see the Cover Letter discussion for the reasons why we decline to do so at this time.
A search of the LoARs shows that this device was originally registered in March 1978 with the blazon Sable, a griffin countersegreant surmounting a twin-towered castle Or. In September 1980 a letter was sent by Wilhelm von Schlüssel, Laurel, confirming the blazon. At some point the blazon was changed and the Armorial currently lists a single blazon, Sable, a griffin segreant to sinister surmounting a twin-towered castle Or. The term surmounting implies that the griffin is overall; it isn't. We have reblazoned the badge to more accurately reflect the emblazon. We have blazoned the griffin as contourny, in accordance with the submitter's preferred blazon.
Her old name, Katrín Brjánsdóttir, is released.
The submitter requested that the augmentation be blazoned as a cross of Caid. Please see the Cover Letter discussion for the reasons why we decline to do so at this time.
Registered August 1999 with the blazon, Sable, a lightning bolt Or within the tines of hart's attires argent, this has been reblazoned to specify the orientation of the lightning bolt.
Rouge Anne du Maurier is the submitter's professional (also known as) name. This is a legal name registered in state court for business purposes. As such, it meets our legal name requirement. The addition of the metronymic Marie creates sufficient difference to make this name registerable.
Submitted as Siobhan O'Cuolahan of Iar Connacht, as submitted, the name has several problems. First, the locative byname of Iar Connacht mixes English and Gaelic in the same name phrase in violation of RfS III.1.a, Linguistic Consistency. Although RfS III.1.a says "In the case of place names and other name elements frequently used in English in their original form, an English article or preposition may be used," Iar Connacht is not a form frequently (if ever) used in English. The adjectival byname Connachtach appears in Mari Elspeth nic Bryan, "An Index to Names in Irish Annals" dated to the 14th C. The Dictionary of the Irish Language, Royal Irish Academy, s.v. Íarmuimnech, defines that word as "pertaining to Íar-Muma" -- that is to say West Munster; Mari's "Index" lists Muimhneach as meaning "from Munster". Given this, Íarconnachtach would be the expected form for a byname meaning "from West Connacht". Second, the byname O'Cuolahan is a modern Anglicization of the Irish surname Ó Cúlacháin. While we are unable to find this surname in the Irish Annals, Woulfe, Irish Names and Surnames, s.n. Ó Cúlacháin, lists O Coullaghan and O Couloghan as late period Anglicized forms of this name. As the submitter indicated that, if the name had to be changed, she cared most about Irish language/culture, we have changed the name to the fully Irish Siobhan Iarconnachtach inghean úi Chúlacháin. We note that the name Siobhan Iarconnachtach O'Coullaghan is also registerable, although its combination of Gaelic and Anglicized Gaelic is a step from period practice.
Registered October 1995 with the blazon, Vert, a cloud with a lightning bolt issuant to base argent, a bordure rayonny Or, this has been reblazoned to indicate that the cloud and the lightning bolt are co-primary charges.
Submitted as William Rumbellow, Rumbellow was documented as a header spelling from Reaney and Wilson, A Dictionary of English Surnames. Neither Reaney and Wilson or the Oxford English Dictionary show a spelling of this word with the double-l before 1650. We have changed the name to William Rumbelow to match the documentation.
Registered in February 1984 with the blazon Per fess rayonny azure and argent, an open book argent and a well gules, the type of well was not specified. Please see the Cover Letter for a discussion on blazoning wells.
This name mixes Spanish and Arabic; this is one step from period practice.
The submitter has permission to conflict with the badge for Alisoun MacCoul of Elphane, Argent, an ass passant to sinister azure.
Submitted as Barabbas_Maccabeus, the submitter did not specify a language/culture, nor did he show that the name was consistent with the naming practices of any particular language and culture. Fortunately for him, Eastern Crown notes that both elements of this name are found in Hungarian naming practice:
I don't know about Jewish usage, but Barabás and variants were quite common in period Hungary. Kázmér devotes a full page to the unmarked patronymic, and also has period entries for the marked patronymics Barabásfi and Barabási. The name is often confused/conflated with Barnabás -- Fehértói (p. 91-92) has a combined entry for Barnabas, Barabas/Barrabas, and Barlabas, with numbered subheadings for each major form. It appears that the spelling Barrabas far outnumbers Barabas in her data.
Fehértói actually has more than one person named Machabeus (p. 504)...Bracketed dates are conjectural.
Machabeus [1141-1161]: Libertos, quos emit Martinus comes ab Budrugiensibus ... Coram quibus empti sunt: Johannes prepositus, Sydemer, Mosy, Ilis, Elias, Machabeus filius Laberti; 1233: monasterii Beati Martini ... Machabeus, Mathias, Beniaminus ... sacerdotes; [1270-1272]>1302: Machabeus [hospes de] Nymty [de Zothmar]. Cf. Macobius.
The 'compare with' entry is (p. 506):
Macobius 1219/1550: pristaldo Macobio de villa Elep. Cf. Machabeus.
This name does not appear to have survived long enough or been common enough to become a surname, as there's nothing like it in Kázmér. Thus, I can't really recommend it as an unmarked patronymic, but something like Barrabas filius Machabei is plausible as a 12th-13th c. Hungarian man's name (recorded in Latin, of course).
We have changed the name to Barabás filius Machabei in order to register it.
Nice device.
Submitted under the name Logan the Bowyer.
The submitter requested an authentic German name. This name mixes Italian and German; this is one step from period practice. As we know of no German equivalent to Caramanna, we are unable to make the name authentic as requested.
Blazoned on the LoI as a talbot, the dog lacks the long floppy ears of a talbot. As it is identifiable as some type of dog, we are registering it simply as a dog.
Submitted as Idonea De Clare, prepositions in English names are not capitalized when separated from the byname by a space. We have changed the name to Idonea de Clare to match period forms.
Blazoned on the LoI as a panther, this is not an English (or heraldic) panther: the snout and tusk prevent that, as does the lack of spots. And it's not a Continental panther: the lack of eagle's forelegs and/or horns prevents that. And the tusk means that this is not a natural panther. The most accurate blazon we could derive was a tyger incensed.
The submitter is a duke and thus entitled to display a ducal coronet.
This badge is clear of the badge for Christgaen von Köln, Argent crusilly formy, a bordure sable, with a CD for removing the bordure and another for the difference between a cross formy and a cross Maltese. The badge is also clear of the device for Dorothea of Caer-Myrddin, Argent, a cross patty sable, with a CD for the type of cross and another for the number of crosses.
We wish to remind the College that endorses (and cotises) follow the line of the ordinary. Thus, a pale engrailed endorsed has both the pale and the endorses engrailed, while a pale endorsed engrailed has only the endorses engrailed.
Her old name, Carolin von Adlersberg, is released.
Please advise the submitter on the correct way to draw proper flames. Normally this badge would have been returned for depicting the flames as Or fimbriated gules, which has been disallowed since the April 1995 Cover Letter. However, her previous submission, with a single slow match, had the flames drawn identically to here, and no mention was made of the fact. The submitter had a similar badge returned in March 2006 for conflict. The submitter was told to draw the sparks correctly (one and two, instead of two and one), which has been done; but if the flame was a problem serious enough for return, it should have been brought up then. As it was not, we will register this emblazon.
Please advise the submitter that some internal detailing on the slow matches will aid in their identification.
Submitted as Prudence the Underwit, there was some question whether the byname Underwit was a meaningful construction. While the submitter sites several examples of names starting with under, no evidence was given that this element was used with a second element that does not indicate relative heights. However, Ekwall, The Oxford Dictionary of English Place-Names, s.n. Undermillbeck, gives the etymology as "under, i.e. south of Millbeck" which is a millstream. We will give the submitter the benefit of the doubt that this is an alternative valid meaning for the element under when used with generic topographic features, such as wit "river bend". On the other hand, the article the is not appropriate with a locative byname. We have changed the name to Prudence_Underwit in order to register it.
There was much discussion on whether the chief should be blazoned as a chief wavy barry wavy azure and argent or as on a chief wavy azure two barrulets wavy argent. As Black Stag noted:
Well, the situation on a chief isn't exactly the same as the situation for charges/multiply divided tinctures on the field. After all, 8 'stripes' for barry wavy on the field would be unexceptionable. While 8 'stripes' on a chief would probably get a return for teeny thin stripes (as that'd be a lot like 24 stripes on the field.)
Six stripes on a chief would probably be too many, making the stripes too thin. Using three stripes this would clearly be a charged chief. Four or five stripes is about the best that can be done to make a chief clearly barry. The chief in this submission has five stripes; while there is no heraldic difference between this and on a chief wavy azure two barrulets wavy argent, there is no reason not to blazon it as a chief wavy barry wavy azure and argent.
This was registered in August 1979 with the blazon Sable, a crenelated castle tower and wall issuing from the sinister, in chief a cloud, all Or. That blazon would essentially have a demi-castle issuant from sinister, with the field visible in base. This has been reblazoned so that the edifice issues from the proper portion of the shield.
Aislinn is an SCA-compatible Gaelic name.
Her old name, Aislinn Chas, is released.
Submitted as Ardenia Rufa, the submitter requested that the byname be changed to the lingua anglica translation the Red. Per her request, we have registered the name as Ardenia the Red.
Blazoned on the LoI as a rowan tree, without leaves there is nothing to identify it as a rowan tree. We have thus blazoned this as a generic tree
Submitted as Asgar Roulfs sunu, there was some question whether the name Roulf was Old English or Old Danish. Although some form of it is found in Latin in an Old English manuscript, the consensus was that it was almost certainly Old Danish. If this is the case, then it the byname Roulfs sunu violates RfS III.1.a Linguistic Consistency, which states that a name phrase must be in a single language. Reaney, A Dictionary of British Surnames, p xviii, notes "This is also a common Scandinavian formation: Þurferð Rolfes sune." As the form Rolfes sune is consistent with a single language usage, we have changed the name to Asgar Rolfes sune in order to register it.
Bruce is the submitter's legal given name.
This name mixes Middle Irish and Early Modern Irish; this is one step from period practice.
While Ceolfara is an acceptable constructed Old English given name, all evidence points to it being a masculine name. While modern English speakers are used to an -a at the end of a name indicating a feminine name (as this is usually true of Latin or Latinized names), this is not always the case in Old English. The bearers of the names we have found using the theme -fara are masculine names, and deuterothemes in Old English are rarely gender neutral. Please inform the submitter that this is a masculine name.
There was discussion whether the blazon Paly argent and vert should be retained or if it should be changed to Argent, three pallets vert. As noted when registering Deanna della Penna's device in the February 2007 LoAR, the blazons and the corresponding emblazons for paly and three pallets are interchangeable. We have therefore kept the submitter's original blazon.
Nice late 16th C Anglicized Irish name!
With five fleurs-de-lys this could either be blazoned as on a chevron Or five fleurs-de-lys gules or a chevron Or semy-de-lys gules. We have elected to retain the submitted blazon.
Registered in May 1985 with the blazon Gules, on a sun Or a crescent inverted sable, in base a chevron inverted Or, the chevron is a co-primary charge, not a secondary charge.
Originally submitted as Cristyne Landebert, the name was changed at kingdom to Cristyne Landebertin, because, per precedent at the time the name was submitted, most bynames in German women's names had to be in the feminine or genitive form. While it appears that most German women's bynames in period were feminized by putting them in the feminine or genitive case, there are a few examples where it appears this has not happened. Until such time as a more specific rule of when it is appropriate to femininize German women's bynames can be formulated, precedent now holds that they can be registered in both their feminine or masculine form. The client in this case indicated that she most desired the form she submitted. However, if she is interested in an authentic name, we suggest that she use the feminized Cristyne Landebertin.
Nice device.
This was registered in October 1976 with the blazon Azure, on a crenelated wall issuant from dexter argent, a starling close to sinister argent perching upon a nest Or. That blazon would make the bird and nest tertiary charges, which they aren't; and the wall would not issue from base, as it does in the emblazon. Pictorially, the "wall" is the lower dexter 2/3 of a field per fess embattled. The nest is resting in the embattlements; and the bird is standing on the nest.
Submitted under the name David Erbe von Bärau.
Submitted under the name David Erbe von Bärau.
Submitted under the name Laurencie La Martre.
Martiall Company is a designator dated to 1629 in "Naming the Honourable Artillery Company", found in Duncan's Cavalier Webpages (http://victoria.tc.ca/~godwin//duncanweb/documents/hacname.html ).
Submitted as Emma MacMinn, MacMinn is a header spelling in Black, The Surnames of Scotland. Header spellings are only registerable if they can be shown to be consistent with period spellings, but there is no evidence for spellings like MacMinn until after 1650. Black shows the spelling M'Men in 1426. We have change the name to Emma MacMen in order to register it.
Blazoned on the LoI as staffs, many commenters thought that they should be blazoned as bars couped as the rounded ends were not visible on the mini-emblazon. These are much thicker than would be expected for walking staffs. We have chosen to use the term rods to allow a more accurate recreation of the emblazon and to differentiate them from walking staffs and ragged staffs. There is no heraldic difference between a rod and a staff.
This device is clear of the device for Raymond Norgate, Argent, billety sable. There is a CD for changing the number of charges and, as billets have a longer vertical axis than horizontal axis, another CD for changing the orientation of the charges.
Nice Middle Irish name!
The tau cross is correctly drawn - it is throughout in only three directions; there is a significant amount of field showing above the crossbar.
This badge was to be associated with Blaecstan Keep, but that name is returned elsewhere in this letter.
Please advise the submitter to draw the brazier with legs to aid in the identifiability of the charge.
Submitted as Malise Lauird, the cited documentation does not support Malise as a period spelling. Black, The Surnames of Scotland, cites a Malise Bane in 1320. An examination of the source from which this name was drawn, Cartularium Comitatus de Levenax p.p. 47-48, shows that it is Black's (modern) translation of a name that appears in Latin as a part of the full name Gillemore filio Malisei dicti Bane. It is highly likely that this name is a Latin representation of a Gaelic name and not an indication of an Anglicized or Norman spelling. Therefore, this precedent still applies:
Submitted as Malise der Totschläger, the given name, Malise, was documented from Withycombe, The Oxford Dictionary of English Christian Names, as an Anglicization of the Gaelic name Mael Iosa. Withycombe is not a reliable source for non-English names or for anglicizations of Gaelic names. However, Black, The Surnames of Scotland s.n. Malise, has Malis or Malisius in 1190 and 1210. The name is also listed in Reaney and Wilson, A Dictionary of English Surnames around the same time. We have changed the name to Malis der Totschläger to match the documentation." [Loar 09/2005, Atenveldt-A]
We have changed the name to Malis Lauird in order to register it.
Registered in June 1996 with the blazon Per bend sinister purpure and vert, a well argent masoned sable, the type of well was not specified. Please see the Cover Letter for a discussion on blazoning wells.
There was some question whether the spelling Sewere was found after the 13th C. John Russell, The Boke of Nurture, published in the 15th C, has the line "y wille þat ye obeye to þe marshalle, Sewere, & kervere."
Registered December 1991 with the blazon, Sable, on a pale invected between two lightning bolts argent, a fir tree couped proper, this has been reblazoned to specify the orientation of the lightning bolts.
Submitted as Oram y Maer, both the given name and the byname have problems. The given name, Oram, appears to be a modern form of the given name. The source used to document the name, Reaney and Wilson, A Dictionary of English Surnames, s.n. Orme, gives no dated versions of this spelling, instead, merely noting that the spelling is due to the strongly trilled r. We also examined Fellows-Jensen, Scandinavian Personal Names in Lincolnshire and Yorkshire, s.n. Ormr, but found no examples of Oram or Orum in that source. Reaney and Wilson date the spelling Orum to 1175, so Orum is registerable.
The byname has formation and meaning problems. Harpy notes:
If the submitter is interested in a byname meaning "(of) the stone" then I believe the submitted form "y Maer" may be an error somewhere along the line for "y Maen". "Maen" means "stone" and is mildly common as a place-name element, e.g., in the locative byname:
P'wer Maynarthur~ (i.e. Perweur Maenarthur -- Black Book of St. Davids 1326)
As a common place-name element, it may fall in the category of the sorts of nouns used as bynames with a definite article -- although note that the examples given are of owned objects, whereas I'd tend to expect "maen" to be locative in function. I don't have any examples of locative elements in bynames of the form "(definite article) (simple uncompounded topographic term)", although this is precisely the type of element that sometimes shows up in the construction "o (definite article) (simple uncompounded topographic term)", as in:
Ithel or Berth ("perth" = "grove, bush" -- Bromfield & Yale rental 1315)
(de) Madoco or Dol ("dol" = "meadow" -- Merioneth Lay Subsidy 1292)
Anghar' or pant ("pant" = "valley" -- Merioneth Lay Subsidy 1292)
Ithel Orellyn ("llyn" = "lake" -- Merioneth Lay Subsidy 1292)
So I'd be more likely to expect "or Maen" (of [from in the spatial sense] the stone) rather than "y Maen" (of [associated with or owning] the stone).
We have changed the name to Orum or Maen, a form which fixes the various problems with the submitter form and gives the byname the desired meaning.
Registered December 1993 with the blazon, Gules, semy of lightning bolts on a chief argent three clouds sable, this has been reblazoned to specify the orientation of the lightning bolts.
Submitted as Tabitha Johnstone of Annandale, the earldom of Annandale and the chiefdom of Clan Johnstone go hand in hand. The current clan chief is Patrick Andrew Wentworth Hope Johnstone of Annandale and of that Ilk. Given this, names combining Johnstone and Annandale may be viewed as claims to be the chief of Clan Johnstone. We have dropped the locative and registered this name as Tabitha Johnstone.
The name the Traveller is an SCA-compatible English byname.
Originally submitted as Asa beiskalda, the name was changed to Asa beiskaldi at kingdom to match available documentation. The byname is from the Landnámabók. An examination of an online copy of this work (http://www.snerpa.is/net/snorri/landnama.htm) shows the byname as beiskalda. We have changed the name back to the originally submitted spelling.
The submitter is a duchess and thus entitled to display a crown.
Submitted as Clarisse de Menoncourt, the submitter requested an authentic 13th C French name. The documentation for the given name, Withycombe, The Oxford Dictionary of English Christian Names, s.n. Clarice, gives Clarisse as a 13th or 14th C form in England, but this does not necessarily mean it is a good French form. Colm Dubh, "An Index to the Names in the 1292 Census of Paris" shows the form Clarice. We have changed the name to Clarice de Menoncourt to comply with her requests for authenticity. We note that the name as submitted is registerable, but, because we could not find the spelling Clarice used in France in the 13th C, we cannot guarantee that it is authentic.
Please inform the submitter that comments on this device included "Lovely!", "It's superb!" and "Exemplary!". This is a wonderful example of period-style heraldry.
This name mixes Gaelic and Anglicized Gaelic; this is one step from period practice.
Please advise the submitter to draw the cross larger.
Nice 15th C Russian name!
The submitter requested that the hen be blazoned as a geline for the sake of the cant. This term is not a standard heraldic term, nor is it a common modern term. Given the difficulty one would have in determining what a geline is, we decline to use it in this blazon.
We wish to inform the submitter that cants needn't be blazoned. The arms of the Earls of Arundel, with their martlets, are canting arms: but you'd only know that if you knew that the French for "swallow" is hirondelle. The martlets aren't blazoned that way; but that doesn't stop them from canting. The same is true here.
The banding on the fleurs-de-lys, gules in this case, is an unblazoned artistic detail.
The use of pawprints is a step from period practice.
This name uses the name of a non-Christian deity; this is one step from period practice.
Registered October 2001 with the blazon, Azure, on a pile argent between two lightning bolts Or a double-bitted battle axe sable, this has been reblazoned to specify the orientation of the lightning bolts.
Kenneth is the submitter's legal given name.
Registered June 1989 with the blazon, Azure, two axes in saltire between two lightning bolts palewise inverted Or, issuant from a chief nebuly argent, this has been reblazoned to specify the orientation of the lightning bolts.
A daisy proper is argent, seeded Or.
Submitted under the name Melbrigða Leifsdøttir.
Please advise the submitter to draw the bordure narrower.
Registered August 1980 with the blazon Vert, a magpie [pica pica] close proper grasping in its dexter talon a feather argent, it was not clear from the blazon that the feather is a maintained charge. We have dropped the Linnaean reference in accordance with current SCA heraldic practice.
Registered in May 1984 with the blazon Gules, on a pale nebuly endorsed nebuly argent, a schaum in profile sable, a schaum is another spelling for a shawm. However, the instrument shown here has the capped reed and upward curve which are the defining characteristics (both musicologically and heraldically) of the krummhorn. While there is no heraldic difference between the two, we have chosen to reblazon this as a krummhorn so that the emblazon can accurately be recreated from the blazon. The endorses, as with cotises, shares the line of the ordinary, thus the second nebuly is not needed in the blazon.
Registered in November 1982 with the blazon Azure, in bend sinister two spikes of barley bendwise sinister embowed Or surmounted by two hop cones conjunct in fess argent. [Hordum vulgare] [Humulus lupulus], the barley stalks are not in bend sinister; they're parallel but definitely in bend (but bendwise sinister embowed). As far as we can determine, the term conjunct has no heraldic meaning: the two hop cones here are in fess, slightly tilted to one another, one overlapping the other. It can't really be blazoned, but conjunct doesn't mean anything. We have reblazoned this the best we can using current SCA heraldic terminology, including dropping the Linnaean description.
Registered June 1998 with the blazon Sable, in pale a sunburst conjoined to a demi-lightning bolt issuant to base and a laurel wreath Or, this has been reblazoned to clarify the placement of the laurel wreath.
Nice armory.
Registered in February 1992 with the blazon Per fess with a left step to sinister sable and Or, a griffin salient to sinister and a bat winged wyvern tailed demi-stag erect, counterchanged, the term left step to sinister has no heraldic meaning. This motif was first submitted by Andreas Syndikus Drachenfreund in December 1983, at which time Laurel ruled, "I will accept the proposed German line of division as "per fess with a left step" (the translation of the German blazon given on P. 100 in Woodward's)." We have reblazoned Iric's device in accordance with that precedent.
Registered in May 1998 with the blazon Argent, a well sable, the type of well was not specified. Please see the Cover Letter for a discussion on blazoning wells.
This device does not conflict with the badge for Catrin ferch Dafydd, Azure, a rose, slipped and leaved, within a bordure dovetailed argent; there's a CD for changes to the secondary charge and another for adding the tertiary rose. Precedent states:
[two roses azure each charged with a rose argent vs a semé of roses] ... there is a CD for changing the number of secondary charges and a second CD for adding the tertiary charges. As drawn the charges in chief cannot be double roses as the outer rose and the inner rose have different orientations. [Beatrice Domenici della Campana, 05/01, A-An Tir]
We do not grant a CD for the orientation of a rose. The orientation in a double rose is even harder to determine. Given this, the precedent cited above is hereby overturned - the orientation of the tertiary rose is not a factor in whether or not the inner rose is considered tertiary charge. However, if you charge a rose with a rose of a different tincture, it is a rose with a tertiary rose whether it is blazoned as a double rose A and B or as a rose A charged with a rose B. The orientation of the rose is not worth difference one way or the other.
Registered December 2004 with the blazon, Quarterly vert and Or, in bend a hammer sable between two lightning bolts Or, this has been reblazoned to specify the orientation of the lightning bolts.
Amphisbaenae have feathered wings by default; the one in this submission has bat-wings, a fact that must be explicitly blazoned.
- Explicit littera accipendorum -
None.
The submitters have not demonstrated that this order name follows period meta-patterns for order names. The meta-pattern for this name is listed as "heraldic charge." Now, the OED has three possible definitions for this term that could fall under this pattern: as a rare heraldic term for a chevron, as a segment of a bird's wing, bearing the primary flight feathers, and as the shoulder-blade of a mammal. The submitters are claiming the third sense. However, are two problems with this. First, the definition of a pinion as a part of a wing is the one likely to come to mind, and lions don't generally have wings. Second, there are no registrations of either a pinion, a shoulder, or a shoulder blade, nor have the submitters or any of the commenters found such a charge used in period heraldry. This, then, requires documentation showing that a shoulder blade is a reasonable and unique heraldic charge, and that a lion's shoulder blade is distinct from the shoulder blade of other creatures shoulder blades (or at least from other non-feline creature's shoulder blades). Neither the submitters nor the commenters have provided such documentation. Barring documentation demonstrating that a lion's pinion has a unique depiction suitable for use as a heraldic charge, this order name is not registerable.
This badge is returned for conflict with Gareth de Grey's device, Sable, an hour glass argent, and badge, (Fieldless) An hourglass argent, framed of wood proper. In each case there is a CD for fieldlessness, but that is the only CD. Laurel has previously ruled that "[an hourglass purpure framed Or vs. an hourglass Or] ... the inside of an hourglass is at least half the charge. [Carlos Juan Ramiro, 12/99, A-Atlantia]". As an hourglass may be drawn with or without the side posts, as noted when registering the device for Nathaniel Grendel the Red in November 2002:
The College of Arms generally felt that the hourglass would be more recognizable with vertical posts on the sides of the frame. This hourglass is drawn with the standard top and bottom plate, but without any vertical side posts holding the top and bottom plates together. However, hourglasses without side posts were noted to be a "standard Society depiction" of an hourglass, so this depiction is acceptable: "...with the hourglass drawn in one of its standard Society depictions (i.e., without the posts)" (LoAR 26 November 1989). We encourage the submitter to draw future renditions of the hourglass with the posts to enhance the identifiability of the charge.
As such, the frame of an hourglass must be considered less than half the charge and its tincture counts naught for difference between hourglasses.
This device is returned due to the improper coloring of a brown hare proper. The October 1995 Cover Letter stated:
PRECEDENT: Henceforward, and more in line with period heraldic practice, animals which are normally brown may be registered simply as an {X} proper (e.g., boar proper, hare proper). Animals which are frequently found as brown but also commonly appear in other tinctures in the natural world may be registered as a brown {X} proper (e.g., brown hound proper, brown horse proper).
This precedent does not, however, loosen the ban on "Linnaean proper" (Cover Letter, May 13, 1991); proper tinctures for flora and fauna which require the Linnaean genus and species to know how to color them. For example, a falcon proper will be considered to be all brown, not brown head, wings and back, buff breast with darker spots, and a tail striped with black; a hare proper will be considered to be all brown, not brown with white underbelly and tail and pink ears. This also appears to be more in keeping with period heraldic practice.
The inner part of a brown hare proper's ears should not be argent, nor should its tail. In addition, the ear and tail are argent on an argent field, therefore this device must also be returned for lack of contrast.
This badge is returned due to the improper coloring of a brown hare proper. The October 1995 Cover Letter stated:
PRECEDENT: Henceforward, and more in line with period heraldic practice, animals which are normally brown may be registered simply as an {X} proper (e.g., boar proper, hare proper). Animals which are frequently found as brown but also commonly appear in other tinctures in the natural world may be registered as a brown {X} proper (e.g., brown hound proper, brown horse proper).
This precedent does not, however, loosen the ban on "Linnaean proper" (Cover Letter, May 13, 1991); proper tinctures for flora and fauna which require the Linnaean genus and species to know how to color them. For example, a falcon proper will be considered to be all brown, not brown head, wings and back, buff breast with darker spots, and a tail striped with black; a hare proper will be considered to be all brown, not brown with white underbelly and tail and pink ears. This also appears to be more in keeping with period heraldic practice.
The inner part of a brown hare proper's ears should not be argent. In addition, the ear is argent on an argent field, therefore this badge must also be returned for lack of contrast.
No documentation was submitted and none found to suggest that the given name Rosmerryn is a valid constructed given name. First, there is no documentation that the spelling of the second element, -merryn, is found in period. While documentation was provided that this is a modern name form for a saint found from 900, this is not the same as showing this was the form used in 900. Second, while Old English names are often diathematic, to create a diathematic name, you must demonstrate that both parts of the name are used as themes, and that each theme is being used in its proper place. Unfortunately, even if Merryn was an attested Old English spelling, there is no evidence that it was a theme rather than a name. In fact, the name which the documentation cites as the etymological ancester of Merryn -- Modwenna -- may be, itself, a diathematic name. Searle, Onomasticon Anglo-Saxonicum lists both Mod- and -wen. If the submitter is interested in a French given name with similar sounds, Colm Dubh, "An Index to the Given Names in the 1292 Census of Paris" (http://www.sca.org/heraldry/laurel/names/paris.html) lists the feminine Rose and the masculine Roussel, Roumain, and Marin.
Her armory was registered under the holding name Randal of Elfsea.
This is returned for redraw; the scarpes are too thin. Blazoned on the LoI as Azure, on a bend sinister azure fimbriated between two hammers bendwise sinister a hammer bendwise sinister argent, a fimbriated bend cannot be the same tincture as the field it lies on. Such a bend appears to be two scarpes rather than a bend fimbriated. What was drawn very thin to act as fimbriation must be interpreted as scarpes - extremely thin scarpes, but scarpes nonetheless. They need to be two or three times wider on resubmission.
This name was withdrawn by the submitter.
None.
This badge is returned for conflict with the device for Vallaulfr Rurikson, Azure, two scarpes between two wolves passant argent. There is a CD changing the type of secondary charges but that is the only difference. Please advise the submitters to draw the scarpes wider on resubmission.
This heraldic title has two problems. First, it does not follow known patterns for heraldic titles. The word hringboga is defined in the LoI as meaning "ringed creature" or "dragon"; the literal translation appears to be (hring) "coiled" (boga) "bow". The word appears in Beowulf as a description or kenning for the dragon, where the dragon is lying coiled and ready to strike. The Oxford English Dictionary s.v. kenning, describes a kenning as "One of the periphrastic expressions used instead of the simple name of a thing." As a roundabout description (kenning) instead of a straightforward noun, it is unlikely that the word hringboga is a reasonable name for a heraldic charge, which is the only possible pattern for a title based on an epithet for a dragon. We note the straightforward title Wyrm Herald ("Wyrm" is a straightforward term used for "dragon" in Old English according to Bosworth-Toller, An Anglo-Saxon Dictionary, s.v. Wyrm), which would fit the model of heraldic charge (albeit with the descriptive element in a pre-heraldic language), and which is currently free from conflict.
We also note that, as far as we are able to determine, hringboga, not hringbogan is the nominative form of this kenning. Hringboga and hence hringbogan appears to be in the weak declension, making hringbogan the genitive or dative form of this word. Nouns in heraldic titles based on heraldic charges are found in the nominative case.
Since the heraldic title was returned, it can not be transferred.
This device is returned for violating the "sword-and-dagger" rule. As ruled in the March 2007 LoAR (v., Desiderata Drake):
While it is acceptable to use the same charge as both a primary (or secondary) charge and a tertiary charge, using a similar charge is not acceptable for exactly the reasons discussed in the September 1993 Cover Letter. We hereby overturn the February 2003 precedent and restore the September 1993 precedent. Due to the armorial identification problems caused by using similar but not identical charges in two different charge groups, this practice is no longer allowed. The use of identical charges as both a primary (or secondary) charge and a tertiary charge is allowed.
Having two different styles of Celtic crosses is not allowed. The crosses on the chief do not resemble the stone cross upon which the SCA based this charge, nor do they resemble the crosses seen in the Book of Kells and other period manuscripts. All of the period examples of which we are aware have ends wider than the center. However, given the variation of Celtic crosses we have registered, these are currently registerable. This overall design is registerable if the submitter chooses a single type of Celtic cross to use.
Since the heraldic title was returned, it can not be transferred.
This device is being returned for a redraw of the Maltese crosses. Please see the Cover Letter for a discussion on the correct way to draw a Maltese cross.
This device is being returned for a redraw of the Maltese crosses. Please see the Cover Letter for a discussion on the correct way to draw a Maltese cross. On resubmission, please advise the submitter to draw the lion larger.
This device is returned for a redraw of the primary charge. Blazoned on the LoI as an ash tree, it is not recognizable as a tree of any type. It more closely resembles a bush. Please instruct the submitter that the tree should have a longer trunk. Overly large leaves are frequently seen in period heraldic oak trees, and such leaves are acceptable for an ash tree, but they should still be drawn proportionally smaller than the leaves in this emblazon.
This device is returned for a redraw or redesign. The charges in chief were originally blazoned as crosses of Jerusalem. This was changed to three crosses couped each between four more crosses couped Or by the Calontir College of Heralds, who noted "We believe the plain cross between four plain crosses to be a valid depiction of a Cross of Jerusalem. We have, however, changed the blazon in kingdom to a more generic one." However, we have no evidence that these are a period variation of a cross of Jerusalem.
The charges in chief aren't a group of three self-contained charges (Jerusalem crosses): they are a group of three "primary" secondaries (the larger crosses couped) and twelve "secondary" secondaries (the crosses couped surrounding them). That's the problem. This is not a case of a single group with two types of charge, as we'd have if this were in chief a cross couped between two mullets or some such. Nor are the three larger crosses and twelve smaller crosses separate groups of secondaries. These are all one group of identical secondary charges, but with a definite "subdivision" which doesn't make for the simplicity that characterizes medieval heraldry. A cross of Jerusalem would not have this problem as it is considered a single charge.
No documentation was submitted and none found to suggest that the Gaelic name Leocán, which the submitter Anglicizes as Logan, was in use as a given name late enough that it is reasonable to suggest an Anglicized form for it. While O Logan is found in Woulfe, Irish Names and Surnames, s.n. Ó Leogáin, as a late period Anglicization of the surname, by the late 16th C, Irish surnames using Ó were no longer representative of the name of a close relative (such as a grandfather). Instead, they represented the names of eponymous ancestors from the 9th C or so. The latest example of the given name Leocán we have found is an entry for 1065 in the Annals of Ulster. Because we have no examples of Leocán in use at a time when an Anglicized form is possible, the Anglicization Logan is not registerable.
The LoI noted that Logan was the submitter's legal middle name. Because middle names may be either given names or surnames by type, to be registerable as a given name under the grandfather clause, a middle name must be a given name by type. Unfortunately, Logan is a surname by type: Black, The Surnames of Scotland, s.n. Logan, notes that the surname derives from a placename. Black makes no mention of the name as a given name. Therefore, Logan is a surname by type and thus not registerable as a given number under the grandfather clause in this case.
His armory was registered under the holding name Brian of Coeur d'Ennui
This badge is returned for conflict with the Dukes of Mecklenburg (important non-SCA arms), Or, an ox's head cabossed sable crowned Or. The removal of the crown is not worth a CD, nor is adding the flames. Thus there is only a single CD for fieldlessness.
This badge is returned for lack of identifiability. Most of the commenters noted that the combination of wings and the bull's head was unidentifiable. As al-Jamal commented:
I'm not at all sure about multiply winging a bull's head this way. The identifiability of exactly what has been done to the bull's head is difficult to make out without recourse to the blazon. The wings to the sides of the head are clear enough, the the lower wings are more likely to be mistaken for flames, and the upper wings put me more in mind of Don King's hairstyle than they do the addition of wings.
Lacking period heraldic evidence that seraph's wings were applied to other charges, this motif is not registerable.
This device is returned as it is too complex. The rule of thumb complexity count limit, as explained in RfS VIII.1.a, is eight. This device has five tinctures (gules, sable, argent, Or and ermine) and five types of charge (chevron, tower, tyger's head, crown, bordure), six if you count the flames, for a complexity count of 10 or 11.
Blazoned on the LoI as a panther's head, the primary charge lacks the spots of an heraldic panther. An English panther (or panther) also would not have the mane and tusk shown here. Because of the tusk, we have blazoned the charge as a tyger's head.
The submitter is a duke and thus entitled to display a ducal coronet.
None.
This is returned for a redraw as the cotises are so wide in comparison to the central chevron that this appears to be a badly drawn three chevrons. While a chevron cotised is the same motif as used in the canton's arms, the cotises in that emblazon are only about a quarter of the size of the chevron and therefore lacks the identifiability problem inherent with the submitted emblazon.
This device is returned for lack of contrast. A rainbow's clouds, like maintained charges, don't necessarily need good contrast with the field, but there must be some contrast. The argent clouds on the argent field have no contrast and this must be returned.
When her previous submission was returned in December 2002, Laurel noted:
The natural rainbow is drawn with argent clouds by default, and this rainbow is also drawn with argent clouds. The clouds have no contrast with the argent portion of the field on which the rainbow lies. This may well be a reason for return. However, in some cases it is allowable for a charge to have some small no-contrast details as long as the overall identifiability of the charge is maintained. At this time, we decline to rule on whether it is acceptable to have a natural rainbow with its proper argent clouds on an argent field, as there was no clear College consensus about whether this should be acceptable. It is allowable to have a natural rainbow proper clouded in some specified tincture, and we encourage the submitter to avoid this question by resubmitting with a rainbow where the clouds have some contrast with the underlying field.
Since that time, it has been ruled multiple times that maintained charges must have some contrast with the field (e.g., Symon de Warwyck, August 2006). The clouds of a rainbow are essentially maintained charges and thus must have some contrast with the field.
This device is returned for lack of contrast. The identifying parts of the thistle are vert and purpure on the azure portion of the field, while most of the brown stag is also on the azure portion of the field. The argent attires help somewhat with identifying the stag, but overall the lack of contrast fatally hinders the identifiability of these charges. The device must therefore be returned.
This name combines English and French in the same name phrase in violation of RfS III.1.a, Linguistic Consistency. While the submitter has provided evidence of compound descriptive names that combine words of French origin with words of Old English origin, he has not provided any that combine French words that were not adopted into English as ordinary words (such as loupe, "wolf") with English words. As such, then, this household name is in violation of our Rules for Submission. In addition, while bynames based on inn signs are typically shown as a single word, we have no examples of actual inn signs that follow this pattern.
If the submitter is interested in a tavern name consistent with the design on the badge, we suggest Wolfes Head Taverne. The English word wolf is well attested; in the Oxford English Dictionary, s.v. wolf, the word wulf appears in Old English in 725, and wolfes in 1552. Mari Elspeth nic Bryan, "English Sign Names", (http://www.s-gabriel.org/names/mari/inn) lists the Bull Head and the Boar's Head. White Wolfes Head Taverne also follows patterns found in this article.
No documentation was submitted and none found to suggest that the town of Bärau was found in period or that the submitted spelling was used in period. Barring such documentation, this name is not registerable. We cannot drop this element in order to register the name because David Erbe is the submitter's legal name.
His device and badge were registered under the holding name David of Carillion.
This badge is returned for conflict with device for Siobhán NicDhuinnshléibhe, Vert, in pale an owl affronty perched atop a branch fesswise argent between three drop spindles inverted sable, threaded argent, which is reblazoned elsewhere in this letter. There is a CD for removing the spindles. There is not a CD for the orientation of the branch, therefore the second CD must come from a difference between the birds.
We have a precedent granting a CD between an owl close (i.e. in its default posture) and a falcon close (in its default posture): "[T]here is another CD for changing the type of bird from an owl close to a falcon close." [Falco de Jablonec, June 02]. In this case, though, neither bird is exactly default: Dieter's hawk is guardant (which is far more typical for owls than hawks), and Siobhan's owl is affronty (which is not attested in period armory). This means that we must go by visual appearances. In this case, there is insufficient visual difference to grant a CD between the birds (in these specific postures).
Blazoned on the LoI as a red-tailed hawk, there is no way to tell a red-tailed hawk from any other hawk when it is completely argent.
As noted on the LoI:
The SCA considers simple-edged roundels to be a medium for heraldic display, and does not register badges that start "(Fieldless) On a roundel..." The most recent precedent is from April 2002 (Solveig Throndardottir, 04/02 A-Æthelmearc): "Note that this does not change our long-standing policy about such "shield shape" charges used in fieldless badges if the tincture is not plain (thus, divided or with a field treatment), or if the charge is itself charged."
This is sufficient grounds for return. The submitter may register (barring conflict or other problems) Argent, a hare courant sable, a bordure gules. However, Gules, on a plate a hare courant sable, which is a valid interpretation of this emblazon, would conflict with a protected historic flag of Germany, Gules, on a plate a cross gammadion saltirewise sable. There would be a single CD for changes to the tertiary charge.
This name mixes an Old English surname with a Middle English designator; in the case of a household name, the designator and the descriptive element constitute a single name phrase:
[Household name MacLeod Keep] Additionally, in the submitted household name MacLeod Keep, Keep is solely English and MacLeod is Scots. While Scots is a language closely related to English, they are not actually the same language. Therefore, the submitted MacLeod Keep violates RfS III.1.a, which requires linguistic consistency within a name phrase. [Simon MacLeod, 07/2003 LoAR, R-Meridies]
Therefore, this name violates RfS III.1.a, Linguistic Consistency, which requires that all elements in a single name phrase be in a single language. Mills, A Dictionary of British Placenames, s.n. Blaxton, lists Blacstan in 1213 and Ekwall, The Oxford Dictionary of English Placenames, s.n. Blaston, lists Blaeston in 1163. We would change the name to one of these Middle English forms, but the submitter will not accept major changes such as a change of language.
Aural conflict with Saint Laurence, known as Saint Laurence the Martyr. Batonvert notes:
I can't see how this doesn't conflict with St. Lawrence the Martyr, one of the great saints of the medieval church, who has been described as the "typical figure of a martyr". "From the fourth century," says Attwater's Dictionary of Saints, "he was venerated as one of the most famous martyrs of the city of Rome."
Her armory was registered under the holding name Dianne of the East.
This device is returned for conflict with the device for Isabella Catharini, Purpure, on a bend cotised argent three irises purpure. There is a CD for changing the secondary charges from cotises to triquetras. While there is a CD between an iris and a forget-me-not, there is not the substantial (X.2) difference required for a CD between tertiary charges.
This device is clear of the device for Etain Winterbourne, Purpure, on a bend between two escallops argent, three violet plants palewise vert, flowered purpure. The violet plants are half vert and half purpure, with each plant having three flowers. There is a CD for the changes to the tertiary charges and another for changing the escallops to triquetras.
This badge is returned for multiple conflicts. This conflicts with the device for Eleanor of Pica, which is reblazoned elsewhere on this letter as Vert, a magpie proper maintaining in its dexter talon a feather argent. There is but a single CD for fieldlessness.
This badge also conflicts with the device for Dafydd Wallraven, Per fess argent and purpure masoned argent, in chief a raven close sable and the device for Thorolf Oddson Villannen, Per pale argent and ermine, in dexter base a raven close proper. In each case there is a CD for fieldlessness but no difference is granted between a magpie and a raven. Nor is there a CD for location of the ravens when compared to a fieldless badge. A magpie can have varying amounts of white; some depictions of a magpie proper are primarily sable. Given this, there is not a CD for tincture between a magpie proper and a magpie sable.
Concerning the device for Serlo of Litchfield, Gyronny gules and Or, a vulture close sable, there is a CD for fieldlessness, but nothing for tincture of the bird. The question thus becomes whether or not a magpie conflicts with a vulture. There are prior precedents stating that a vulture conflicts with a hawk. There is no difference granted between a hawk and a raven, nor between a raven and a magpie. However, conflict is not necessarily transitive and a vulture may not conflict with a magpie. If this is resubmitted, we recommend that the submitter (and the East CoH) be prepared to show that a CD should be granted between a magpie and a vulture.
Unfortunately, this badge must be returned under RfS X.5 for visual conflict with a badge for the Barony of the Forgotten Sea, (Fieldless) A Ukrainian trident head vert. We wish to inform the submitter that this identical badge was returned in September 2006 (v. Pipa Sparkes).
This device must be returned because the mini-emblazon (and the emblazon in OSCAR) do not match the emblazon received by the Laurel office. This is sufficient grounds for return by itself. In addition, the large emblazon shows a log that is neither fesswise nor bendwise, but somewhere halfway between. This is also sufficient grounds for return. Please advise the submitter to redraw this as clearly fesswise or clearly bendwise on resubmission.
If the submitter truly wishes a branch, rather than the charge emblazoned on this submission, the branch needs to be much thinner (and branch like).
As the device has been returned, the blanket permission to conflict must also be returned.
This device is returned for non-period style. We are unaware of any examples of a primary chevron accompanied by braced secondary chevronels. Barring period heraldic examples of this motif, it is not registerable.
This device is returned conflict with both the arms of the March of Grimfells, Sable, on a pile throughout Or a spiderweb throughout sable charged with a laurel wreath vert, and with the device for Oyn Cefnog, Sable, on a pile throughout Or three pheons two and one gules. In each case there is but a single CD for changes to the tertiary charges.
This device is returned for redraw of all of the charges. The chevron and its cotises are too low on the field. We have consistently returned overly enhanced or abased ordinaries (e.g., Muirgius mac Con Mara hui Ségdai, 11/2002), when not supported by period examples. The sprigs of holly are not sprigs - each is a set of disconnected leaves and disconnected berries. In addition, the berries were missing from the mini-emblazon.
This device is returned for conflict with Ana Moonstar's device, Azure, a wolf rampant reguardant Or, maintaining in its teeth a mullet of eight points argent, standing upon a moon in her plentitude per pale argent and sable. As noted in the March 2006 LoAR (v. Elric Strangulf, R-An Tir), Ana's moon is equivalent to a maintained charge and thus there is only a single CD for making the wolf fretty.
This device is returned for redraw of the line of division. A chief indented flory at the lower points would be an acceptable line of division; however, as drawn here, this emblazon of the line is not acceptable. On resubmission there should be fewer points - about half as many - and larger fleurs-de-lys.
Blazoned on the LoI as a catamount, this is not a catamount as defined in the SCA: i.e., a mountain lion. This is a Scots cat-a-mountain, commonly blazoned as a wildcat.
This name conflicts with the Calon Cross, Order of the, registered May 1990. Recent precedent holds that incomplete forms of a branch name are considered transparent for purposes of conflict:
[Order of the Guardians of Fontaine.]This order name conflicts with the Order of the Guardians of Atenveldt. The summarization of documentation states "Fontaine, as the name of the Barony, should satisfy the placename standard." While Fontaine is not the full name of the Barony, and the group has documented Fontaine as a mundane placename, the combination of the main descriptive element of the barony's name in an Order name with ownership by the barony makes it impossible to view this placename as referring to anyplace but the Barony of Fontaine dans Sable. This name should be registerable with a letter of permission to conflict from the Kingdom of Atenveldt. [March 2007]
In this case, it is impossible to view Calon in Calon Cross as anything but a clear reference to Calontir. We note that thie submitted name would be registerable with a letter of permission to conflict from the Kingdom of Calontir.
Conflict with the Order of the Golden Lily, Bosnia's highest military commendation. This order, according to "SFOR Stabilization Force" (http://www.nato.int/sfor/media/2004/ms040514.htm) is not only this region's highest military honor, but carries with it a yearly stipend. As the highest military honor of a country much in the news of late, we feel this real-world order name is worthy of protection.
This device must be returned as the emblazon is not reproducible from any blazon we could derive. Metron Ariston summed up the problem best:
As blazoned, I would have expected all the swords to be below the laurel wreath in their entirely. While this design fills the space better, it is not the one a reasonable heraldic artist would opt for and so I am not sure it meets the requirement that the emblazon be reproducible from the blazon.
This badge is returned for conflict with Katlin von Kappel, Per saltire sable and gules, four fleurs-de-lys bases to center Or. There is a CD for changes to the field, but that is the only CD; there is not a CD for the number, the arrangement, or the conjoining of the fleurs-de-lys.
The submitters have permission to conflict with the badge for Thomas de Castellan, (Fieldless) Four fleurs-de-lys conjoined in saltire, bases to center, Or.
Conflict with Eleanor of Toledo, wife of Cosimo de' Medici, Duke of Florence. While she does not have her own entry in Britannica Online, her name is extremely well known within the SCA; her portrait by Bronzino is the inspiration for one of the most popular and repeated Italian dresses in the SCA, and the pattern from her knitted stockings is legend with fiber arts folks. As such, she is well enough known in the SCA to be worthy of protection. The names Eleanor and Elena are too similar in sound and appearance, and the substantive elements of the bynames are identical.
This device must be returned as it appears to be marshalling. The Rules for Submission (RfS XI.3) state "Armory that appears to marshall independent arms is considered presumptuous....". The explanatory text of RfS XI.3.b states "No section of the field may contain an ordinary that terminates at the edge of that section or more than one charge unless those charges are part of a group over the whole field." Laurel has previously ruled:
After much soul-searching, I must agree with the commenters who saw an appearance of marshalling in the device. Rule XI.3.b states that quarterly may be used only "when no single portion of the field [appears] to be an independent piece of armory." In general, complexity in any of the quarters makes it look like independent armory; for example, XI.3.b explicitly cites the use of multiple charges in a quarter as unacceptable. The motif Quarterly X and Y, in bend two [charges] is allowable when the uncharged quarters are plain tinctures; we don't protect plain tinctures. But when the uncharged quarters are complex fields, we lose that rationale; and the complexity then begins to make it look like an independent coat. This, beneath all the subtext, is exactly what XI.3.b is meant to prevent. (Aric Thomas Percy Raven, October, 1992, pg. 30)
In this case, using a checky field in the uncharged quarters means that this submission must be considered marshalled arms. Uncharged quarters may only consist of plain tinctures and those must not be tinctures of protected important non-SCA arms (v. Murdoch Bayn, 08/2002).
In addition, the lozenges were blazoned on the LoI as conjoined; however, the lozenges are not touching and therefore are not conjoined. Therefore this also causes the submitted device to be marshalled arms.
This device is returned for a redraw of the gyronny. As al-Jamal notes: "Chiefs on divided fields are really treated as an extension of the shield; they do not overlie the underlying field divisions like in the emblazon here".
Old Norse grammar requires that the gender of the patronymic agree with the gender of the given name, but the genders of the name parts do not agree in the submitted name. Unfortunately, as best we can determine Melbrigða is a masculine name, a Norse form of the Old or Middle Irish Máel Brigte, which is also a masculine name. Talan Gwynek, "Old Norse Forms of Early Irish Names" (http://www.ellipsis.cx/~liana/names/drafts/irish-norse.html) notes "Although ON -a is a feminine ending, the name here is masculine." Metron Ariston notes "In the saga of King Harald in the Heimskringla the name is mentioned specifically as the name of a Scottish earl: "Sigurðr jarl drap Melbrigða tönn, jarl skozkan" (Earl Sigurd killed Melbrigða Tooth, a Scottish earl)." We would change the name to Melbrigða Leifsson, but the submitter wants a feminine name and will not accept major changes. We cannot change the given name to make it a feminine name, and changing the patronymic marker from døttir to son would significantly change the sound and appearance of the name. Therefore, we are forced to return this.
In resubmitting, please inform the submitter that the typical Old Norse feminine patronymic marker is -dóttir. The submitted spelling -døttir is appropriate for later Danish patronymics.
Her device has been registered under the holding name Michelle of Arenal.
No forms were received for this order name. The Administrative Handbook IV.C. says:
No submission, including any resubmission, appeal, change or release of a protected item, etc., shall be considered for registration until a complete set of paperwork is provided to the appropriate heraldic officer.
Because no forms were received by the Laurel office, we are forced to return this name. Without forms, we cannot provide an evaluation of the registerability of this name or suggestions for changes.
No forms were received for this order name. The Administrative Handbook IV.C. says:
No submission, including any resubmission, appeal, change or release of a protected item, etc., shall be considered for registration until a complete set of paperwork is provided to the appropriate heraldic officer.
Because no forms were received by the Laurel office, we are forced to return this name. Without forms, we cannot provide an evaluation of the registerability of this name or suggestions for changes.
This badge is returned for conflict with the device for Alexandra of Elentil, Sable, a mullet of eight points argent, a bordure gules, fimbriated argent. There is a CD for changing the tincture of the bordure, but nothing for removing the fimbriation. The lozenges in Rhys's badge appear to be a mullet of six points and thus not a CD from a mullet of eight points.
We note that the lozenges were blazoned on the LoI as conjoined, but they are not touching and therefore are not conjoined.
This device is returned for lack of identifiability. This combination of charges makes it nearly impossible to identify the fact that the bow is armed with a needle rather than the expected arrow.
None.
No documentation was submitted and none found to suggest that the name Delara was not a unique name in period. The name is documented from the article "Names of Persia", http://www.avesta.org/znames.htm, shows Delara as a name in use in Kermin in 1956. While the name occurs in the 11th C Epic of the Kings, it appears there as the name of the mother of Alexander the Great. We have no examples of the name in use in medieval Persia, nor do we have any other examples of the name except as the mother of Alexander. Barring documentation that this name was actually used in medieval Persia, or appeared in Persian literature referring to someone besides the mother of Alexander the Great, Delara is no registerable.
None.
This device is returned for a redraw of the grapes. As depicted in this emblazon, the roundels forming the grape bunches are not conjoined. In fact, no part of the bunches are conjoined. This is a very modern stylization of grapes, and therefore is not registerable.
- Explicit littera renuntiationum -
The submitter requested an authentic 13th C name, but this was not mentioned on the LoI. Although all the elements in the name are dated to the 13th C, it is less clear whether the structure of the name is appropriate for this time period. We are pending this name to allow the commenters to address the authenticity request.
Here is the original documentation summarization:
Elewys is documented from Talan Gwynek's "Feminine Given Names in A Dictionary of English Surnames, Part Three: The Names H-Z" at <http://www.sca.org/heraldry/laurel/reaneyHZ.html>under the header <Helewise> and is dated to 1273.
<Cuylter> is documented from "The textile industry in Essex in the late 12th and 13th centuries: A study based on accopational names in charter sources" by Michael Gervers at <http://www.utoronto.ca/deeds/pubs/doc3/app1.htm>as Richard Cuylter from Finchingfield, dated to 1240. The introductory page can be found at <http://www.utoronto.ca/deeds/pubs/doc3/intro.htm.>It is also documented in "12th & 13th Century English Textile Surnames" by Arayanhwy merch Catmael at <http://www.ellipsis.cx/~liana/names/english/textile.html>under the header <Quilter>, also dated to 1240.
<Finchingfield> is also documented from "The textile industry in Essex in the late 12th and 13th centuries: A study based on accopational names in charter sources" by Michael Gervers at <http://www.utoronto.ca/deeds/pubs/doc3/app1.htm>as Richard Cuylter from Finchingfield, dated to 1240.
Also included is a page of bibliographical information from an unknown article at <http://eh.net/coursesyllabi/syllabi/munro/NewDrap2.htm.>
This was item 9 on the An Tir letter of January 31, 2007.
This device is pended for discussion on whether or not we should protect Rohan, Vert, a horse courant argent. Latimer in commentary noted:
The Lord of the Rings having undergone a resurgence in visibility and popularity since the 1995 decision not to protect its armory, I request reconsideration of the protection of Rohan: Vert, a horse courant argent. This is notably visible in the movie (albeit sporadically) as the war banner carried into the battle at Minas Tirith. (The banner is double-sided, with the horse facing the hoist, and is rendered in an artistic style resembling the dismemberment here.) If Rohan is protected, then this must be returned, having just one CD for adding the secondary charges.
The 1995 ruling that Latimer references states "The commentary on this and the other proposals from Tolkien was somewhat mixed. However popular the Lord of the Rings trilogy is among older members of the SCA, it appears to have lost much of its status over the intervening years. Here, the commentary generally favored not protecting these arms."
As no commenters addressed the issue, we are pending this for discussion on whether or not Rohan's arms should be protected. We encourage commenters to give their opinions either way, not just to rely on the comments by the first person to respond in OSCAR.
This was item 24 on the Caid letter of January 24, 2007.
This name combines Occitan and Spanish, but no information was submitted or supplied by the commenters to show substantial contact between the Occitan speaking regions and Spain (in this case Aragon). While we believe that this should not be a problem, we would like explicit information on such contact. Therefore, we are pending this name to allow commentary on contact between these regions.
This was item 2 on the East letter of January 30, 2007.
- Explicit -
Created at 2007-09-02T11:09:59