Fabien Audard

Fabien Audard (born March 28, 1978) is a French former professional footballer who played as a goalkeeper.

Fabien Audard
Audard playing for Lorient against Rennes in February 2008
Personal information
Date of birth (1978-03-28) March 28, 1978
Place of birth Toulouse, France
Height 1.89 m (6 ft 2 in)
Playing position(s) Goalkeeper
Senior career*
Years Team Apps (Gls)
1996–2001 Toulouse 9 (0)
2001–2003 Bastia 0 (0)
2002–2003 → Lorient (loan) 30 (0)
2003–2015 Lorient 266 (0)
2004–2005 → Monaco (loan) 4 (0)
Total 309 (0)
* Senior club appearances and goals counted for the domestic league only

Career

Born in Toulouse, Haute-Garonne, Midi-Pyrénées, Audard began at his local club Toulouse FC which formed him. He made his debut as a first-half substitute in the Ligue 1 match against Olympique de Marseille on October 3, 1998. Toulouse were already a goal down and eventually lost 2–0. He conceded his first goal to Fabrizio Ravanelli.

On November 4, 2000, that Audard made his next appearance, playing the full match as Toulouse drew 0–0 with RC Strasbourg. He played four further times that season before moving to SC Bastia in August 2001.

Audard did not play for Bastia in his first season there, and was loaned out to Ligue 2 Lorient for the 2002–03 season, where he played thirty matches. The move was made permanent and the 2003–04 season gave Audard 25 more matches. AS Monaco secured his services on loan for the 2004–05 season, where he played four matches as cover for Flavio Roma.

Returning to Lorient, Audard missed just one match of their 2005–06 promotion campaign.

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.
gollark: Probably. The main issue I can see is that you would have to rewrite the entire metadata block on changes, because start/end in XTMF are offsets from the metadata region's end.
gollark: I thought about that, but:- strings in a binary format will be about the same length- integers will have some space saving, but I don't think it's very significant- it would, in a custom one, be harder to represent complex objects and stuff, which some extensions may be use- you could get some savings by removing strings like "title" which XTMF repeats a lot, but at the cost of it no longer being self-describing, making extensions harder and making debugging more annoying- I am not convinced that metadata size is a significant issue
gollark: I mean, "XTMF with CBOR/msgpack and compression" was being considered as a hypothetical "XTMF2", but I'd definitely want something, well, self-describing.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.