Christian Friedrich von Otto

Christian Friedrich von Otto (26 October 1758 – 8 September 1836) was a Württemberger official and politician.

Life and career

Otto was born on 26 October 1758 in Dettingen unter Teck, as the son of a Protestant minister. After attending high school in Stuttgart, he studied law with Carl Christopher Hofacker (1749–1793) at the University of Tübingen. Later, he moved to the University of Strasbourg and focused on the Supreme Court in Colmar with French law. This helped him prepare his dissertation, and in 1780 he obtained his doctorate and worked as a lawyer.

Secretary of the Duke

In 1786, he became secretary of Charles Eugene, Duke of Württemberg. In 1792, he was appointed Minister and assessor of the court. He later established the Kingdom of Württemberg. After 1806, he took over the Police Department of the Upper Württemberg and the Regional Economics College.

Napoleonic Wars

During the Napoleonic Wars, he added the position of Commissioner-General for supply of foreign troops. This included the management of financial and material logistics and the hospital system. In 1811, he became Head of the Local Government and a member of the newly established Württemberg State Council. In 1814 he acquired the Grand Cross of Civil Merit Württemberg, which was connected with German nobility.[1] In 1815, he took care of the financial compensation of the troops stationed in France the Württemberg army and the army of the Grand Duchy of Hesse by the French Treasury. In 1818 he acquired the Order of the Crown (Württemberg).[2] He died in Stuttgart on 8 September 1836.

Notes
  1. Königlich Württembergisches Hof- und Staatshandbuch. 1828, S. 73.
  2. Königlich Württembergisches Hof- und Staatshandbuch. 1828, S. 28.
gollark: API coherency: drop stuff like XMLHttpRequest which is obsoleted by cleaner things like `fetch`, actually have a module system and don't just randomly scatter objects and functions in the global scope, don't have a weird mix of callbacks, events and promises everywhere.
gollark: Alternatively, cross-origin stuff is allowed but runs with separate cookies, caches, etc. to first-party requests, and comes with a "requested from this origin" header.
gollark: Cross-origin fixes: *no* use of crossdomain resources unless the other thing opts in. This breaks image hotlinking and such, which is annoying, but fixes CSRF entirely.
gollark: That doesn't really help with the security issues though.
gollark: Maybe a standard interface for external plugins for access to that stuff, so browsers wouldn't need to implement all the APIs individually?
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.