![]() |
|
![]() |
#1 |
EAAF Staff
Join Date: Dec 2004
Location: Louisville, KY
Posts: 7,272
|
![]()
I would place this as possibly from the late 1700s or early 1800s, Sulu region, and is of chieftain class.
If the moderators would move this to the Ethno section where we can continue the discussion. |
![]() |
![]() |
![]() |
#2 |
Vikingsword Staff
Join Date: Dec 2004
Location: The Aussie Bush
Posts: 4,361
|
![]()
Agree with Jose that this is probably an early 19th C. Sulu kris. The traditional finish on the blade would be to polish it with very fine sandpaper and then etch the blade to show its pattern. There are many threads here that discuss etching Moro kris, and I would suggest using the search function on this site to obtain a wealth of more information.
Ian. |
![]() |
![]() |
![]() |
#3 |
Member
Join Date: Dec 2004
Location: Greenville, NC
Posts: 1,854
|
![]()
A lovely example of this "archaic" type! Congrats!
|
![]() |
![]() |
![]() |
#4 | |
Keris forum moderator
Join Date: Aug 2006
Location: Nova Scotia
Posts: 7,211
|
![]() Quote:
![]() |
|
![]() |
![]() |
![]() |
#5 |
EAAF Staff
Join Date: Dec 2004
Location: Louisville, KY
Posts: 7,272
|
![]()
David I thought of that, but there aspects of the Ganga and the forte areas that are very early and appear archaic. This blade is either an anomaly or later blade with archaic styles (unheard of so far).
|
![]() |
![]() |
![]() |
#6 |
Vikingsword Staff
Join Date: Nov 2004
Posts: 6,336
|
![]()
Maybe we might consider this kris as a 'transitional' style.
Do I see activity in the core of this sword? |
![]() |
![]() |
![]() |
#7 |
Member
Join Date: Dec 2004
Location: Greenville, NC
Posts: 1,854
|
![]()
David,
I see your point. The blade is wider than typical with far more shallow luks, but when I look at the whole thing in its entirety it strikes me as archaic, even more so if it etches out to a twistcore. We can surely agree that it is at least early 19th century. I think Battara may have a good point as well...that it is a variation of the "archaic" form. I hate getting tied into jargon that is too "rule-making" on these type of issues because it has been my experience that every time we think we have found a line or defining feature, there can be an exception to the rule. ![]() |
![]() |
![]() |
![]() |
|
|