Louis Édouard Fournier

Louis Édouard Fournier (12 December 1857 – 10 April 1917) was a French painter and illustrator.

The Funeral of Shelley by Louis Édouard Fournier (1889); pictured in the centre are, from left, Trelawny, Hunt, and Byron

Fournier participated in many large-scale artistic endeavors, chief of which was the creation of frescoes for the decoration of the Grand Palais in Paris, in association with other artists including Alexandre Falguière. Fournier also created many mosaic friezes, considered at the time milestones in French art.

One of his most celebrated frescoes, "Aux gloires du Lyonnais et du Beaujolais" is in the Deliberation Room in the Council General of Rhône in Lyon. He also produced a series of paintings devoted to the beauties of Lyon, along with many wood carvings.

One of his most famous works is "The Funeral of Shelley" (1889), shown here.

Fournier also illustrated numerous books, including works of Jean de la Fontaine and Honoré de Balzac, most notably The Duchess of Langeais.

Further reading
  • Marshall, Nancy Rose (April 2014). ""A Fully Consummated Sacrifice upon Her Altar": Victorian Cremation as Metamorphosis". Victorian Studies. 56 (3): 458–469. doi:10.2979/victorianstudies.56.3.458.


gollark: It could record locally and upload later, though.
gollark: This person apparently reverse-engineered it statically, not at runtime, but it *can* probably detect if you're trying to reverse-engineer it a bit while running.
gollark: > > App behavior changes slightly if they know you're trying to figure out what they're doing> this sentence makes no sense to me, "if they know"? he's dissecting the code as per his own statement, thus looking at rows of text in various format. the app isn't running - so how can it change? does the app have self-awareness? this sounds like something out of a bad sci-fi movie from the 90's.It's totally possible for applications to detect and resist being debugged a bit.
gollark: > this is standard programming dogma, detailed logging takes a lot of space and typically you enable logging on the fly on clients to catch errors. this is literally cookie cutter "how to build apps 101", and not scary. or, phrased differently, is it scary if all of that logging was always on? obviously not as it's agreed upon and detailed in TikTok's privacy policy (really), so why is it scary that there's an on and off switch?This is them saying that remotely configurable logging is fine and normal; I don't think them being able to arbitrarily gather more data is good.
gollark: > on the topic of setting up a proxy server - it's a very standard practice to transcode and buffer media via a server, they have simply reversed the roles here by having server and client on the client, which makes sense as transcoding is very intensive CPU-wise, which means they have distributed that power requirement to the end user's devices instead of having to have servers capable of transcoding millions of videos.Transcoding media locally is not the same as having some sort of locally running *server* to do it.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.