Walter Vielhauer

Walter Vielhauer  (April 1, 1909 in Reutlingen - April 19, 1986 in Heilbronn) was a communist and anti-fascist of Heilbronn who was held captive by Nazi Germany before and during World War II.

He was first arrested in March 1933 and was held several weeks at the new concentration camp Heuberg. After his release, he continued his struggle against fascism and in autumn of 1933, he was arrested again. He was condemned to five and a half years in penintentiary, which he had to spend in solitary confinement. After serving his sentence, he was sent to various concentration camps, Welzheim, Dachau, Mauthausen and Buchenwald, where he was active with the Resistance activities there.

In June 1945, he was deployed by the United States Army as assistant of the lord mayor and was responsible for social affairs in Heilbronn until 1948.

Sources
  • Hitler als Hoffnungsträger. In: Heilbronn im nationalsozialistischen Deutschland 1933–1945 (in German)
  • Buchenwald - Ein Konzentrationslager. Bericht der ehemaligen KZ-Häftlinge Emil Carlebach, Paul Grünewald, Helmut Röder, Willy Schmidt, Walter Vielhauer. ISBN 3-87682-786-8 (in German)
  • Trau! Schau! Wem? Dokumente zur Geschichte der Arbeiterbewegung im Raum Heilbronn/Neckarsulm 1844-1949. ISBN 3-929348-09-8 (in German)
  • Opfer von Terror und Verfolgung: Walter Vielhauer (1909–1986) (in German)
gollark: Okay, very hacky but technically workable: have an XTMF metadata block of a fixed size, and after the actual JSON data, instead of just ending it with a `}`, have enough spaces to fill up the remaining space then a `}`.
gollark: XTMF was not really designed for this use case, so it'll be quite hacky. What you can do is leave a space at the start of the tape of a fixed size, and stick the metadata at the start of that fixed-size region; the main problem is that start/end locations are relative to the end of the metadata, not the start of the tape, so you'll have to recalculate the offsets each time the metadata changes size. Unfortunately, I just realized now that the size of the metadata can be affected by what the offset is.
gollark: The advantage of XTMF is that your tapes would be playable by any compliant program for playback, and your thing would be able to read tapes from another program.
gollark: Tape Shuffler would be okay with it, Tape Jockey doesn't have the same old-format parsing fallbacks and its JSON handling likely won't like trailing nuls, no idea what tako's program thinks.
gollark: Although I think some parsers might *technically* be okay with you reserving 8190 bytes for metadata but then ending it with a null byte early, and handle the offsets accordingly, I would not rely on it.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.