From 3b49e6b16cb2eff84311abccd6387376c6f4bcbf Mon Sep 17 00:00:00 2001 From: David Runge Date: Fri, 19 Apr 2019 08:51:51 +0200 Subject: posts/*: Fixing the use of the sphinx-only :abbr: docutils role (by defining a new custom role per instance). --- posts/201604-linux-audio-conference-2016.rst | 24 ++++++++++++++++++++---- 1 file changed, 20 insertions(+), 4 deletions(-) (limited to 'posts/201604-linux-audio-conference-2016.rst') diff --git a/posts/201604-linux-audio-conference-2016.rst b/posts/201604-linux-audio-conference-2016.rst index 63309dc..9f78ee9 100644 --- a/posts/201604-linux-audio-conference-2016.rst +++ b/posts/201604-linux-audio-conference-2016.rst @@ -10,7 +10,7 @@ The conference ______________ | The |linux_audio_conference| is actually a quite old concept by now. Started as a small Linux Audio user group meeting at LinuxTag back in 2002, the conference more and more developed into a multi-national event, thanks to people such as Frank Neumann (who by the way initially had a *"hacker meeting"* in mind) and places like the |zkm|. -| As more universities hosted it, its academic side strengthened, leading to proper :abbr:`proceedings (In academia, proceedings are the collection of academic papers published in the context of an academic conference.)`, paper and poster presentations. +| As more universities hosted it, its academic side strengthened, leading to proper |abbr_proceedings|, paper and poster presentations. | Generally speaking it has also always been a place to present software, do workshops to show people how to use software and try it out - suited for developers, users and interested alike! | Another nice aspect that evolved over the years is the concept of the *"Linux Sound Night"*, giving the stage to the artists to present their pieces or perform live. | There's obviously a lot more to the history of the |linux_audio_conference| (which is no wonder after such a long time!), than I could elaborate on. @@ -19,8 +19,8 @@ ______________ | This is where I offer you the following three choices: | -* :abbr:`tl;dr (Too long; didn't read)`, *"I don't care about the pain, take me to the good times!"*: Just skip the *"how"* and go to `the results `_ -* :abbr:`tl;dr (Too long; didn't read)`, *"I only care about the pain"*: Watch |video_lac_is_dead_long_live_minilac| +* |abbr_tldr|, *"I don't care about the pain, take me to the good times!"*: Just skip the *"how"* and go to `the results `_ +* |abbr_tldr|, *"I only care about the pain"*: Watch |video_lac_is_dead_long_live_minilac| * *"I'm all up for pain (and good times, for that matter)"*: Read on! Additionally watch |video_lac_is_dead_long_live_minilac| @@ -65,7 +65,7 @@ _________ | | Two weeks before the start of |minilac| the wiki was attacked by a wave of spammers and I had to deal with the unpleasant work of deleting the pages of 500 spambots, blocking their accounts and strengthening the (hastily setup) security measures for the wiki. Lesson learnt. | Apart from the spambots the wiki also entailed another issue, that has to do with the way the |voc| operates. Being free-time professionals, they usually have conferences use |frab| for dealing with the content, which is an all-in-one conference management system, that generates all things needed for streaming, |info-beamer|, interfacing the |engelsystem| and generating a |fahrplan| (especially the latter is super helpful during large events to keep track of what is happening where, as there's also an Android App available for it). -| This meant parsing the information from our wiki and generating the needed :abbr:`XML (Extensible Markup Language)` and :abbr:`JSON (JavaScript Object Notation)` files ourselves. Pretty painful, but we got it done (well, apart from triggering a bunch of bugs in the |voc|'s |voc_schedule_validator|, which lead to never being able to generate a proper |fahrplan|). +| This meant parsing the information from our wiki and generating the needed |abbr_xml| and |abbr_json| files ourselves. Pretty painful, but we got it done (well, apart from triggering a bunch of bugs in the |voc|'s |voc_schedule_validator|, which lead to never being able to generate a proper |fahrplan|). | Last minute fixes for the |info-beamer| were needed as well, but thanks to the |voc|, we got them done just in time! | Meanwhile I prepared some hardware to be lent from the |electronic_studio| and the insurance for the |voc| equipment (to be used in combination with already available |c-base| hardware). | @@ -358,3 +358,19 @@ These are the lessons learnt from doing this event: ZKM +.. |abbr_proceedings| raw:: html + + proceedings + +.. |abbr_tldr| raw:: html + + tl;dr + +.. |abbr_xml| raw:: html + + XML + +.. |abbr_json| raw:: html + + JSON + -- cgit v1.2.3