William I de La Marck

William de la Marck[1] (1446–1485) was an adventurer of German extraction. He became an important character in the late 15th century in the Prince-Bishopric of Liège. William's was nicknamed Le Sanglier des Ardennes (The Wild Boar of the Ardennes)— because he was as fierce as the wild boar which he delighted to hunt.[2]

In 1482, he had Louis de Bourbon, Bishop of Liège, assassinated, in order to replace him by his own son Jean de la Marck. He failed to have Jean accepted, and the next bishop was John of Hornes. This act led to a civil war in the prince-bishopric.

On 21 May 1484, a treaty was signed at Tongeren, whereby the de la Marck family forfeited its claims to the bishopric and supported Liège's struggle against Maximilian I, Holy Roman Emperor for the reward of 30,000 livres. Bouillon castle was mortgaged to William de la Marck until the time of repayment.

In 1485, he was ambushed near Sint-Truiden and taken to Maastricht, where he was beheaded on 18 June 1485.

William's cousin Erard de la Marck became prince-bishop from 1506 until 1538.

His great-grandson William II de la Marck was an important leader of the Gueux de mer in the Eighty Years' War.

Cultural influences

He is described by Sir Walter Scott as "William, Count of la Marck", in Quentin Durward.[2]

Notes and references
  1. Also known as Guillaume de la Marck in some English language sources
  2. E. Cobham Brewer (1894). Dictionary of Phrase and Fable, San’glier (Sir),Boar


gollark: I agree that writing everything in intensely horrific JS is bad. I just don't think that much application software which is currently written in C would become worse if written in something safer and higher level.
gollark: I'm quite confident that the majority of user-facing ~~ones~~ computer systems have most of the development effort invested in random applications software which doesn't need to be hyperoptimized.
gollark: The top end grows, but most applications actually aren't that.
gollark: Computers are ridiculously powerful and more than capable of running most general purpose things anyone cares about very fast, if those things are sanely implemented. We know this because they can continue sort of usably working despite JS and such.
gollark: They're already very fast. Unless you're doing some very time sensitive data processing you can afford bounds checks and such in your code.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.