comparing pointers with bools or integers is not a good idea and
clang>=3.4 or xcode>=5.1 now report errors for such code. The
errors break the build and so they have to be fixed.

The SAL module avoided the heavy dependency on the stlport4-libraries by using
a custom allocator for its internal STL containers. With stlport4 removed these
dependencies are gone and the SAL-internal custom allocator is obsoleted. Since
the custom allocator results in build problems with clang>=3.4 or xcode>=5.1 it
is time to remove it for good.

in AV Foundation the most accurate media asset duration is available when the
AVPlayerItem's status changes to AVPlayerItemStatusReadyToPlay. There already
is an observer for this, but the upper layers expect getDuration() to be
synchronous and to return within a reasonable time. Since returning an
approximation is sufficient using the AVAsset's duration as fallback is fine.

FrameGrabber used to load its own copy of a movie. Since multimedia content
is often very data-intensive this should and can be avoided by using the
movie asset already available in the Player.

in the dmake build environment active header and source files with the
same name result in problems when in the same project. The Quicktime and
MacAVF files have been renamed so that both can be active concurrently.

While XCode5's xcode-select supports the -p and --print-path options, XCode4
officially only knows -print-path. XCode4 seems to tolerate --print-path though
(tested on XCode4.6), so this can be universally used.
Patch-by: Thorsten Wagner <thorsten.wagner.4@gmail.com>
Review-by: Herbert Duerr <hdu@apache.org>

because the QuickTime API is not available to 64bit clients. The switch to QTKit
is temporary only because it has already been deprecated in OSX 10.9. We'll have
to switch to OSX's AVFoundation framework instead soon.

Suggested by: Ariel Constenla-Haile <arielch@apache.org>

There is an issue building the bridges module with newer versions
of gcc. Merge a local workaround for gcc used in amd64 (r1424178)
to fix the build.

Reference:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/187218

patch by: caolanm@redhat.com

The spelling issue is real but we can't really start renaming functions in 
the API.

Reported by:	arielch

Attempt to clean up most but certainly not all the spelling
mistakes that found home in OpenOffice through decades.

Did I mention this is more important than translating
German comments? ;)

Attempt to clean up most but certainly not all the spelling
mistakes that found home in OpenOffice through decades. We
could probably blame the international nature of the code but
it is somewhat shameful that this wasn't done before.

Attempt to clean up most but certainly not all the spelling
mistakes that found home in OpenOffice through decades. We
could probably blame the international nature of the code but
it is somewhat shameful that this wasn't done  before.

Attempt to clean up most but certainly not all the spelling
mistakes that found home in OpenOffice through decades. We
could probably blame the international nature of the code but
it is somewhat shameful that this wasn't done  before.

Attempt to clean up most but certainly not all the spelling
mistakes that found home in OpenOffice through decades. We
could probably blame the international nature of the code but
it is somewhat shameful that this wasn't done  before.

124674: Toolbarmanager: correct show/hide of toolbars (correction of fix for issue 124355); correct consideration of hidden toolbars;

-- do not propagate tab stops of unused paragraph styles
-- do not propagate default tab stops

Added "IsBackgroundObjectsVisible" property support for sd OOXML importing