Middle Kingdom - Internal Letter of Acceptances & Returns – August 2002
This is the August 2002 Middle Kingdom Letter of Acceptances and Returns for Escutcheon’s and Keythong’s June Letters. Unless otherwise noted, all clients will accept changes. {Comments in braces {} were removed from the Letter of Intent sent to Laurel and the College of Arms. Names, devices, or badges in braces have been returned or pended; general comments or replies to commentary are also placed in braces. Thanks to AElfreda aet AEthelwealda, Mikhail of Lubelska, Rory mac Feidhlimidh, Aryanhwy merch Catmael, Athenais Bryennissa, Knut, Ettiene le Couteau des Roches, Kevin Ambrozijwski, Phebe Bonadeci, and Jaelle of Armida for their commentary this month.}
{This month, I have initiated the Great Midrealm Scanning Project. Not nearly as ambitious as the Laurel project, it is still my intent to digitize the files – all 14 drawers of them! Our project is slightly different than Laurel’s, as we are scanning all documents in rough alphabetical order and then filing them in accession # order, which is tracked through an Access Database. Thus, we are also assembling an authoritative database of every item in the files. This will allow us to better track down missing forms and cross reference joint badges. The project is also estimated right now to take about five years to complete, assuming that I do it all myself (which, thankfully, will not be the case!). At the end of the first month, we have digitized 70 files with a total of 490 sheets of paper.]
1) Cydrych Clutorix. New Name and Device. Per chevron azure and argent, three talbots statant two and one counterchanged.
Cydrich is found in Jones, “The First Thousand Years of British Names, Appendices IV and V” (http://www.sca.org/heraldry/laurel/names/british1000/appendix4_5.html). It is also found in Bartrum, Welsh Genealogies, AD 300-1400. Lastly it is dated to 1015 in “Gruffudd ap Cydrich” (http://www.mathematical.com/cydrychgruffudd1047.html). The second element is a given name extrapolated from burial records noted in Jones (in Appendix 3). From an inscription on a stone CLVTORIGI | FIL/IPA/VLINI | M/ARINILATIO translated as the burial place of Clutorix (PN) son of Paulinus (PN) Marinus (PN) of Latium. The client will NOT accept MAJOR changes, cares most about sound, and wishes his name to be authentic for Welsh language/culture.
Jones’s article suggests that this name should really be constructed with the second element in some sort of genitive form (e.g., “Clydrych filius Clutorigi”) but we would argue as well that it could be registered as an unmarked patronymic. The client does permit minor changes, so perhaps some sort of acceptable compromise can be found.
Name Commentary
Ettienne, et al: Name OK.
Ary: [Cydrych] is listed as the standard form of a name recorded as [Cidrich] or [Cydrich] in the Llandav charters, according to the article cited on the LoI.
The surname is actually recorded as [CLVTORIGI] (genitive) in the 5th century, according to Tangwystyl's article; [Clutorix] is her reconstruction of the nominative form.
Note that this combines two given names in the nominative, one Old Welsh, one Latin; such a construction is not appropriate for either language. At most, this should be changed to [Cydrych Clutorigi filius] or [Cydrych filius Clutorigi], following the patronymic constructions found in Appendix IV. However, since the client does not allow any changes, this needs to be returned.
Device Commentary
Rory: Consider "Per chevron azure and argent, two demiwolves rampant adorsed issuant form the line of division argent, and a dog stantant reguardant sable (D: Bran of SilverKeep, 7/97). A CD for changing the upper dogs to demiwolves. Another CD for the slight change of the lower dog's tincture & posture?
Knut: Two and one is the default for a primary group of three objects. This depiction appears to be a slight trian aspect which obscures the tails. I have more trouble with the lack of visible tails than the hint of trian aspect. I would also prefer to see some internal details but this appears to be identifiable.
Bran of Silver Keep - July of 1997 (via Atenveldt) Per chevron azure and argent, two demiwolves rampant addorsed issuant from the line of division argent, and a dog statant reguardant sable. CD type of half of primary group (rampant demiwolves vs tallbots), CD tincture of half of primary group (sable vs azure in the basemost charge in a group of three) Clear. Clear.
Ettienne, et al: Possible conflict with Angelique Thibudeau (Per chevron azure and argent, three deifs voided counterchanged).
Ary: "Two and one" is the default arrangement for three charges on a field; it came be removed from the blazon, e.g. "Per chevron azure and argent, three talbots statant counterchanged." Lovely arms.
2) Elena inghean Ronáin. New Name {and Device. Azure, a gryphon dormant and in dexter chief a crescent argent. }
Elena is dated to 1271 in Scott, “A List of Feminine Personal Names Found in Scottish Records. Part Two: Pre-1400 Names” (http://www.sca.org/heraldry/laurel/names/scottishfem.html). “Ronáin” is the genitive form of the Gaelic masculine name Ronan, according to Jones, “100 Most Popular Men’s Names in Early Medieval Ireland” (http://www.s-gabriel.org/names/tangwystyl/irish100/). The client cares most about sound and having a Scots name.
{The device is being returned for redrawing. The griffin as drawn is difficult to identify. There is a standing Laurel precedent on the subject: “The dormant posture should be used carefully, as it can all too easily render a beast unidentifiable. In this case, the wolf's head, paws and tail are neatly tucked in, making him indistinguishable from a meatloaf. This must be returned, per Rule VIII.3. (Vladimir Andreivich Aleksandrov, January, 1993, pg. 24).” To speak more directly to this particular case, the griffin resembles a “meatloaf” as well as the head is buried and the crouching position overall eliminates the most easily distinguishable characteristics of griffin.
In redrawing, the client should also be aware of the device of Maureen ha-Ivriah (reg 1/74): "Azure, an Assyrian griffin couchant, gazing to chief, wings displayed, argent" which is quite close in design. The client, in executing their redrawing will need to walk the fine line between making the design more identifiable without coming into conflict with this (or any other) registered device.}
Name Commentary
Athenais: The name looks fine.
Ettienne, et al: Name OK.
Ary: [Elena] is a Latin form of [Ellen] or [Helen], found in English and Scots contexts. It is wholly out of place in an otherwise Gaelic name, but it is registerable. I believe there is an Irish Gaelic adaptation of the name, but do not have OCM on hand at the moment. There is very little (if any) evidence for [Ronán] in Scotland; the client should be made aware that, as-is, there is no way that her name can be made authentic for Scots or Scottish Gaelic culture as it is.
Device Commentary
Aelfreda, et al.: Possible conflict with Maureen ha-Ivriah (reg 1/74): "Azure, an Assyrian griffin couchant, gazing to chief, wings displayed, argent." There is one CD for addition of the crescent.
Elsbeth's precedents say "... there is not a CD between dormant and couchant... [Caointiarn Comhthaistealaí, 09/00, R-Artemisia]"<,br>
Daud II says (coincidentally mentioning this exact possible conflict): "[Registering Per bend sable and vert, a griffin couchant argent.] Versus ... Azure, an Assyrian griffin couchant gazing to chief wings displayed argent, there is a CD for the change to the field, and Laurel precedent (LoAR of 17 June 1990, p. 1) grants another for posture in the difference between wings addorsed and wings displayed. [1/94, p.1]"
The question remains, is the position of the wings in the new submission sufficiently different from displayed? We are not sure.
Athenais: The gryphon is drawn a little oddly, even considering the dormant posture. I would have expected the wings to be folded down, rather than addorsed. Additionally, the paws covering a large part of the gryphon’s face make it harder to identify. No conflicts found. The dormant posture should be used carefully, as it can all too easily render a beast unidentifiable. In this case, the wolf's head, paws and tail are neatly tucked in, making him indistinguishable from a meatloaf. This must be returned, per Rule VIII.3. (Vladimir Andreivich Aleksandrov, January, 1993, pg. 24)
Knut: Azure, a winged meatball (a meatloaf would be stretched out more) wings inverted and addorsed and in dexter chief a crescent argent (The wings look a little more bent than extended to me)
[three mice dormant] This is a good example of identifiable dormant, since the mouse heads with their identifying ears are largely against the high contrast field, rather than the low contrast mouse bodies.
[Gwenddolynn ni hAilleachaín, 10/01, A-Merdies] Precedents - François under posture:
The dormant posture should be used carefully, as it can all too easily render a beast unidentifiable. In this case, the wolf's head, paws and tail are neatly tucked in, making him indistinguishable from a meatloaf. This must be returned, per Rule VIII.3. (Vladimir Andreivich Aleksandrov, January, 1993, pg. 24) Precedents - Bruce under identifiability
Pretty drawing. Unfortunately, the head, especially the beak, is obscured by a foreleg, the two foreclaws combine to give the impression of five digits on the splayed claw, not the avian four, and not enough of the forelimbs are showing to present the classic tuft of feathers characteristic of avian legs. These characteristics combine to leave this depiction with doubtful identifiability.
[Registering Per bend sable and vert, a griffin couchant argent.] Versus ... Azure, an Assyrian griffin couchant gazing to chief wings displayed argent, there is a CD for the change to the field, and Laurel
precedent (LoAR of 17 June 1990, p. 1) grants another for posture in the difference between wings addorsed and wings displayed. [1/94, p.1]
Maureen ha-Ivriah - January of 1974 Azure, an Assyrian griffin couchant, gazing to chief, wings displayed, argent. CD wing position, CD secondary, clear Return for redraw.
Ettienne, et al: Device OK.
Ary: The blazon can be simplified to "in canton." I'm not sure how identifiable the griffin is in this posture.
{*) Gillian of Bloodwood. New Name and Device. Argent, a chief rayonny sable, a fleece purpure.
The name is being returned because the byname could not be documented. In order to register this name, the client needs to show that the locative either exists as an actual place or that it is a plausible name, based upon similar examples in period.
The device is being returned with the name and might have been OK. However, the rayonny division should be redrawn on the resubmission so that the flames (up and down) are equal and the same width.}
Name Commentary
Aelfreda, et al.: We were unable to find the word "bloodwood" in period, but were able to find the phrase "red wood" (two words). From the OED 2nd edition, online version:
Bloodwood: 1724 in F. Moore Trav. Inner Afr. (1738) 267, I shall now describe the Pau de Sangue, or *Bloodwood, so call'd from a Red Gum which issues from it. 1880 SILVER Handbk. Australia 275 Blood-wood and turpentine both hard and durable.
Redwood: 1. a. Wood of a red colour, obtained from many different trees, chiefly of tropical regions; formerly applied esp. to such as were used for dyeing. 1619 W. PHILLIP tr. Schouten's Relation Wonderfull Voiage 37 In each Canoe..there lay two whole broad planckes of fayre redde wood. 1634 Copy Court Roll (Wakefield), One milne..used for the grinding of red wood. 1640 Jrnl. Ho. Comm. II. 33 The sole importing of the Red-wood.
Athenais: Withycombe states that the given name is “the popular English form of Julian(a); very common in the Middle Ages...”
The only mention of a surname beginning with “blood” or “blod” in R&W is Blood, dated to 1256 in the spelling Blod (header “Blood, p. 50). Under the same heading, it mentions Blodletere c1095, and Blodyr 1441, for a blood-letter. (That is, a letter of blood, or an early form of physician. Sort of.) These do not document the combination of “blood” with “wood” (or indeed, anything else). Gillian Blod seems to be the closest form of the submitted name that is documentable.
Ettienne, et al: Please have client find placename docs.
Ary: I couldn't find any evidence for [Blood-] as an appropriate element for an English placename.
Device Commentary
Athenais: The submitter might be told that rayonny is usually symmetrical, with waves going both ways. The fleece looks a little more alive than normal, but it is a fine drawing. The CoA doesn’t use French spellings in blazonry; this should be rayonny. It’s normal to blazon the primary charge first. Suggested reblazon: Argent, a fleece purpure and a chief rayonny sable. No conflicts found.
Knut: Argent, a fleece purpure and a chief rayonné sable. (primary charge group goes before every other group except strewn charges) The rays pointing up should be the same width as the rays pointing down.
[Quarterly sable and argent, a dragon passant Or impaled by a sword proper all within a laurel wreath Or.] ...the mostly argent sword is unidentifiable against the argent field. [Dragon’s Rest, Shire of,
08/99, R-Artemisia]
Precedents - Elsbeth under contrast: The argent face of the fleece can't lie on the argent field. Clear
Return for redraw.
Ettienne, et al: Looking at the device, one would be remiss to makecomments about BBQ lamb.
Ary: "Argent, a fleece purpure and a chief rayonny sable."
{*) Gillian of Bloodwood. New Badge. (Fieldless) A fleece purpure.
{Name submitted this LoI}
This is being returned because the name is being returned. Otherwise, it should be OK.}
Badge Commentary
Knut: Clear.
Ettienne, et al: Looking at the device, one would be remiss to makecomments about BBQ lamb.
{*) Gwen Wirion. New Device. Quarterly ermine and vert.
{Name reg’d 5/02}
This device was withdrawn by the submitter}
Device Commentary
Aelfreda, et al.: The arms of Brittany (SCA reg. 12/94) are "Ermine." From the Precedents of Alisoun MacCoul of Elphane: “Society tradition does not protect the ermine field of Brittany unless it appears in the context of quartering or attached to a name which is strongly redolent of Brittany. (LoAR 28 Feb 87, p. 2)" We suggest return for quartering with Brittany.
Rory: no conflict noted -- talk about your simple armory!
Athenais: The client’s name was registered 03/02 as Gwen Wirion. No conflicts found. Nice armoury!
Knut: Clear
Ettienne, et al: Amazingly enough, no conflict was found.
Ary: Do we know on what Meridien LoI this name was submitted on? Lovely arms!
{*) HallKell Surtr-thorn. New Name and Badge. Or, 11 piles, issuant from all around and conjoined at the nombril point purpure, a dragon’s head argent issuant from flames azure and Or.
The name is being returned for grammatical problems. The given name (spelled “Hall k ell” is probably OK, although it could be spelled without the spaces as “Hallkell” as found in Geirr Bassi). The byname is much more problematic. Not only do the elements not translate to the client’s desired meaning of “black thorn” but the use of that type of byname is not supported in period Norse. Only in the 18th century do we find names like Törnroos (“thorn rose”). At least one commentator suggested that Hallkell surtr would be a good name and perhaps the submitter will consider that as an alternative. Otherwise, the general advice was for the client to return to Geirr Bassi and pick an example actually found therein.
The badge is being returned with the name but also has stylistic problems that would have merited a return in their own right. The design violates the rule of period heraldry that the design be readily and easily identifiable (RfS VIII.3: “Elements must be used in a design so as to preserve their individual identifiability”). The field is not identifiable and overly complex, the flames are not depicted in a fashion that maintains their neutral nature, and the dragon’s head has been depicted in trian (“3-D”) aspect. While these problems could all be addressed with some simplification and redrawing, we would encourage some consideration of a redesign towards an emblazon that is bolder and clearer.}
Name Commentary
Athenais: The given name is found as Hallkell in Aryanhwy’s article. It is also found in Geirr Bassi, p. 11, col. 1. “Black thorn” doesn’t seem to follow the standard naming practices of Norse nicknames, which were usually very concrete in meaning and often insulting. They weren’t usually formed, as far as I can tell, by combining prothemes and given names at random, especially if the given name is of the opposite gender from the person using the nickname. Geirr Bassi lists surtr (a variant of svartr) as meaning “black,” and shows several compound names are formed from svartr, which is always at the beginning of the word. There is one nickname listed, {th}yrnif{o’}tr, that means “thorn-foot.” However, this would seem to indicate that {th}yrni, like svartr, is used at the beginning of compound names/words, so the two couldn’t be combined.
Ettienne, et al: Hallkell was found in Geri-Bassi p.11.Surtr-thorn not found in GB.
Ary: The given name is found as [Hall_k_ell], not [Hall_K_ell], in my article, and should be modified accordingly. While [surtr] is indeed listed in my article, meaning "black," [surtr-thorn] is not an appropriate construction; [thorn] is not a Norse word meaning [thorn], and contrary to what the LoI states, [{TH}orn] is not listed as a given name in the first article. A number of variants of [{TH}or-] are, but none with the [-n-]. This element should be dropped; [Hallkell surtr] is a fine Viking-era Old Norse name.
Badge Commentary
Aelfreda, et al.: The field is the problem. It cannot be blazoned as gyronny, since it has too many pieces.
From the precedents of Jaelle: "[registering Gyronny of sixteen gules and Or, a Celtic cross azure] The question was raised regarding whether gyronny of sixteen is period, and whether it can be used in the SCA. Papworth's Ordinary of British Armorials, cites an instance from the 12th century, and Martin Schrot's Wappenbuch, a German heraldic treatise shows a 16th century example... Given this, we will register Gyronny of sixteen in simple cases, but nothing more, barring period evidence. (Padric O Mullan, 6/99 p. 2)"
If it is blazoned as 11 piles, there is a different problem. The flame is not azure and Or. It is "a flame azure charged with a flame Or." Since this is an overall charge, the device has four layers: field, piles, dragon + azure flame, Or flame. We suggest return for excessive complexity.
Rory: as Escutcheon notes, this badge is VERY difficult to blazon, and runs afoul of Armorial Identifiability as well as Armorial Balance. It is not really gyronny debased, it is not really piley, and even Escutcheon's attempted blazon doesn't really do the drawing justice.
Athenais: As drawn, the badge is basically unblazonable. I would suggest returning it for a redraw with a standard field division. The flames are also not drawn as standard flames with tongues of alternating colours, but as on a flame, a flame, which hasn’t been allowed for some time. The conclusion reached from this research is that to be truly proper, flames should be effectively a neutral charge, approximately half Or and half gules, and should generally take one of the forms as exemplified in Figs. 1, 3 or 4 above, with the "tongues" of flame being alternately Or and gules (or gules and Or). The practice in the SCA of making flames red on the outside and yellow in the center (or vice versa) appears to be based on incorrect assumptions and should be discontinued. (CL 4/95)
Knut: Gyronny of twenty-two from the nombril point Or and purpure, a dragon’s head argent issuant from a flame azure charged with a piece of lichen Or.
There are multiple problems with this submission.
[a phoenix argent rising from flames proper] The flames are not proper (alternating tongues of Or and gules), but are rather "On a flame Or another gules." This form cannot be blazoned as part of a phoenix, and therefore must be returned for a redraw. [Magnús Slembidjákn, 09/00, R-Artemisia]
Precedents - Elsbeth under Flames and Fire: Though blazoned as "enflamed argent and azure", the flames were drawn on the large emblazon as "azure, fimbriated argent". We have disallowed fimbriated flames for quite some time. [12a/93, p.15]
Precedents - Da'ud 2.1 under Fire and flames: The motif of a flame with a core of one tincture surrounded by another tincture has been banned for many years. One of the main reasons it the
potential unidentifiability of the central part of the charge, as is obvious in this case.
[Gyronny of sixteen sable and argent, a salamander statant reguardant gules enflamed Or] Gyronny of sixteen can only be used in some devices, per the following precedent: The question was raised regarding whether gyronny of sixteen is period, and whether it can be used in the SCA. Papworth's Ordinary of British Armorials, cites an instance from the 12th century, and Martin Schrot's Wappenbuch, a German heraldic treatise shows a 16th century example... Given this, we will register Gyronny of sixteen in simple cases, but nothing more, barring period evidence. (Padric O Mullan, 6/99 p. 2)
Precedents - Elsbeth under Field division – Gyronny: In Society heraldry, while fields may be gyronny of as many as 12, charges may be gyronny of no more than 8. (LoAR of 22 March 83)
(Katrine Vanora of Maidstone, October, 1992, pg. 26)
Precedents - Bruce under Field division – Gyronny: Likewise, the gyronny of more than sixteen parts has been banned for many years.
Finally, if the color version that I saw is anything close to reality, the shades of azure and purpure used here are far too close to each other to maintain identifiability between them.
The motif of a gyronny issuant from a point other than the center of the device has been registered many times without comment, most recently in July of 1999: Cwenhild of Cydllan Downs - July of 1999 (via Atlantia) Gyronny raguly of four issuant from dexter chief ermine and vert.
Gyronny issuant from the nombril point Or and purpure, a dragon’s head argent issuant from upon a flame azure looks clear. (A partially Or flame can't be placed on a partially Or field.)
Return for multiple problems.
Ettienne, et al: Badge looks like a dojo patch.
Ary: This is unblazonable and unmedieval in style. This needs to be returned for violating RfS VIII.3 armorial identifiability, "Elements must be used in a design so as to preserve their individual identifiability." The field is not identifiable, and proves again the rule of thumb - if it's not blazonable, it's probably not medieval.
3) Hroar Njalsson. New Name and Device. Or a pitcher vert, a bordure gules.
Hroarr is found in Geirr Bassi (11) but we find multiple cases in Lind, Norsk-Isländska Personbinamn where the double –rr was reduced to a single –r, so the client’s spelling seems plausible. The client constructed the byname from Njal, as in Njal’s Saga and Njáll is found in Geirr Bassi. Njall is an anglicisation and Lind (268) has Niall and Nials son, suggesting that Hroar Nialson might be a better name, but the client’s submitted form seems registerable and the client did not request an authentic name, so we are proposing registering it as submitted.
Name Commentary
Athenais: Hroarr is found in Geirr Bassi, p. 11, col. 2. Njall is found on p. 13, col. 2, and Njalsson is formed according to the patronymic examples on p. 17. Hroarr Njalsson seems like a perfectly good Norse name, although I’m uncertain if dropping an “r” is common to Norse practices. Does the submitter’s copious documentation show proof that Hroar is a period spelling?
Ettienne, et al: Name OK.
Ary: The elements are found in Geirr Bassi as Device Commentary
Aelfreda, et al.: The baluster is in the default position, spout to dexter. Please remove the word "reversed" from the blazon.
GLOSSARY OF TERMS As Used By The College of Arms of the Society for Creative Anachronism, Inc.
Table 4: Conventional S.C.A. Default Postures
Pitcher Palewise, spout to dexter
Rory: blazon is in error, the baluster is not reversed. According to the PicDict, Pitcher, it's spout is to dexter by default (see diagram #570).
Athenais: I don’t see any real problem with the device, although the baluster certainly looks remarkably like a standard pitcher. According to the PicDic, s.n. PITCHER, the spout is to dexter by default, which means that the handle would be to sinister. It’s probably safe to drop the reversed from the blazon, as it doesn’t seem to be reversed by SCA standards.
Knut: Or, an ewer vert within a bordure gules
"The handle (fr. corniere) should be sinister, and the lip dexter." (Parker 244, s.v. ewer) [BoE, 25 Aug 85, p.11]
Precedents - Baldwin under Pitcher: The handle is sinister and the lip is dexter, which is the default, not reversed.
Does any of what he submitted document the term baluster? Baluster does not appear anywhere in the current SCA ordinary and it's use in pottery is not supported in either the OED or EBrit. Ettienne, et al:I can not tell the difference between a baluster and a water pitcher, so why not say water pitcher.
Ary: There was never any question that jugs, such as amphorae, were appropriate heraldic charges; the question was whether _balusters_ were appropriate. I do not see any evidence presented here to answer it. However, I also don't see anything in the emblazon that is particularly baluster-esque, and this could probably be reblazoned as 'jug' and sent on.
4) Ivan Kuzmich. New Name.
Ivan is first found in 1181, according to Wickenden (120). Kuzmich is first found in 1594, according to ibid (179). The client will NOT permit MINOR changes.
At least two internal commentators noted that the gap between the dates of the given name and the patronymic might lead the College to consider the name “temporally incompatible.” I must admit that my initial response to that possibility was to laugh it off as pedantic stupidity (not only is Ivan found in the 16th century, but it is the most common name of the period!), but perhaps I suffer from the nearsightedness of an expert. At least three points are in order:
1) My Dictionary (like Withycombe and several of our other sources) only lists the oldest available date. The implication is that the name was used from the supplied date onwards (i.e., Ivan is found as early as 1181 and regularly thereafter). The Dictionary was certainly never designed for or intended for ruling on temporal compatibility.
2) We know almost nothing about temporal compatibility in Russian onomastics. There is nothing published by professionals in the field. Thus, we are not really in a position to be confidently returning names (or ruling weirdnesses) because of it.
3) What we do know about Slavic onomastics suggests that naming conventions were particularly static. After the introduction of Christianity (and the subsequent fading out of non-Christian names), there are few major changes until the time of Peter the Great. There are a few patterns and trends, but no indication that a particular grammar or set of names was ruled out entirely in any particular region or time period.
We may have reached a level of knowledge where we can comfortably say that an English name has to have elements that are within X years of each other, but we are not at this point (either to consider temporal compatibility or to set a date range) for Russian and other Slavic languages. And I strongly believe that, if we ever do have this knowledge, we will discover that our rules for Western Europe don’t apply for the Eastern end (for any number of reasons including the Tatar Yoke’s isolation, the conservative nature of Orthodoxy, etc.).
Name Commentary
Athenais: Both names are found in _A Dictionary of Period Russian Names_, 2nd ed. (http://www.sca.org/heraldry/paul/), by Paul Goldschmidt.
_Ivan_ is a variant of _Ioann_, which is "the Russianization of John (God is Gracious) and one of the most common given names. Both the older form (Ioann) and the newer (Ivan) are common in period." _Ivan_ is dated to 1181-2 (Ivan Fominsyn, governor).
_Kuzmich_ is listed as a patronymic variant from _Kuzma- and dated to 1594 (Iurko Kuzmich Rogtinets, craftsman).
The name looks good as is.
Ary: [Ivan] is dated to 1181-2 in Paul's dictionary. [Kuzma] is dated to 1463-5 s.n. Kren', 15th C s.n. Kukhtyr', and 12th-13th C s.n. Kuz'ma. The patronymic [Kuzmich] is found s.n. same dated to 1594. This gives quite a bit of temporal discontinuity - however, [Ivan] is probably appropriate through the 16th century, since it is still in use. Paul, can you maybe get a later date for the given name? Otherwise it will be returned for temporal incompability.
5)Lisette de la Lavande Shelbyew Name and Device. Argent, a six-headed wyvern sejant, in chief three whelk shells purpure.
Lisette is dated to 1528 in Scott, “Late Period Feminine Names from the South of France” (http://www.sca.org/heraldry/laurel/names/latefrenchfem.html). For this portion of her name the client cares most about period and place.
De la Lavande is meant to indicate an occupation of gathering and/or selling lavender. The word “lavande” (lavender) is dated to 1383 in Rey, Le Grand Robert de la Langue Française. The client submitted the name as “dela Lavanda” (an Italian form) because of her assuption that, due to the location, an earlier Italian form would be used rather than the later French form (her source indicates that the word lavande is derived from the Italian lavanda). For this element she would very much like to retain the meaning, but if no version of “Lavender” is deemed suitable will reluctantly accept “lavendier” (washerwoman). La lavendière is found in the 1292 Census of Paris (http://www.sca.org/heraldry/laurel/names/paris.html )
Shelby is a constructed English place name with elements drawn from Ekwall (4th edition). “Shel-” is found in a number of cases (Sheldon, Shelwick, etc.) and “-by” in many more (Scotby, Lamonby, etc.). The client cares most about sound on this element.
The client stated an interest in having a period late 16th century Provençal/English name, but her documentation supports more of a French/English name and that is how we believe it should be registered (mostly to avoid the weirdness of having three languages in a name).
Name Commentary
Athenais: As documented, the name contains three languages and is probably returnable for two weirdnesses: one for mixing French and Italian, and one for mixing English and Italian, according to the Lingual Weirdness chart found with Fran{c,}ois’ Draft Precedents at (http://home.earthlink.net/~mranc/sca/). If the French form of the occupational byname is used, it would reduce this to only one weirdness and thus be registerable. (A persona story is not documentation.)
Ettienne, et al: We had slight problems with the name construction. The townspeople of Shelby wouldn't call her "Shelby." They would consider her from France.
Ary: The preposition [dela] 'of the' is not appropriate in an occupational byname. My sources for Provencal surnames are fairly limited, and I cannot give any additional support for "lavender-seller" as an appropriate Provencal form. The masculine form of the client's alternate byname, [le lavendier], is found in the 1292 census of Paris; Device Commentary
Aelfreda, et al.: We are unsure if this conflicts with the Heralds' Seal for Triton Herald (reg 8/79): :(Tinctureless) A triton-shell trumpet bell in chief." There is one CD for tincturelessness. We could not find a picture of Triton's seal, so we could not tell if these two are visually different.
Athenais: The “hydra” looks more like a six-headed wyvern, since it has only two legs. As the definition of a hydra, according to the PicDic (s.n. DRAGON), is “a multi-headed dragon,” this is probably an acceptable variant, but should be blazoned explicitly in order to reproduce the drawing. The fact that the hydra is sejant should also be mentioned. It’s normal to spell out numbers in blazon, rather than use numerals. Suggested reblazon: Argent, a six-headed wyvern sejant, in chief three whelk shells purpure. No conflicts found.
Knut: Clear.
Ettienne, et al: Device is OK.
6) Lisette de la Lavande Shelby. New Badge. Argent a whelk shell purpure.
{Name submitted on this LoI}
Badge Commentary
Knut: Clear.
Ettienne, et al: Argent a whelk shell purpure. There is a possible conflict with a Kingdom of Atlantia badge ((Fieldless)a whelk shell palewise argent).
7) Nicholas Winterscale. New Name. {and Device. Per chevron paly sable and argent and azure, a cross formy argent.}
Nicholas is found in Scott, “Late Sixteenth Century English Given Names” (http://www.sca.org/heraldry/laurel/names/eng16/eng16.html). Winterscale is found in parish records of Egglecliff and dated to 1578 (http://www.cs.ncl.av.uk/genuki/Transcriptions/DUR/EGG.html ). {The device is being returned for conflict with the Order of Dannebrog (Important non-SCA Badge, reg’d 11/98) (A cross formy argent fimbriated gules). There is a single difference for changing the field but none for the removal of the fimbriation. There is an additional conflict with Seth Williamson of Exeter (reg’d 5/97) (Lozengy purpure and Or, a cross fitchy argent). Again, there is one difference for the change of the field, but none for the change from a cross formy fitchy to a cross formy. There are a number of ways that the client could clear these conflicts.}
Name Commentary
Athenais: Nice name! Hopefully photocopies of the documentation for Winterscale are included in the submission packet, as I was unable to get the linked site to come up.
Ettienne, et al: Name OK
Device Commentary
Aelfreda, et al.: The cross shares its tincture with part of the upper section of the field, therefore its placement on the azure portion is a forced move. We find possible conflict with Dannebrog, Order of (SCA reg 11/98) "(Fieldless) A cross formy argent fimbriated gules." and with Seth Williamson of Exeter (reg 5/97) "Lozengy purpure and Or, a cross formy fitchy argent."
In both cases, there is one CD for changing the field. We are unsure if fimbriation is sufficent for a second CD (first item), and if "formy" is sufficiently different from "formy fitchy" for a second CD. (second item)
Athenais: It’s not really necessary to specify the number of “paly”, and the cross isn’t all that formy. The blazon as given is a little confusing; I would put the per chevron field division first. Suggested reblazon: Per chevron paly sable and argent and azure, a cross formy argent. Unfortunately, since the cross has to be on the lower half of the field, it conflicts with the important nonSCA badge of the Order of Dannebrog (reg. 11/98 via Laurel), (Fieldless) A cross formy argent fimbriated gules. There’s one CD for the field, but nothing for the position of the cross or the fimbriation.
There is not a CD for fimbriation ... [Fiona ingen ui Fhaolain, 07/00, RÆthelmearc]
... we do not give a CD for position [of the primary charge] when one of the pieces of armory is fieldless... [Brandric of Rhydderich Hael, 10/99, RÆthelmearc]
(Note that there couldn’t be a CD for position of the cross anyway, since the cross is forced to base by the field.)
Knut: Per chevron paly of six sable and argent and azure, a cross formy argent. (The entire shield is divided per chevron, therefore that goes first. The top part, the paly, goes next, followed by the azure. The argent cross is doesn't need to be specified as in base because it can't lie on the partially argent top part and is therefore forced from the center to the base.)
RfS X.g - Arrangement Changes - Changing the relative positions of charges in any group placed directly on the field or overall is one clear difference, provided that change is not caused by other changes
to the design.
There is not a CD for fimbriation ... [Fiona ingen ui Fhaolain, 07/00,R-Æthelmearc]
Precedents - Elsbeth under Fimbriation and Voiding: Dannebrog, Order of - November of 1998 (via Laurel): (Fieldless) A cross formy argent fimbriated gules.
CD fieldless, No CD for fimbriation or location on shield (by either forced move or lack of position for fieldless armory) - Conflict.
... there is not a CD between a cross crosslet fitchy and a cross bottony. [Gertraud von Wuerzburg, 12/99, R-Caid]
Precedents - Elsbeth under Crosses: Seth Williamson of Exeter - May of 1997 (via Atenveldt): Ettienne, et al: Device OK.Please have client draw chevron closer to base.
Ary: This is "Per chevron paly of six sable and argent, and azure, a cross formy argent." (And quite lovely, I might add).
8) Nonna the Midwife. New Name. {and Device. Per bend sinister vert and azure, in bend sinister a trident argent between two golden carp proper embowed in annulo.}
Nonna is documented from a Christian saint who died in 374 (http://user.erols.com/saintpat/ss/0805.htm).
The byname can be documented in two ways. First of all, the word itself is found in the OED: “Midwife: 1. A woman who assists other women in childbirth, a female accoucheur. 1592 SHAKES. Rom. & Jul. I. iv. 54, I see Queene Mab hath beene with you: She is the Fairies Midwife. 1615 CROOKE Body of Man 269 Adde hereto the skilfull hand of the heads-woman or Midwife as we cal them.” Secondy, there is a dated reference for the byname itself: Johanna Mydwyff is dated to 1381 in a poll tax, according to The Poll Taxes of 1377, 1379 and 1381. Part 1, Bedfordshire - Leicestershire (284).
{The device is being returned for redrawing. The late dating of Golden Carp bothered several members of the College who noted that we “originally” only registered heraldry that could be dated pre-1485 (!) and that our current rules instruct us to avoid post-1600 heraldry. The client’s own documentation notes that “There are no ancient instances of this fish in English heraldry.” Given that the Golden Carp was not even introduced until our grey area, it is extremely unlikely that it was used in heraldry before it.
There are also artistic problems with this device. First of all, the carp (colored as orange) are too dark to be clearly visible against the field. They should be colored as a lighter tincture (gold or silver) and then blazoned as such. The positioning of the fish is also problematic but might be seen only as a weirdness (and thus registerable), so we’ll let it slide as the client points out that the fish sideways might not be identifiable at all. However, the proper coloration combined with the unusual posture are two weirdnesses and cause for return. The trident needs to be redrawn so that its bottom handle does not quite reach the edge of the shield. None of these problems on their own would be cause for return, but combined together (and, with the questionable registerability of the Golden Carp in the first place, they represent too much to register.}
Name Commentary
Aelfreda, et al.: OED 2nd edition, online version: Athenais: The name looks registerable.
Knut: Names from the grey area are permissible for use when there is a strong likelihood that they could have first been used prior to 1600, but were not recorded until afterwards (though prior to 1650). In the case of the Society of Friends it is well know when they came into existence, so it is not a period model. (Christall Gordon, 3/99 p. 12)
Precedents - Jaelle under Name - Documentation & Documentable: If 1611 was the date of the definite introduction to, and not merely the first recorded appearance in, Europe, then this is not an
acceptable armorial elemment. Please tell the submitter that western Europe isn't the entire scope of the SCA. A date in Byzantium before 1601 is perfectly acceptable. Also, don't bring up "the old days" in
conjunction with armory cut-off dates. In the old days of the SCA the cut-off date for armorial elements was 1485.
Ettienne, et al: With this device, she should be Nonna the Fishwife.
Ary: The documentation submitted for the byname is not sufficient, and for awhile I wasn't sure I was going to be able to help, as the last time S. Gabriel researched this byname, we came up dry. However, Talan Gwynek on chance found a reference to a [Johanna Mydwyff] in a poll tax from 1381. The full
citation is Carolyn C. Fenwick, ed. The Poll Taxes of 1377, 1379 and 1381. Part 1, Bedfordshire - Leicestershire (Oxford: Oxford University Press, 1998); p. 284. It would be nice to see more solid docs for the given name, but given the saintly reference, it's probably registerable.
Device Commentary
Rory: a "golden carp proper" is much better and easier to understand than a "koi proper" Without digging into dictionaries, I would have no idea what a "koi" was. As there seems to be no reason to keep the "koi" for canting purposes, the change is very good.
As far as the claim "As the SCA originally covered through 1650, this time frame is allowed" is concerned - nonsense. That's like saying "Since the College of Arms used to register Elvish names, registering this one is allowed". The SCA covers pre-17th Century Western Culture (Bylaws, III. Objectives and Purposes), which cuts off at 1600, not 1650. According to RfS VII.4, Compatible Armorial Content/Period Flora and Fauna says "Flora and Fauna that were known in the period and domain of the Society may be registered in armory. Hybrids or mutations of period forms known to have been developed after 1600 generally may no be used as charges. For example, the English Sheepdog may not be used in Society armory because it was developed after 1600." By the client's own documentation, the golden carp were not introduced until 1611.
HOWEVER, the college also acknowledges a "grey area' for the purposes of documenting names and armory. "Anything that can be documented as late as 1650 may be considered acceptable, even though the official cut-off date of the SCA's domain as defined in Corpora is 1600....Grey area documentation should only be used as a last resort." (Glossary of Terms, p. 3).
Please understand that I have no problems with this submission; I just wished to point out a fallacy in the documentation.
(Very Minor structural note: Flip-flop submissions #12 & 11 - the client's name & device, even though a resubmission, should go before her badge & household name, since it's the registration of the badge/house depends on registering a primary name for it to go with.)
Athenais: The device has some problems. It resembles nothing so much as a piece of Japanese kimono fabric or wallpaper. I have no idea what a “koi proper” would look like–I’ve seen a lot of koi, and no two of them have looked alike. “Golden carp proper” might just be registerable, even if they are orange fish, but why not just make them Or? They’re Japanese goldfish, after all. The golden carp mentioned in the ILoI were not introduced to Europe during our period, but during the grey period–our cutoff date is 1600. (The SCA didn’t originally cover through 1650, as the ILoI states, at least for heraldry–the original cutoff date was 1485.)
No matter what the “natural” viewpoint of fish is, one must remember that heraldry is not art, and heraldry is not naturalistic. The carp are “tergiant in annulo,” and I’m not certain that tergiant is a registerable position for fish, as it severely limits their identifiability. The trident isn’t quite just bendwise sinister, since the handle ends at the end of the shield, nor is it quite throughout, since the forked points don’t end at the edge of the shield. Overall, I’d say that this should be returned for some serious redrawing.
Knut: Per bend sinister vert and azure, in bend sinister throughout a trident argent between two fish embowed in annulo tenne marked argent.
As to the various species of fish allegedly displayed tergiant, all are shown in a lateral view, just ask any icthyologist. Lobsters, crabs and clams are not fish, and do not have any bearing on fish postures.
RfS VIII.4. c Natural Depiction -- Excessively naturalistic use of otherwise acceptable charges may not be registered. Excessively natural designs include those that depict animate objects in unheraldic postures, use several charges in their natural forms when heraldic equivalents exist, or overuse proper. Proper is allowed for natural flora and fauna when there is a widely understood default coloration for the charge so specified. It is not allowed if many people would have to look up the correct coloration, or if the Linnaean genus and species (or some other elaborate description) would be required to get it right. An elephant, a brown bear, or a tree could each be proper; a female American kestrel, a garden rose, or an Arctic fox in winter phase, could not.
As to the claim of a more "natural" view of the fish, this is heraldry not art or nature. Overly natural dispiay is cause for return.
The carp, being a fairly ordinary looking fish, should be normally be shown in a lateral view to display the facial profile and the full set of fins for maximun identifiability.
There are only two SCA registrations of tergiant fish, one of which, a ray, is far more identifiable tergiant than in a lateral view.
I repeat my suggestion that a tergiant fish is one step from period practice, and therefore a weirdness. [a carrot proper] The carrot in this submission was drawn so that it was predominantly orange. No evidence has been presented that a period heraldic carrot proper would be of any particular color. Period carrots could be white, red, or various shades of yellow in period. The shades of yellow might include the color we now call "orange", but that is not clear from the evidence which has so far been presented. Regardless of the botanical propriety of a period orange carrot, there is no one obvious color for a carrot to take in period, and therefore there is no default tincture for a carrot proper. This carrot cannot be explicitly
blazoned with a heraldic tincture, because orange is not an acceptable color for use in heraldry unless it is used appropriately with a proper charge. Therefore, this must be returned. [Randall Carrick, 10/01, R-Outlands] Precedents - François under proper
Is this coloring the widely understood default for golden carp?
Since this is the direct ancestor of the modern goldfish, goldfish proper might be better. I recall seeing a case where Laurel substituted a modern name for a species when it was far better known
than the period name. Ary: This resubmission does not address all of the problems of the original submission, including that of the use of a non-ordinary essentially as an ordinary. Also, if the large emblazon is colored at all like the mini on the website, this is color (gules) on color (vert and azure).
Ettienne, et al:Device OK
9) Nonna the Midwife for House Njalsson. New Household Name {and Badge. Or, a pitcher reversed vert, on a bordure gules the words “Sporcus labor sed alicui faciendus est” sable.}
{Name submitted on this LoI}
T he client constructed the byname from Njal, as in Njal’s Saga and Njáll is found in Geirr Bassi (13). Njall is an anglicisation and Lind (268) has Niall and Nials son, suggesting that Nialson might be a better name, but the client’s submitted form seems registerable and the client did not request an authentic name, so we are proposing registering it as submitted. The name follows a common practice of “House X” (e.g., House of Anjou).
{The badge is being returned for tincture violation. The sable letters of the motto do not have sufficient contrast with the gules bordure.}
Name Commentary
Athenais: This probably should have come after #12, Nonna the Midwife, since the AH (II.B.e) states “When a household name is registered by an individual, records dealing with the group's name and badge[s] will be retained under the Primary Society Name of the individual registering the item.”
The household name is fine. Njalsson is also documentable from Geirr Bassi, and is the standard patronymic formation from Njall.
Ettienne, et al: Name OK
Ary: This does not follow any of the period models for household names enumerated in RfS III.2.b.iv Household Names: "Household names must follow the patterns of period names of organized groups of people. Possible models include Scottish clans (Clan Stewart), ruling dynasties (House of Anjou), professional guilds (Bakers Guild of Augsburg , Worshipful Company of Coopers), military units (The White Company), and inns (House of the White Hart)." This should have been listed _after_ her name resubmission on the LoI.
Badge Commentary
Rory: while this IS a baluster reversed (unlike submission #7 above), the sable motto on the gules bordure fails the good contrast requirement (RfS VIII.2 Armorial Contrast).
Athenais: It’s worth noting that this badge is only one CD away from the submitted device of Hroar Njallson, and no letter of permission to conflict is mentioned in the ILoI. If the household name and/or badge is to be jointly owned between Nonna the Midwife and Hroar Njallson, that also needs to be mentioned.
I don’t see any real problem with the badge, although the baluster certainly looks remarkably like a standard pitcher. According to the PicDic, s.n. PITCHER, the spout is to dexter by default, which means that the handle would be to sinister. It’s probably safe to drop the reversed from the blazon, as it doesn’t seem to be reversed by SCA standards. The blazon would also be a little clearer as either ...on a bordure gules the words... or ...a bordure gules charged with the words...
Knut: Or, an ewer reversed vert,on a bordure gules the words Sporcus labor sed alicui faciendus est, sable.
Sable words on gules bordure - tincture violation
Or, an ewer reversed vert, a bordure gules with any legal tertiary group is clear.
Return for reworking.
Ettienne, et al: Badge OK, except for previous comments under #7.
{*) Phineas Quinn. Change of Registered Name and New Device. Azure, semy of estoiles argent.
Withdrawn by submitter.}
Name Commentary
Athenais: It’s helpful to give both page numbers and header names, as well as editions, when citing from books. For instance, Phineas is found in my copy of Withycombe, 1st ed., on p. 234, under “Phin(h)eas.”
The name should be registerable as is, and Quinn is certainly a reasonable variant of the name, since Quine and Quinne are dated to 1275, and Quin is dated to 1394. (R&W, p. 368, header “Quinn.”)
Ettienne, et al: We were unsure how common "Phineas" is and would like supporting docs. Withycombe does not have dates.
Device Commentary
Knut: Azure estoilly argent
Winter's Gate, Barony of - November of 1980 (via the West): Per fess indented sable, estoilly argent, and argent. CD field. Since estoilly argent can't be on argent, the in chief arrangement is forced and not worth a CD - conflict
Cadhla Morag nicChlurain of Tregdin - November of 1975: Azure, within six estoiles in annulo argent, an estoile sable fimbriated argent. CD arrangement, no CD for tincture of only one of seven charges. Possible CD if the central estoille is actually voided instead of fimbriated. (Addition of tertiary group.) - Probable conflict. Ary: Amazingly enough, this fabulous device appears conflict free.
Ettienne, et al: The device, Azure, semy of estoiles argent conflicts with Barony of Nordskogen Azure, a semy of snowflakes argent in canton a laurel wreath, Or.
10) Ryan Murdoch Mackenzie. Change of Registered Name.
The client’s current name (Ryan of Grey Gargoyles) was registered on 4/02. Ryan is the client’s given name (a copy of his driver’s license is attached). Murdoch is a header spelling in Reaney and Wilson (317). Black (620) notes that one of the meanings of the byname is “belonging to the sea” and has several variant spellings dated to 1425 including Mordac, Mordoc, and Moreduc. Mackenzie is also a header spelling in Reaney and Wilson (292). Several variant spellings are found in Black (525) in the 15th century (MacEnzie, Makcanze, etc.).
Name Commentary
Rory: Murdoch & Machenzie are listed in Reaney & Wilson.....are there any DATES listed with those names? Just checking, since my copy of R&W has been loaned out & I couldn't check to see if the names were within period.
Athenais: The client’s name might have been on a November LoI, but according to the Laurel calendar, it was considered a December letter due to the postmark. The name was registered 04/02 as Ryan of Grey Gargoyles, along with his device, Quarterly Or and azure, in bend two lions rampant gules.
The ILoI is a little misleading in the documentation for this name. “Murdoch” is the header spelling found on p. 317 of R&W, but it is not dated to period. The listing gives Murdoc dated to 1066 and says about the name in general, “Introduced into Yorkshire before the Conquest by Norwegians from Ireland.”
“Mackenzie” is the header spelling found on p. 292, but is also not dated to period. The closest dated spelling is M’Kenze 1473.
The use of two surnames is probably a weirdness, but the name should be registerable.
Ary: His name and device were accepted by Laurel in 04/02. This name currently has problems in that
it has two patronymic surnames. Reaney & Wlson s.n. Murdoch say it is an anglicization of Old Irish [Muireadhach], Old Welsh [Mordoc], Middle Gaelic [Muireadhaigh] and Gaelic [Murdoch]. It was introduced into Yorkshire before the Conquest by the Norwegians from Ireland. The specific English form [Murdoch] is not dated, but [Murdac] is dated to 1130.
[Mackenzie] is also an ENglish form of a Gaelic patronym. R&W s.n. MacKenzie give its origins as the Gaelic "son of Coinneach", and the dated forms are [Makkyneth] 1264 and [M'Kenze] 1473. I'm sure Black probably has more dated forms, but Black is at my house and I am not.
Either [Ryan Murdac] or [Ryan M'Kenze] is acceptable, but not both surnames.
Ettienne, et al: We TOLD him to wait to submit his name & now he has to spend another $8 to change his name.
{*) Sabine du Coeurgris. New Name and Device. Gules, a bean plant argent between four pheons Or.
The name is being returned because the byname has not been sufficiently documented. While both elements (coeur and gris) are both documentable, the pattern of combining them is not. Couerjoly appears to mean either “heart soup” or “meek heart” according to the Dauzat cite (147, cp “Corhumel”), neither of which supports the use of “heart” + “gray” (or any other color) in a byname. In order to register this name, the client will want to find a byname whose pattern demonstrates the concept of The device is being returned with the name. There were no other problems with it. When the client resubmits, she will want to include the documentation for the beans again.}
Name Commentary
Athenais: Sabine is dated to 1279 in Talan’s article, cited in the ILoI.
What does “joly” mean? (My translation program doesn’t have the word.) “Coeur” means “heart,” so Coeurjoly is presumably (something)-heart. I’m not sure how reasonable Coeurgris is, though, since “gris” means “grey.” The only possible things I can think of “Greyheart” meaning are sickly, pale, or cowardly.
Ary: [Sabine] is dated to 1279 in the cited source. What does [gris] mean? Without knowing this, it's difficult to tell if the construction is appropriate. My guess is that no preposition or article would be appropriate, e.g., [Arval Benicoeur].
Ettienne, et al: Name OK.
Device Commentary
Rory: No conflicts were found. In fact, we could not find another registration of "bean plant" in the O&A. Will this be the defining pictorial depiction of the charge?
Athenais: The beanplant is similar to the crequier in its stylization. As long as the proper documentation is forwarded to Laurel, this should be fine.
Knut: Clear
Ary: The pheons are "two and two." The bean plant is not identifiable as such.
Ettienne, et al: Device OK.
11) Thomas de Keth. New Name and Device. Per bend argent and azure, an elephant statant contourny Or atop its back a tower sable.
Thomas is dated to the mid-13th century in Black (768) as Thomas Cites Thomas filius Maldoueny. De Keth is found in ibid (388, under Keith) and dated to 1185. If the name must be changed, the client has a speech problem and must be able to pronounce the name.
Name Commentary
Athenais: Nice name. I can sympathize with the client’s speech problem (I had one for quite a while as a child), but it’s difficult to know exactly what changes would be acceptable to him, if necessary, without knowing the particular type of problem. (No “s”s? No “sh”s? No “r”s?) With the documentation given, however, the name should be fine as is.
Ary: Lovely name.
Ettienne, et al: Name OK.
Device Commentary
Athenais: The elephant is either statant contourny or statant to sinister. No conflicts found.
Knut: Per bend, argent and azure, an elephant statant sinister Or sustaining on its back a tower sable.
or
Per bend, argent and azure, a tower sable issuant from the back of an elephant statant sinister Or.
The primary criterion for determining whether a charge proper has sufficient contrast is the visibility of the portion of the charge which identifies it. (LoAR 23 Apr 88, p. 18) Precedents - Alisoun under contrast
The elephant's Or head with the identifying trunk is on the argent part of the field.
Clear on any legal field.Per fess, per pale and per bend sinister all would work. He picked the only line of division orientation of argent and azure that wouldn't.
Return for violating RfS VIII.3 - Armorial Identifiability.
Ettienne, et al: There is a badge registered in the West that is an elephant with a tower proper on itsback, but it should clear.
12) Vilk{u,} Urvas, Shire of. New Device.
Azure, an armored wolf statant tail ululant contourny argent, in dexter chief a bezant charged with a laurel wreath azure, a chief embattled Or.
{Name reg’d 4/02}
A petition of support is enclosed.
{This item was pended in June for a lack of a petition. The petition has been supplied.}
Paul W Goldschmidt
Lacking applicable documentation, this must be reblazoned as an ewer.
I can't see enough color in the color image to call the ewer vert.
Or, an ewer vert within a bordure gules looks Clear.
The client cares most about sound and would like to have an authentic Elizabethan English name.
Lozengy purpure and Or, a cross formy fitchy argent. CD field, No CD for forced move or fitching - Conflict
Return for multiple conflicts.
Midwife: 1. A woman who assists other women in childbirth, a female accoucheur. 1592 SHAKES. Rom. & Jul. I. iv. 54, I see Queene Mab hath beene with you: She is the Fairies Midwife. 1615 CROOKE Body of Man 269 Adde hereto the skilfull hand of the heads-woman or Midwife as we cal them.
Clear. Return for documentation of date in Europe or middle east and possibly color.
Return for multiple conflicts.
Done by my hand this 19th day of August,
Paul Wickenden of Thanet, Rouge Scarpe
3071 Cimarron Trail
Madison WI 53719
goldschp@mailbag.com
-->Disclaimer: This page is not officially sanctioned by the SCA,
Inc., the Middle Kingdom, or the MK College of Heralds. It is a private
project of the Escutcheon Herald (Angharad Rhos Tewdwr of Pembroke) and the Rouge Scarpe Herald (Paul Wickenden of Thanet) who
have based the information published here on publicly-available
documentation.