Re: [tdf-discuss] RE: Concerned about Table formatting in Writer

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
> (http://openoffice.org/bugzilla/show_bug.cgi?id=94630).
>
> [ 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 (https://bugs.freedesktop.org/show_bug.cgi?id=34391)
> 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,
Cor

--
 - http://nl.libreoffice.org
 - giving openoffice.org its foundation :: The Document Foundation -


--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted