Talk:Hadhafang

From Tolkien Gateway
Revision as of 16:36, 11 November 2019 by Olwe (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Latest comment: 11 November 2019 by Olwe

Some viewers claimed that Hadhafang was a Japanese-type sword. This is not true. Hadhafang was inspired by western cavalry sabers and the Assyrian sickle-sword. Hadhafang is made for use on horseback, as evidenced by the fact that Arwen was to carry a borrowed Rohiric sword during the actual Battle of Helms Deep, but Hadhafang during the charge and the Warg battle. However, the decision to not include Arwen in Helms Deep was made and we never got to see this sword in battle. Some people have also commented on the bad balance of the prop, not realizing that is meant for work from horseback. Retrieved from "http://lotr.wikia.com/wiki/Hadhafang"

What's everyone think about this ? Dunrana 02:26, 5 August 2010 (UTC)Reply[reply]

I'm not convinced it's useful unless we have references for all of that. Interesting theory, though, I've not heard any of this before. --Mith (Talk/Contribs/Edits) 07:04, 5 August 2010 (UTC)Reply[reply]
The first mention of the Assyrian bladibla was in a page revision from May 11, 2007. One should possilby look for one of the Weta Publishing publications on the film trilogy to have come out in the weeks before that; otherwise there is not a single online trace out there. --Olwe 16:16, 11 November 2019 (UTC)Reply[reply]
Addendum: I may have found the 'missing link' to the source of this statement here: "There were some pre-release production specials run for each of the 3 movies that showed a lot of the work that went into designing and making the weapons and armor used in the movies. I particularly liked the elvish weapons for their beautiful lines and decorative work. Elvish swords like Elrond's Hadhafang had a definite samurai influence to them." So in those 'specials' which might be found on the EEs they may have talked about how 'Hadhafang' came about. --Olwe 16:36, 11 November 2019 (UTC)Reply[reply]