Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Hello Pieter,

Pieter E. Zanstra wrote (18-04-11 21:40)

I am either posting to the wrong list, or apparantly there are no
supporters to get this problem fixed. PZ

[ snip ]

That set aside, the fact of the matter is that maintaining a company
style in Writer tables is a rather tedious chore. I maintain a couple
of 1000+ page documents which contain many tables. For this type and
size of document, Writer is superb over the "competition". There is
however one but...

That is the lack of table styles. I tried as a work around to apply a
user defined autoformat to all tables. But unfortunately there is a
bug in autoformats. Back in 20008 this bug has already been reported
to the OOo community

[ snip ]

I have discussed this issue directly with two core actors in the Libo
community who bot advised me to post the problem on this list.
Unfortunately I am not a programmer, so I can not solve this myself.
I can offer my time for thoroughly testing any early or late
implementations that solve this problem.

For me the solution is not necessarily in fixing the table
autoformats. A more principled solution using table styles or table
cell styles (
would be great. I would appreciate that solving this issue would get
a higher priority than it presently has.

Thanks for (again) posting. I saw your initial message too. And yes, I too think it would be fine to have a better solution then the current one.

However, it is not easy to predict how the issue will be picked up.

1st, you have to get attention.
You did that. The fact that you do not get replies, does not imply that your mail is not noticed.

2nd. Since developers are busy and the list with wishes, needs etc is loooong, bringing is your own developing capacity is best guaranty that the problem will be solved.
Ok, you are not a developer, but offer to help.
Maybe you could try to find a developer who can work (start working) on it? Maybe via a bounty? Or find some funding, ... Since the development process of LibreOffice is really open, it could also help solving the issue if you were able to get an initial technical description, or a start of a patch done. That will raise attention and make it easier for others to step in.

We will have a 2nd LibreOffice Hackers event in The Netherlands, probably early June, and I'll be glad to bring the issue to the attention of the people. But I cannot make any promise wrt interest of people, if it fits in their skills and time available etc. But .. who knows ;-)

Hope this helps a bit, maybe you or someone else can continue with one of the ideas.

Kind regards,

 - giving its foundation :: The Document Foundation -

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.