122026: adjust names of newly introduced UNO commands; correct uno:FlipHorizontal and uno:FlipVertical

the changes to emplace_args.hpp are from the boost 1.50 version 

122072 map SID_ATTR_LINE_START and SID_ATTR_LINE_END to the correct GetState method GetDrawAttrState

122072 map SID_ATTR_LINE_START and SID_ATTR_LINE_END to the correct GetState method GetDrawAttrState

there are non-gcc compilers such as clang that support this feature

when the provided type and the target type of an initializer list don't match
the new behaviour described in C++11's N2672 proposal can be triggered. Though
that is very useful in general it complicates things for our case so that we're
better of to use the little helpers provided by XCode's CF framework.

i122041 Added 'Automatic' to TextPropertyPanel FontColor and HilightColor, added 'No Color' to ParagraphPropertyPanel BackgroundColor

- a reference to a still incomplete AquaA11FocusListener was used
- method declarations inside the class must omit the class name qualifier

The interesting discussion in http://gcc.gnu.org/ml/gcc/2012-03/threads.html#00455
pointed to the fnon-call-exception option to solve this problem. Thanks to Stephan
for starting this fruitful mailing list thread.

they are dirtied directly in the assembler code, so add them to the clobber list

destructing them via their baseclasses virtual destructor would be possible but
some aggressive compilers use their type knowledge to destruct them directly.
For such cases these destructors need to available as inlines or as visible symbols
which does not always seem to be the case for implicitly declared destructors.

also a minor cleanup of that code part

else clang/libc++ cannot decide between bool and a reference into a bit-vector specialization

also mark some related local functions as static

Work around libc++'s specialization for fill_n() not returning the matching OutputIterator.

The TR1 containers don't support dynamic hash functions provided in their constructor.
Having the hash functor as part the hash container's type is cleaner anyway.

the function call convention for IA32 apps on OSX documented at
http://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/LowLevelABI/130-IA-32_Function_Calling_Conventions/IA32.html
indicates that ECX is not preserved.