I was actually trying to understand why command line option parsing on my computer with self compiled VLC behaves as "If the first character of optstring is '+' or the environment variable POSIXLY_CORRECT is set, then option processing stops as soon as a non-option argument is encountered." while neither of these conditions is true (see the while( getopt_long( ... ) != EOF ) loop).
Small illustration:
./vlc -vvv -I dummy input.ts --color
All options before the first non option argument work as expected (-vvv and -I dummy). All options after the first non option argument are also interpreted as being non option arguments.
Help would be appreciated.
(I've already had reports of other people having the same kind of issues)

Report and fix from Pavlov Konstantin “thresh”

- Fix HTTPd crash
- Break the old interface again

Thanks.

For those wondering, this *is* swedish.

intf.m: * we can't localise empty strings, so don't put an error when trying to do so, but just a warning
    * be a bit nicer and return @"" instead of NULL strings
    - this fixes the display of certain modules in the preferences such as the parametric equaliser

prefs.m: * removed 2 unused variables

* Add Shorten codec. This refs #632 It doesn't seem to work, but that might be an endianness issue. will someone please check with this sample? http://www.mplayerhq.hu/MPlayer/samples/A-codecs/lossless/luckynight.shn

* winamp2.xml: added "kbps" info in winamp skins

Win32 specific changes: Add --started-from-file option to tell VLC that it was started by clicking on a file (or disc). Add --one-instance-when-started-from-file option to tell VLC to use one instance mode when --started-from-file is used. See replies to r15125 for an explanation.

Should fix the old interface - will most likely break the new one
(in particular try with non-Latin-1 characters)