recreated tag libreoffice-3.3.3.1 which had these commits:

commit dc53bbdbf2e1d0cbb53bb4619188955698f8a5c2 (tag: refs/tags/libreoffice-3.3.3.1)
Author: Petr Mladek <pmladek@suse.cz>
Date:   Tue May 31 17:39:09 2011 +0200

    Version 3.3.3.1, tag libreoffice-3.3.3.1 (3.3.3-rc1)

commit e4601251b90e2555b032eadbdaa56dcfb91b5aae
Author: Noel Power <noel.power@novell.com>
Date:   Wed Apr 13 18:52:58 2011 +0100

    fix for fdo#35108 allow dot net clients to bootstrap libreoffice

    Signed-off-by: Petr Mladek <pmladek@suse.cz>

 cli_ure/source/native/native_bootstrap.cxx |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

commit 1818bf1dbc330974c749ca17b4d7b79796587fae
Author: Jani Monoses <jani.monoses@canonical.com>
Date:   Mon Mar 14 19:10:04 2011 +0100

    prefer gcc __sync functions over pthread

    Signed-off-by: Bjoern Michaelsen <bjoern.michaelsen@canonical.com>

 sal/osl/unx/interlck.c |    9 +++++++++
 1 files changed, 9 insertions(+), 0 deletions(-)

1 files changed, 4 insertions, 4 deletions

diff --git a/offapi/com/sun/star/chart2/XPlotter.idl b/offapi/com/sun/star/chart2/XPlotter.idl
index e6f6ef3fafd4..af3b19a63b29 100644
--- a/offapi/com/sun/star/chart2/XPlotter.idl
+++ b/offapi/com/sun/star/chart2/XPlotter.idl
@@ -75,7 +75,7 @@ module com {  module sun {  module star {  module chart2 {
 interface XPlotter : ::com::sun::star::uno::XInterface
 {
     //-------------------------------------------------------------------------
-    /** Each Plotter implicit uses a certain type of logic coordinate
+    /**	Each Plotter implicit uses a certain type of logic coordinate
         system for interpreting data as coordinates.
         For example a bar-chart uses a Cartesian coordinate system for
         interpreting x- and y-values from a spreadsheet as Cartesian
@@ -90,11 +90,11 @@ interface XPlotter : ::com::sun::star::uno::XInterface
     //-------------------------------------------------------------------------
     /** For each type of shapes ('logic' or 'illogic') there exists one
     container. The Plotter will create shapes and then add (or remove)
-    them from these containers.
+    them from these	containers.
 
     <p>
     The lifetime of the container has to be handled by the calling object. The
-    calling object must assure that the container will exist longer than the
+    calling object must assure that the	container will exist longer than the
     XPlotter Object.
     </p>
     ...
@@ -108,7 +108,7 @@ interface XPlotter : ::com::sun::star::uno::XInterface
     XPlotter object needs a Scale to decide which shapes
     need to be created and maybe logically clipped. The XPlotter object
     becomes the new owner of the given scales and directions and needs to keep
-    them alive. Nobody else will change them.
+    them alive.	Nobody else will change them.
     Pay attention that a 'Scale' can have several breaks.
     */
     void setScales( [in] sequence< ScaleData > rScales);