Re: How to add generate symbols for gdb?

[Hung Mark]

Hi Ariel,

After I reconfigured the project  with --build-with-package-format option,
debugging symbols were successfully generated,
even before I tried to use dbglevel=2 or debug=t in the target module.

I also updated wiki
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step
for these options.


By the way, I also tried build debug=true dbg_build_only=true. It keep eat
up my diskspace ( 35GB before I break it ).
I wonder what it does and whether it is still a valid command.

Thank you for all the effort.




2014-08-17 0:55 GMT+08:00 Ariel Constenla-Haile :

> On Sun, Aug 17, 2014 at 12:27:39AM +0800, Hung Mark wrote:
> > Here is how I did:
> > After I build & deliver in the module, I go into instsetoo_native, then
> > build --all -P4 -- -P4
> > After that, I install all packages generated with dpkg -i.
> > Will it work this way?  They should work the same except my way takes
> > longer.
>
> I guess symbols are stripped somewhere in that process.
>
>
> > > It's better to move the installation from instsetoo_native to another
> > > place, build the needed modules with debug symbols, then copy the
> > >
> >
> > What do you mean by moving instsetoo_native to another place?
>
> I mean move the installation set that is generated there when you build
> with
>
> --with-package-format="installed"
>
> In this case, you have an office installation in
>
> instsetoo_native/unxlngx6/Apache_OpenOffice/installed/install/en-US
>
> and the SDK in
>
> instsetoo_native/unxlngx6/Apache_OpenOffice_SDK/installed/install/en-US
>
>
> Then move that installation somewhere else, in your home directory, for
> example.
>
> This will work if you don't need the desktop integration, it is faster
> to build (as you don't build rpms/debs). Then copy the libraries with
> debugging symbols from the source tree output directory to that
> installation.
>
>
> > I assume that you suggest this for preserving my original installation,
>
> No, I meant not to build packages; or, if you do so, rebuild the
> libraries you need with debugging symbols and copy them back to the
> place where you installed the office, because the whole process of
> building packages and installing them seems to be stripping the
> libraries.
>
>
> Regards
> --
> Ariel Constenla-Haile
> La Plata, Argentina
>

Re: Fwd: Funds for speaker to Central America Free Software event

[Alexandro Colorado]

BTW here is a flyer that was forward to me by the event organizers:
*http://tinyurl.com/lbnd7s3 *


On Sat, Aug 16, 2014 at 11:54 PM, Alexandro Colorado  wrote:

>
>
>
> On Sun, Aug 10, 2014 at 6:25 AM, jan i  wrote:
>
>> On 10 August 2014 13:00, Andrea Pescetti  wrote:
>>
>> > On 10/08/2014 jan i wrote:
>> >
>> >> It would be nice if at least the PMC group got knowledge about the
>> size of
>> >> this fund.
>> >>
>> >
>> > Of course it does. See http://s.apache.org/Vcg and
>> > http://s.apache.org/YqfA (links only accessible to members). Despite
>> many
>> > discussions, we never managed to reimburse anything so far except
>> > merchandising for FOSDEM 2013 (about 145 EUR).the
>> >
>>
>> Thanks for a swift reaction !
>>
>> Just to sure nobody misunderstand it, the "never managed" part is not due
>> to lack for will ! We are very open to any proposals, that benefits our
>> community but there has not been so many request (and some of them ended
>> up
>> by people not asking for funding).
>>
>> rgds
>> jan I
>>
>>
>> >
>> > Regards,
>> >   Andrea.
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> > For additional commands, e-mail: dev-h...@openoffice.apache.org
>> >
>> >
>>
>
> ​In the past there were some events that speakers and others received
> funding. The policy change depending of relevance and opportunity. Most of
> the funding was shared with the event organizers (split the bill between
> airfare or hotel bill).
>
> A similar form-driven process was handed by KDE EV for their activities.
>
> This time around the event is somewhat relevant to the area since is the
> largest and better organized event for the past 5 years. There seems to
> have gain some popularity in the area and even thought I have never
> attended to it before. I have got good reviews from ECSL.
>
> Unfortunately there hasn't been a relevant amount of contributions for
> that part of the world, and there has always been the intention but not
> always the right time to do it.
> The average number of participants is around 300 people, from 4 countries
> and with good potential to contribute to the project specially on l10n, but
> also extension development and such.
>
> I am in touch with the organizers so I could get more specific information
> on request. Will give a look at Jan's links and see what else is there to
> be done.​
>
>
> --
> Alexandro Colorado
> Apache OpenOffice Contributor
> 882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614
>



-- 
Alexandro Colorado
Apache OpenOffice Contributor
882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614

Re: Fwd: Funds for speaker to Central America Free Software event

[Alexandro Colorado]

On Sun, Aug 10, 2014 at 6:25 AM, jan i  wrote:

> On 10 August 2014 13:00, Andrea Pescetti  wrote:
>
> > On 10/08/2014 jan i wrote:
> >
> >> It would be nice if at least the PMC group got knowledge about the size
> of
> >> this fund.
> >>
> >
> > Of course it does. See http://s.apache.org/Vcg and
> > http://s.apache.org/YqfA (links only accessible to members). Despite
> many
> > discussions, we never managed to reimburse anything so far except
> > merchandising for FOSDEM 2013 (about 145 EUR).the
> >
>
> Thanks for a swift reaction !
>
> Just to sure nobody misunderstand it, the "never managed" part is not due
> to lack for will ! We are very open to any proposals, that benefits our
> community but there has not been so many request (and some of them ended up
> by people not asking for funding).
>
> rgds
> jan I
>
>
> >
> > Regards,
> >   Andrea.
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
> >
>

​In the past there were some events that speakers and others received
funding. The policy change depending of relevance and opportunity. Most of
the funding was shared with the event organizers (split the bill between
airfare or hotel bill).

A similar form-driven process was handed by KDE EV for their activities.

This time around the event is somewhat relevant to the area since is the
largest and better organized event for the past 5 years. There seems to
have gain some popularity in the area and even thought I have never
attended to it before. I have got good reviews from ECSL.

Unfortunately there hasn't been a relevant amount of contributions for that
part of the world, and there has always been the intention but not always
the right time to do it.
The average number of participants is around 300 people, from 4 countries
and with good potential to contribute to the project specially on l10n, but
also extension development and such.

I am in touch with the organizers so I could get more specific information
on request. Will give a look at Jan's links and see what else is there to
be done.​


-- 
Alexandro Colorado
Apache OpenOffice Contributor
882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614

Re: [VOTE]: Release Apache OpenOffice 4.1.1 (RC3)

[Keith N. McKenna]

On 8/15/2014 3:15 AM, Jürgen Schmidt wrote:
> Hi all,
> 
> this is a call for vote on releasing the available release candidate
> (RC3) as Apache OpenOffice 4.1.1.
> 

> Please vote on releasing this package as Apache OpenOffice 4.1.1
> 
> The vote starts now and will be open until:
> 
>Tuesday, 19 August: 2014-08-19 12:00am UTC+2.
> 
> We invite all people to vote (non binding) on this RC. We would like
> to provide a release that is supported by the majority of our project
> members.
   [X] +1 Release this package as Apache OpenOffice 4.1.1
   [ ]  0 Don't care
   [ ] -1 Do not release this package because...



signature.asc
Description: OpenPGP digital signature

Re: opengrok.adfinis-sygroup.org unavailable

[Regina Henschel]

Hi all,

I have written an email to the support of adfinis-sygroup. They have 
restarted the service and openGrok works again now.


Kind regards
Regina


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [VOTE]: Release Apache OpenOffice 4.1.1 (RC3)

[Regina Henschel]

Hi Jürgen,

downloaded Windows-Version de, langpack_en, SDK, source. md5 is OK.
Standard-Installation over an existing RC2 without problems. User 
settings are retained.



Jürgen Schmidt schrieb:

Hi all,

this is a call for vote on releasing the available release candidate
(RC3) as Apache OpenOffice 4.1.1.

[..]

Please vote on releasing this package as Apache OpenOffice 4.1.1

The vote starts now and will be open until:

Tuesday, 19 August: 2014-08-19 12:00am UTC+2.

We invite all people to vote (non binding) on this RC. We would like
to provide a release that is supported by the majority of our project
members.

[ ] +1 Release this package as Apache OpenOffice 4.1.1
[ ]  0 Don't care
[ ] -1 Do not release this package because...


+1 Release this package as Apache OpenOffice 4.1.1

Kind regards
Regina

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [VOTE]: Release Apache OpenOffice 4.1.1 (RC3)

[Kay Schenk]

On Sat, Aug 16, 2014 at 4:23 AM, Jose R R  wrote:

> Niltze, Jürgen-
>
> I was about install ApacheOO 4.1.1 (RC3) but the sha256 do not match:
>
> $ wget
> http://ci.apache.org/projects/openoffice/milestones/4.1.1-rc3-r1617669/binaries/en-US/Apache_OpenOffice_4.1.1_Linux_x86-64_install-deb_en-US.tar.gz.sha256
>
> $ sha256sum -b  Apache_OpenOffice_4.1.1*gz
> 5121c9333b47bca9af71ca2f0dd41da463748a5cfb1a41eb8232284ad98323c2
> *Apache_OpenOffice_4.1.1_Linux_x86-64_install-deb_en-US.tar.gz
>
> $ cat Apache_OpenOffice_4.1.1_Linux_x86-64_install-deb_en-US.tar.gz.sha256
> 9624930a634891ed7ed6b2d19dd71303da1e900cf7ced56885f6d0bdceced4a9
> *Apache_OpenOffice_4.1.1_Linux_x86-64_install-deb_en-US.tar.gz
>
> Further:
> $ wget https://people.apache.org/keys/group/openoffice.asc
>
> $ wget
> http://ci.apache.org/projects/openoffice/milestones/4.1.1-rc3-r1617669/binaries/en-US/Apache_OpenOffice_4.1.1_Linux_x86-64_install-deb_en-US.tar.gz.asc
>
> $ gpg --import openoffice.asc
>
> $ gpg --verify
> Apache_OpenOffice_4.1.1_Linux_x86-64_install-deb_en-US.tar.gz.asc
> gpg: Signature made Wed 13 Aug 2014 04:40:19 AM PDT using RSA key ID
> 51B5FDE8
> gpg: BAD signature from "Juergen Schmidt "
>
> Am I doing something incorrectly?
>
>
> Best Professional Regards.
>

No mismatch issues on Linux-32 rpm. So, hopefully one of the 64 bit deb
folks can check this out soon.


>
>
> On Fri, Aug 15, 2014 at 12:15 AM, Jürgen Schmidt 
> wrote:
> > Hi all,
> >
> > this is a call for vote on releasing the available release candidate
> > (RC3) as Apache OpenOffice 4.1.1.
> >
> > Apache OpenOffice 4.1.1 is mainly a bugfix release with some important
> > bugfixes. And we can provide again more complete UI translations and
> > have now support for 41 languages. New languages for this release
> > compared to 4.1.0 are Catalan, Catalan (Valencia AVL) and Catalan
> > (Valencia RACV).
> >
> > Apache OpenOffice 4.1.1 is the continuation of high quality software
> > releases.
> >
> > An overview of the integrated release issues can be found under:
> >
> >
> http://ci.apache.org/projects/openoffice/milestones/4.1.1-rc3-r1617669/AOO4.1.1_fixes.html
> >
> > The release candidate artifacts (source release, as well as binary
> > releases for 41 languages) and further information how to verify and
> > review Apache OpenOffice 4.1.1 can be found on the following wiki page:
> >
> >
> https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds
> >
> > (alternative directly via
> > http://ci.apache.org/projects/openoffice/milestones/4.1.1-rc3-r1617669)
> >
> > *.dmg files are still not recognized as binaries and have to be
> > saved manually (save link as ...).
> >
> > The RC is based on the release branch AOO410, revision 1617669! And a
> > fresh and clean RAT scan output of this revision can be found under
> >
> >
> http://ci.apache.org/projects/openoffice/milestones/4.1.1-rc3-r1617669/AOO4.1.1_RAT_Scan.html
> >
> > Please vote on releasing this package as Apache OpenOffice 4.1.1
> >
> > The vote starts now and will be open until:
> >
> >Tuesday, 19 August: 2014-08-19 12:00am UTC+2.
> >
> > We invite all people to vote (non binding) on this RC. We would like
> > to provide a release that is supported by the majority of our project
> > members.
> >
> >[ ] +1 Release this package as Apache OpenOffice 4.1.1
> >[ ]  0 Don't care
> >[ ] -1 Do not release this package because...
> >
> > -
> > To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: l10n-h...@openoffice.apache.org
> >
>
>
>
> --
> Jose R R
> http://www.metztli-it.com
>
> -
> NEW Apache OpenOffice 4.1.0! Download for GNU/Linux, Mac OS, Windows.
>
> -
> Daylight Saving Time in USA & Canada ends: Sunday, November 02, 2014
>
> -
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 
-
MzK

"For evil to flourish, it only requires good men to do nothing."
  -- Simon Wiesenthal

Re: Development progress on SVG-graphics

[Regina Henschel]

Hi all,

there have been some discussions in German in private emails before the 
implementations. That was a wrong behavior and should not happen again, 
please excuse this.


I'll translate and summarize here some of those discussions:

CSS knows a large variety of selectors in a rule, read 
http://www.w3.org/TR/CSS21/selector.html. We discussed to which extend 
they should be supported. Because currently Inkscape supports CSS only 
rudimentary, and there are no special requests in Bugzilla, and other 
areas of CSS (e.g. filter and animation) are more important, the 
decision has been, to support only those selectors, which can be 
implemented straightforward within the existing design. Find details 
about current implementation in the comments in 
main/svgio/source/svgreader/svgstylenode.cxx.


There exists currently no code to load external data which are 
referenced in a svg-image. Therefore support for "@import" rule has been 
postponed.


In contrast to browsers, the environment, in which svg-images are used 
in Apache OpenOffice, has no user-defined style sheets. In addition 
'@import' rule is not supported. So the author's rule is always taken 
and authors can directly determine the order of styles. Therefore the 
'!important' part of a description is ignored for now.


A CSS-style is stored in a SvgStyleAttributes-instance. Each svg-node 
gets a linked list of pointers to styles, ordered according the priority 
specified by "cascading". The list is build once using method 
fillCssStyleVector. (I hope, I've got it right.)


Kind regards
Regina

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

RE: DocFormats - Open source OOXML implementation

[Dennis E. Hamilton]

OK, I get it.  There is cross-talk between this dev-openoffice list and 
general-incubator involving two messages there,

1. A general-incubator post from you, replying to a message from Peter Kelley 
about his DocFormats document-conversion project and bringing Peter's request 
to the attention of general-incubator, at
.

2. An observation from Andrea that is essentially good wishes.

I find it an interesting leap from DocFormats to OpenOffice for tablets and 
look forward to seeing the incubator proposal.

I am definitely interested in the "student proposal, to get a compliance sheet 
made
for products that offer OXML and/or odf" that you mention.

Interoperability in interchange among document formats is a driving issue for 
me.  I look forward to more about that.  There has been significant effort in 
this area, although it does not seem to have made much impact and is generally 
little-known.  The OASIS effort on ODF Interoperability and Conformance (OIC 
TC) folded its tent in November 2013.  (On that one, I am an unindicted 
co-conspirator.)

I will see what references I can dig up after I submit updated pre-conference 
versions of some papers due this weekend, 
.  Information about those 
interop/conversion efforts would also be good backup information for the 
DChanges 2014 workshop next month.

 - Dennis

PS: Roundtripping between OOXML and HTML is something that Microsoft put 
considerable effort into.  Some found the resulting HTML (pre-HTML5) rather 
nauseous, but it is remarkably presentation-preserving as far as it goes. It 
might be informative to look into how well AOO does the same between ODF and 
[X]HTML as a calibration.  One could also look at the Office Web Apps, that 
manifest OOXML documents via editable web-page interfaces as a descendant.  
These seem to be tied to the way that some Phone and Tablet Microsoft Office 
applications are tied to cloud-stored documents.


-Original Message-
From: jan i [mailto:j...@apache.org] 
Sent: Saturday, August 16, 2014 09:45
To: Dennis Hamilton
Cc: dev; jan iversen
Subject: Re: DocFormats - Open source OOXML implementation

On 16 August 2014 18:38, Dennis E. Hamilton  wrote:

> I don't have any skin in this game.
>
> Yet I am baffled about where this work is going on and what Apache Project
> it relates to.  Is there an incubator proposal for Apache DocFormats on its
> way?
>
Yes there is a proposal on its way, look at general-incubator approx. the
last 3 days. Right now it is not decided who should sponsor this project.

[ ... ]

The intention is clearly to at least have a close cooperation with these
projects. But docFormats aims at a bit more (like e.g. being openoffice on
tablets).

I am right now working on student proposal, to get a compliance sheet made
for products that offer OXML and/or odf. MAybe that would be something you
would want to help out with.


[ ... ]


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: DocFormats - Open source OOXML implementation

[Peter Kelly]

ODF toolkit and Apache POI are both APIs to specific file formats. The key 
differences with DocFormats are

1. Support for multiple file formats (a limited range supported presently, but 
the intention is to expand to other formats)
2. Ability to "abstract over" a file format, in that the goal is to allow 
people to write apps without caring what format the data is physically stored in
3. Use of HTML as a common intermediate format during translation (though other 
formats can be manipulated if natively supported by an editor, then converted 
back to the source format)
4. Bi-directionality, i.e. the ability to do non-destructive updates when 
converting between formats
5. A building-block for creating HTML-based editors, viewers, and other 
applications (in particular, using WebKit or other browser engines)
6. No reliance on Java

If you want to do mobile, you can't use anything Java-based - that is, if you 
want to support iOS. No-one can use the two projects you mentioned if they want 
to build an iPhone or iPad app, which is one of several reasons ODF is absent 
from the mobile space.

Although in the past, Java has been a great choice for cross-platform 
applications, sadly this is no longer the case - hence C (the code was 
originally in Objective C but translated to C). It's also an extra dependency 
which can unnecessarily bloat requirements for an application, whereas this is 
very lightweight.

In addition to a library for dealing with file formats, the overall idea is 
much wider than that - to build applications on top of this, such as an editor, 
also within the context of the project. And also, promoting the idea of "file 
format independence", in the same way as most now see platform-independence as 
a good thing. We're looking to make it as flexible as possible, so that it can 
be adapted for mobile, desktop, and web. It's sort of a "clean start" in a 
sense, though not necessarily aiming to entirely replicate existing projects, 
but rather something new.

Both the ODF toolkit and Apache POI have useful work which will quite possibly 
be of use. In particular I think the latter may be helpful for supporting the 
older binary MS file formats, and we hope to collaborate with other Apache 
projects where relevant.

--
Dr. Peter M. Kelly
Founder, UX Productivity
pe...@uxproductivity.com
http://www.uxproductivity.com/
http://www.kellypmk.net/

PGP key: http://www.kellypmk.net/pgp-key
(fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966)

On 16 Aug 2014, at 11:38 pm, Dennis E. Hamilton  wrote:

> I don't have any skin in this game.
> 
> Yet I am baffled about where this work is going on and what Apache Project it 
> relates to.  Is there an incubator proposal for Apache DocFormats on its way?
> 
> In particular, I would expect that some thought would be given to the ODF 
> Toolkit and that incubator project, .
> 
> Also, Apache POI would seem to have some relevance, especially the OpenXML4J 
> component, .
> 
> These are all Java based, as is Armin's current project in the AOO 
> repository.  I haven't listed open-source projects outside the embrace of ASF.
> 
> A single  remark is in-line below (although this notation may derail 
> defective HTML presentation of plaintext containing angle brackets).
> 
> Re-subscribing to general-incubator now ... 
> 
> Oh, and congratulations on joining the IPMC, Jan.
> 
> -- Dennis E. Hamilton
>dennis.hamil...@acm.org+1-206-779-9430
>https://keybase.io/orcmid  PGP F96E 89FF D456 628A
>X.509 certs used and requested for signed e-mail
> 
> 
> 
> -Original Message-
> From: jan i [mailto:j...@apache.org] 
> Sent: Saturday, August 16, 2014 01:10
> To: dev
> Subject: Re: DocFormats - Open source OOXML implementation
> 
> On 16 August 2014 03:50, Peter Kelly  wrote:
> 
> [ ... ]
>> Now, onto the fix:
>> 
>> The library needs to have some way of checking that the HTML file being
>> used as part of an update operation has a mapping (id attributes) that
>> match the docx file being updated (in the case of creating a new file, this
>> is just an empty docx file). In the even that this is not the case, it
>> could still do the update, but would act as if the entire document had been
>> replaced with a completely new one.
>> 
>> The solution I'll likely implement (and this should really be my first
>> task, given the potential for problems like the above is this):
>> 
> In my humble opinion you should not use time on this right now.
> 
> If you fix a bug we have a 1-1 relation (1 man used, 1 bug fixed)
> If you start getting the documentation right we have a 1-n relations (1 man
> used, n men help fix bugs).
> 
> Please have in mind, we build a community in order to move away from "I
> have to do it, because I am the only one who know how" and you are the most
> important enabler of that..we need your knowledge in a file, so that
> others can work.
> 
> [ ... ]
> 
> When 

Re: How to add generate symbols for gdb?

[Ariel Constenla-Haile]

On Sun, Aug 17, 2014 at 12:27:39AM +0800, Hung Mark wrote:
> Here is how I did:
> After I build & deliver in the module, I go into instsetoo_native, then
> build --all -P4 -- -P4
> After that, I install all packages generated with dpkg -i.
> Will it work this way?  They should work the same except my way takes
> longer.
 
I guess symbols are stripped somewhere in that process.


> > It's better to move the installation from instsetoo_native to another
> > place, build the needed modules with debug symbols, then copy the
> >
> 
> What do you mean by moving instsetoo_native to another place?

I mean move the installation set that is generated there when you build
with

--with-package-format="installed"

In this case, you have an office installation in 

instsetoo_native/unxlngx6/Apache_OpenOffice/installed/install/en-US

and the SDK in

instsetoo_native/unxlngx6/Apache_OpenOffice_SDK/installed/install/en-US


Then move that installation somewhere else, in your home directory, for
example.

This will work if you don't need the desktop integration, it is faster
to build (as you don't build rpms/debs). Then copy the libraries with
debugging symbols from the source tree output directory to that
installation.


> I assume that you suggest this for preserving my original installation,

No, I meant not to build packages; or, if you do so, rebuild the
libraries you need with debugging symbols and copy them back to the
place where you installed the office, because the whole process of
building packages and installing them seems to be stripping the
libraries.


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


signature.asc
Description: Digital signature

Re: DocFormats - Open source OOXML implementation

[jan i]

On 16 August 2014 18:38, Dennis E. Hamilton  wrote:

> I don't have any skin in this game.
>
> Yet I am baffled about where this work is going on and what Apache Project
> it relates to.  Is there an incubator proposal for Apache DocFormats on its
> way?
>
Yes there is a proposal on its way, look at general-incubator approx. the
last 3 days. Right now it is not decided who should sponsor this project.


>
> In particular, I would expect that some thought would be given to the ODF
> Toolkit and that incubator project, <
> http://incubator.apache.org/odftoolkit/>.
>
> Also, Apache POI would seem to have some relevance, especially the
> OpenXML4J component, .
>
The intention is clearly to at least have a close cooperation with these
projects. But docFormats aims at a bit more (like e.g. being openoffice on
tablets).

I am right now working on student proposal, to get a compliance sheet made
for products that offer OXML and/or odf. MAybe that would be something you
would want to help out with.


> These are all Java based, as is Armin's current project in the AOO
> repository.  I haven't listed open-source projects outside the embrace of
> ASF.
>
> A single  remark is in-line below (although this notation may
> derail defective HTML presentation of plaintext containing angle brackets).
>
> Re-subscribing to general-incubator now ...
>
> Oh, and congratulations on joining the IPMC, Jan.
>
thanks a lot.

rgds
jan i

>
>  -- Dennis E. Hamilton
> dennis.hamil...@acm.org+1-206-779-9430
> https://keybase.io/orcmid  PGP F96E 89FF D456 628A
> X.509 certs used and requested for signed e-mail
>
>
>
> -Original Message-
> From: jan i [mailto:j...@apache.org]
> Sent: Saturday, August 16, 2014 01:10
> To: dev
> Subject: Re: DocFormats - Open source OOXML implementation
>
> On 16 August 2014 03:50, Peter Kelly  wrote:
>
> [ ... ]
> > Now, onto the fix:
> >
> > The library needs to have some way of checking that the HTML file being
> > used as part of an update operation has a mapping (id attributes) that
> > match the docx file being updated (in the case of creating a new file,
> this
> > is just an empty docx file). In the even that this is not the case, it
> > could still do the update, but would act as if the entire document had
> been
> > replaced with a completely new one.
> >
> > The solution I'll likely implement (and this should really be my first
> > task, given the potential for problems like the above is this):
> >
> In my humble opinion you should not use time on this right now.
>
> If you fix a bug we have a 1-1 relation (1 man used, 1 bug fixed)
> If you start getting the documentation right we have a 1-n relations (1 man
> used, n men help fix bugs).
>
> Please have in mind, we build a community in order to move away from "I
> have to do it, because I am the only one who know how" and you are the most
> important enabler of that..we need your knowledge in a file, so that
> others can work.
>
> [ ... ]
>
> When the project (hopefully) enters incubator, we will automatically have
> access to a bug tracking system (jira), and with that hopefully only being
> some month away I would not recommend setting up one now.
>
> 
>On Github, there is already an issues structure,
>.
>I think this should be continued in use until a different
>setup arrives "any day soon".  Note that some Github projects
>create a single subrepository that is just for its issues
>function.  E.g., https://github.com/keybase/keybase-issues
> 
>
>
> [ ... ]
>
>
>

RE: DocFormats - Open source OOXML implementation

[Dennis E. Hamilton]

I don't have any skin in this game.

Yet I am baffled about where this work is going on and what Apache Project it 
relates to.  Is there an incubator proposal for Apache DocFormats on its way?

In particular, I would expect that some thought would be given to the ODF 
Toolkit and that incubator project, .

Also, Apache POI would seem to have some relevance, especially the OpenXML4J 
component, .

These are all Java based, as is Armin's current project in the AOO repository.  
I haven't listed open-source projects outside the embrace of ASF.

A single  remark is in-line below (although this notation may derail 
defective HTML presentation of plaintext containing angle brackets).

Re-subscribing to general-incubator now ... 

Oh, and congratulations on joining the IPMC, Jan.
 
 -- Dennis E. Hamilton
dennis.hamil...@acm.org+1-206-779-9430
https://keybase.io/orcmid  PGP F96E 89FF D456 628A
X.509 certs used and requested for signed e-mail



-Original Message-
From: jan i [mailto:j...@apache.org] 
Sent: Saturday, August 16, 2014 01:10
To: dev
Subject: Re: DocFormats - Open source OOXML implementation

On 16 August 2014 03:50, Peter Kelly  wrote:

[ ... ]
> Now, onto the fix:
>
> The library needs to have some way of checking that the HTML file being
> used as part of an update operation has a mapping (id attributes) that
> match the docx file being updated (in the case of creating a new file, this
> is just an empty docx file). In the even that this is not the case, it
> could still do the update, but would act as if the entire document had been
> replaced with a completely new one.
>
> The solution I'll likely implement (and this should really be my first
> task, given the potential for problems like the above is this):
>
In my humble opinion you should not use time on this right now.

If you fix a bug we have a 1-1 relation (1 man used, 1 bug fixed)
If you start getting the documentation right we have a 1-n relations (1 man
used, n men help fix bugs).

Please have in mind, we build a community in order to move away from "I
have to do it, because I am the only one who know how" and you are the most
important enabler of that..we need your knowledge in a file, so that
others can work.

[ ... ]

When the project (hopefully) enters incubator, we will automatically have
access to a bug tracking system (jira), and with that hopefully only being
some month away I would not recommend setting up one now.


   On Github, there is already an issues structure, 
   .
   I think this should be continued in use until a different 
   setup arrives "any day soon".  Note that some Github projects 
   create a single subrepository that is just for its issues 
   function.  E.g., https://github.com/keybase/keybase-issues



[ ... ]



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: How to add generate symbols for gdb?

[Hung Mark]

Hi Ariel,



> > Do I have to build all with debug=t to in order to get symbolic tables?
> > What are the necessary and not necessary steps?
>
> Symbols might be stripped. Look at LinuxX86-64Env.Set.sh and make sure
> that
>
> ENABLE_SYMBOLS="TRUE"
> DISABLE_STRIP="TRUE"
>
>
My LinuxX86-64Env.Set.sh have these options turned on already.



> In theory, --enable-symbols should turn on --disable-strip-solver.
>
> > Please suggest. Thanks.
>
> Are you copying the libraries with debug symbols back in your
> installation? Or are you build the whole office and taking the
> installation from instsetoo_native?
>
>
Here is how I did:
After I build & deliver in the module, I go into instsetoo_native, then
build --all -P4 -- -P4
After that, I install all packages generated with dpkg -i.
Will it work this way?  They should work the same except my way takes
longer.


> It's better to move the installation from instsetoo_native to another
> place, build the needed modules with debug symbols, then copy the
>

What do you mean by moving instsetoo_native to another place?
I assume that you suggest this for preserving my original installation,
which may be not necessary for me because I work in VM that is built
exclusive for AOO.


> libraries back.
>
> In old dmake modules, for example sd
>
> cd sd
> build debug=true dbglevel=2 && deliver
> cp unxlngx6/lib/*.so /program/
>
>
> In make based modules, for example sw
>
> cd sw
> make -sr DEBUG=yes
> cp ../solver/420/unxlngx6/workdir/LinkTarget/Library/*sw*.so  installation>/program/
>
>
Great!  Copying those files is obviously faster than re-install debian
packages.
I will try to reconfigure and build it again with a cleaner environment.

Re: How to add generate symbols for gdb?

[Ariel Constenla-Haile]

On Sat, Aug 16, 2014 at 07:48:16AM +0800, Hung Mark wrote:
> Hi,
> 
> I tried to configure with --enable-symbols to build with symbolic
> generation.
> Here is my command line:
> 
> ./configure \
>  --with-dmake-url=
> http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2 \
>  --with-epm-url=
> http://www.msweet.org/files/project2/epm-3.7-source.tar.gz \
>  --disable-odk \
>  --disable-binfilter \
>  --with-lang="en-US zh-TW" \
>  --enable-symbols
> 
> Then in the module I wanted to debug, I built with
> 
> build debug=t dbglevel=0 && deliver
> 
> However gdb still told me that there was no debugging symbols found.
> 
> Do I have to build all with debug=t to in order to get symbolic tables?
> What are the necessary and not necessary steps?

Symbols might be stripped. Look at LinuxX86-64Env.Set.sh and make sure
that 

ENABLE_SYMBOLS="TRUE"
DISABLE_STRIP="TRUE"

In theory, --enable-symbols should turn on --disable-strip-solver.

> Please suggest. Thanks.

Are you copying the libraries with debug symbols back in your
installation? Or are you build the whole office and taking the
installation from instsetoo_native?


It's better to move the installation from instsetoo_native to another
place, build the needed modules with debug symbols, then copy the
libraries back.

In old dmake modules, for example sd

cd sd
build debug=true dbglevel=2 && deliver
cp unxlngx6/lib/*.so /program/


In make based modules, for example sw

cd sw
make -sr DEBUG=yes
cp ../solver/420/unxlngx6/workdir/LinkTarget/Library/*sw*.so /program/


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


signature.asc
Description: Digital signature

Re: DocFormats - Open source OOXML implementation

[Peter Kelly]

On 16 Aug 2014, at 12:55 pm, Andrea Pescetti  wrote:

> I've also been fixing (or breaking, who knows!) some documentation on my 
> clone (my "fork" as Github likes to call it) but I'll submit a pull request 
> only when basic things work.

I've just merged in your changes and also invited you as a committer to the 
repository. Then you'll be able to push directly to it instead of having to 
maintain your own fork.

I vote that we establish a policy of rebasing instead of merging in the general 
case (unless there's a good reason to do otherwise), as this will help maintain 
a mostly-linear history and avoid the annoyances described in [1]. That is, if 
before I push to the repository I see that the remote master has advanced (due 
to you or Jan committing something else), I'll rebase my commits on top of 
yours, so they look like they come "after" them in the history. Likewise, you 
and Jan would do the same if I've made commits. What do you think?

http://blog.spreedly.com/2014/06/24/merge-pull-request-considered-harmful

--
Dr. Peter M. Kelly
Founder, UX Productivity
pe...@uxproductivity.com
http://www.uxproductivity.com/
http://www.kellypmk.net/

PGP key: http://www.kellypmk.net/pgp-key
(fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966)



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: How to add generate symbols for gdb?

[Hung Mark]

No. Dbglevel=2 doesn't work.



2014-08-16 17:30 GMT+08:00 John O'Sullivan :

> Dbglevel=2 ?
> On 16 Aug 2014 00:48, "Hung Mark"  wrote:
>
> > Hi,
> >
> > I tried to configure with --enable-symbols to build with symbolic
> > generation.
> > Here is my command line:
> >
> > ./configure \
> >  --with-dmake-url=
> > http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2 \
> >  --with-epm-url=
> > http://www.msweet.org/files/project2/epm-3.7-source.tar.gz \
> >  --disable-odk \
> >  --disable-binfilter \
> >  --with-lang="en-US zh-TW" \
> >  --enable-symbols
> >
> > Then in the module I wanted to debug, I built with
> >
> > build debug=t dbglevel=0 && deliver
> >
> > However gdb still told me that there was no debugging symbols found.
> >
> > Do I have to build all with debug=t to in order to get symbolic tables?
> > What are the necessary and not necessary steps?
> > Please suggest. Thanks.
> >
> >
> > Best Regards
> >
>

Re: [VOTE]: Release Apache OpenOffice 4.1.1 (RC3)

[Jose R R]

Niltze, Jürgen-

I was about install ApacheOO 4.1.1 (RC3) but the sha256 do not match:

$ wget 
http://ci.apache.org/projects/openoffice/milestones/4.1.1-rc3-r1617669/binaries/en-US/Apache_OpenOffice_4.1.1_Linux_x86-64_install-deb_en-US.tar.gz.sha256

$ sha256sum -b  Apache_OpenOffice_4.1.1*gz
5121c9333b47bca9af71ca2f0dd41da463748a5cfb1a41eb8232284ad98323c2
*Apache_OpenOffice_4.1.1_Linux_x86-64_install-deb_en-US.tar.gz

$ cat Apache_OpenOffice_4.1.1_Linux_x86-64_install-deb_en-US.tar.gz.sha256
9624930a634891ed7ed6b2d19dd71303da1e900cf7ced56885f6d0bdceced4a9
*Apache_OpenOffice_4.1.1_Linux_x86-64_install-deb_en-US.tar.gz

Further:
$ wget https://people.apache.org/keys/group/openoffice.asc

$ wget 
http://ci.apache.org/projects/openoffice/milestones/4.1.1-rc3-r1617669/binaries/en-US/Apache_OpenOffice_4.1.1_Linux_x86-64_install-deb_en-US.tar.gz.asc

$ gpg --import openoffice.asc

$ gpg --verify Apache_OpenOffice_4.1.1_Linux_x86-64_install-deb_en-US.tar.gz.asc
gpg: Signature made Wed 13 Aug 2014 04:40:19 AM PDT using RSA key ID 51B5FDE8
gpg: BAD signature from "Juergen Schmidt "

Am I doing something incorrectly?


Best Professional Regards.


On Fri, Aug 15, 2014 at 12:15 AM, Jürgen Schmidt  wrote:
> Hi all,
>
> this is a call for vote on releasing the available release candidate
> (RC3) as Apache OpenOffice 4.1.1.
>
> Apache OpenOffice 4.1.1 is mainly a bugfix release with some important
> bugfixes. And we can provide again more complete UI translations and
> have now support for 41 languages. New languages for this release
> compared to 4.1.0 are Catalan, Catalan (Valencia AVL) and Catalan
> (Valencia RACV).
>
> Apache OpenOffice 4.1.1 is the continuation of high quality software
> releases.
>
> An overview of the integrated release issues can be found under:
>
> http://ci.apache.org/projects/openoffice/milestones/4.1.1-rc3-r1617669/AOO4.1.1_fixes.html
>
> The release candidate artifacts (source release, as well as binary
> releases for 41 languages) and further information how to verify and
> review Apache OpenOffice 4.1.1 can be found on the following wiki page:
>
> https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds
>
> (alternative directly via
> http://ci.apache.org/projects/openoffice/milestones/4.1.1-rc3-r1617669)
>
> *.dmg files are still not recognized as binaries and have to be
> saved manually (save link as ...).
>
> The RC is based on the release branch AOO410, revision 1617669! And a
> fresh and clean RAT scan output of this revision can be found under
>
> http://ci.apache.org/projects/openoffice/milestones/4.1.1-rc3-r1617669/AOO4.1.1_RAT_Scan.html
>
> Please vote on releasing this package as Apache OpenOffice 4.1.1
>
> The vote starts now and will be open until:
>
>Tuesday, 19 August: 2014-08-19 12:00am UTC+2.
>
> We invite all people to vote (non binding) on this RC. We would like
> to provide a release that is supported by the majority of our project
> members.
>
>[ ] +1 Release this package as Apache OpenOffice 4.1.1
>[ ]  0 Don't care
>[ ] -1 Do not release this package because...
>
> -
> To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: l10n-h...@openoffice.apache.org
>



-- 
Jose R R
http://www.metztli-it.com
-
NEW Apache OpenOffice 4.1.0! Download for GNU/Linux, Mac OS, Windows.
-
Daylight Saving Time in USA & Canada ends: Sunday, November 02, 2014
-

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: How to add generate symbols for gdb?

[John O'Sullivan]

Dbglevel=2 ?
On 16 Aug 2014 00:48, "Hung Mark"  wrote:

> Hi,
>
> I tried to configure with --enable-symbols to build with symbolic
> generation.
> Here is my command line:
>
> ./configure \
>  --with-dmake-url=
> http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2 \
>  --with-epm-url=
> http://www.msweet.org/files/project2/epm-3.7-source.tar.gz \
>  --disable-odk \
>  --disable-binfilter \
>  --with-lang="en-US zh-TW" \
>  --enable-symbols
>
> Then in the module I wanted to debug, I built with
>
> build debug=t dbglevel=0 && deliver
>
> However gdb still told me that there was no debugging symbols found.
>
> Do I have to build all with debug=t to in order to get symbolic tables?
> What are the necessary and not necessary steps?
> Please suggest. Thanks.
>
>
> Best Regards
>

Re: [VOTE]: Release Apache OpenOffice 4.1.1 (RC3)

[Software Valencià]

+1
El 2014/08/15 09:15, Jürgen Schmidt escrigué:

Hi all,

this is a call for vote on releasing the available release candidate
(RC3) as Apache OpenOffice 4.1.1.

Apache OpenOffice 4.1.1 is mainly a bugfix release with some important
bugfixes. And we can provide again more complete UI translations and
have now support for 41 languages. New languages for this release
compared to 4.1.0 are Catalan, Catalan (Valencia AVL) and Catalan
(Valencia RACV).

Apache OpenOffice 4.1.1 is the continuation of high quality software
releases.

An overview of the integrated release issues can be found under:

http://ci.apache.org/projects/openoffice/milestones/4.1.1-rc3-r1617669/AOO4.1.1_fixes.html

The release candidate artifacts (source release, as well as binary
releases for 41 languages) and further information how to verify and
review Apache OpenOffice 4.1.1 can be found on the following wiki page:

https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds

(alternative directly via
http://ci.apache.org/projects/openoffice/milestones/4.1.1-rc3-r1617669)

*.dmg files are still not recognized as binaries and have to be
saved manually (save link as ...).

The RC is based on the release branch AOO410, revision 1617669! And a
fresh and clean RAT scan output of this revision can be found under

http://ci.apache.org/projects/openoffice/milestones/4.1.1-rc3-r1617669/AOO4.1.1_RAT_Scan.html

Please vote on releasing this package as Apache OpenOffice 4.1.1

The vote starts now and will be open until:

Tuesday, 19 August: 2014-08-19 12:00am UTC+2.

We invite all people to vote (non binding) on this RC. We would like
to provide a release that is supported by the majority of our project
members.

[ ] +1 Release this package as Apache OpenOffice 4.1.1
[ ]  0 Don't care
[ ] -1 Do not release this package because...

-
To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org
For additional commands, e-mail: l10n-h...@openoffice.apache.org






-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: OO registrymodifications.xcu

[Rory O'Farrell]

On Sat, 16 Aug 2014 09:47:56 +0200
Andrea Pescetti  wrote:

> On 01/08/2014 Rory O'Farrell wrote:
> > A question has arisen on the en-Forum concerning file
> > registrymodifications.xcu
> > On a newly installed OpenOffice this starts off at about 22kb. Over time it 
> > grows
> 
> I have many of them (several different user profiles), peaking at ~290KB 
> for the version I use most often.
> 
> If I pass it through an XML pretty-printer (such as "xmllint --format") 
> I see many XML fragments about files that I opened: not only those 
> listed in recent documents, but hundreds of them, possibly every single 
> fine that I opened with this version. These XML fragments might explain 
> the constant growth.
> 
> Regards,
>Andrea.

Thanks for the further information, Andrea. The reason for asking is that one 
Forum Volunteer (John_Ha) has a suspicion that many of the occasional problems 
with OpenOffice which are cured by deleting or renaming the User Profile, 
thereby causing OO to generate a new default profile, could be cured equally 
well (and without loss of customisation) by simply reinstalling 
registrymodifications.xcu. Over time we may need to consider what purpose (if 
any) the "ancient" history stored in registrymodifications.xcu serves 

-- 
Rory O'Farrell 

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: DocFormats - Open source OOXML implementation

[jan i]

On 16 August 2014 03:50, Peter Kelly  wrote:

> On 16 Aug 2014, at 5:26 am, Andrea Pescetti  wrote:
>
> On 15/08/2014 Peter Kelly wrote:
>
> Those of you interested in OOXML may want to have a look at my own
> implementation of (a subset of) the spec, which is part of a library
> I've just made available as open source (license is ASLv2):
> https://github.com/uxproductivity/DocFormats
>
>
> It's very interesting. I hope that in future it may become relevant to
> OpenOffice or to Apache at large.
>
> The design is based on bidirectional transformation, as a way of
> achieving non-destructive editing of foreign file formats. This permits
> incremental implementation of a given spec without risking data loss due
> to incomplete features, since unsupported features of a given file
> format are left untouched on save.
>
>
> Does this mean that
> $ dfutil/dfutil filename.docx filename.html
> $ dfutil/dfutil filename.html filename2.docx
> should produce a "filename2.docx" that is quite similar to
> "filename.docx"? It is failing rather badly (invalid OOXML output in the
> second conversion, ZIP container clearly missing files and possible
> breaking order) in a simple test I did with a 1-page docx file.
>
>
> I'm not surprised this is the first issue to come up :$ There's a *lot* of
> knowledge I need to document for others; questions from you and others are
> the best way to motivate me to get that written ;)
>
> What's happening here is that when the filename.html produced in the first
> step, each of its elements contains an id attribute containing a numeric
> identifier that refers to a specific element in the source docx file
> (specifically, the word/document.xml file within the package). These
> numeric identifiers are generated during parsing, and correspond to the
> position of the element in document order (so 1, 2, 3, etc.). When you
> convert from HTML to .docx, it uses the id attributes to re-establish these
> relationships, so that it knows which elements in the HTML file correspond
> to which elements in the .docx file.
>
> The problem you encountered stems from the fact that this mapping is only
> valid in specific circumstances - that is, when the .docx file being
> updated is exactly the same as its original. If this is not the case, then
> the identifier assigned to a given node will different whenever there are
> other nodes that have been inserted between it. So for example if you do
> the following:
>
> dfutil filename.docx filename.html
> # Modify filename.html
> dfutil filename.html filename.docx
> dfutil filename.html filename.docx
>
> Then the third run will fail, because in the second the docx file will
> have been updated based on the changes in the HTML, changing the sequence
> numbers assigned to each node, and then on the second run the mapping will
> be valid. The conversion works on the assumption that the docx file is the
> same as the original. The way that UX Write uses the library, it ensures
> this is the case, but the library does not check for this (and yes, it
> should; more on this below).
>
> Your case is similar, though in this case you're creating a new docx file,
> not updating an existing one. However what it actually does in this case is
> to create an empty .docx file, and then "update" that based on the HTML. In
> doing so, it assumes that the HTML does not contain any mappings (that is,
> id attributes with the prefix "bdt"). Since the filename.html you generated
> does, it tries to map these to elements in the docx file, failing badly.
>
> The only workaround for this at present is to manually edit the HTML file
> and remove all id attributes. The quickest way to do this is with the
> following command:
>
> sed -i '' -E ' s/ id="word[0-9]+"//' filename.html
>
> Then, when you run dfutil, it will see that there is no mapping for any of
> the elements in the HTML file, and thus avoid the problems in the output
> you observed.
>
> Now, onto the fix:
>
> The library needs to have some way of checking that the HTML file being
> used as part of an update operation has a mapping (id attributes) that
> match the docx file being updated (in the case of creating a new file, this
> is just an empty docx file). In the even that this is not the case, it
> could still do the update, but would act as if the entire document had been
> replaced with a completely new one.
>
> The solution I'll likely implement (and this should really be my first
> task, given the potential for problems like the above is this):
>
In my humble opinion you should not use time on this right now.

If you fix a bug we have a 1-1 relation (1 man used, 1 bug fixed)
If you start getting the documentation right we have a 1-n relations (1 man
used, n men help fix bugs).

Please have in mind, we build a community in order to move away from "I
have to do it, because I am the only one who know how" and you are the most
important enabler of that..we need your knowledge in a file, so that
others can work.

Re: OO registrymodifications.xcu

[Andrea Pescetti]

On 01/08/2014 Rory O'Farrell wrote:

A question has arisen on the en-Forum concerning file
registrymodifications.xcu
On a newly installed OpenOffice this starts off at about 22kb. Over time it 
grows


I have many of them (several different user profiles), peaking at ~290KB 
for the version I use most often.


If I pass it through an XML pretty-printer (such as "xmllint --format") 
I see many XML fragments about files that I opened: not only those 
listed in recent documents, but hundreds of them, possibly every single 
fine that I opened with this version. These XML fragments might explain 
the constant growth.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org