4.2.0 unable open .docx (Was Re: Latest test builds)

2019-01-21 Thread Rory O'Farrell
On Mon, 21 Jan 2019 08:39:23 +0100 Peter Kovacs wrote: > Hi Rory, > > do we have a Bug for this? > > > All the Best > > Peter I have not yet raised this as a bug - will do later today when a current serious crisis (don't ask!) is dealt with. This has independently been brought to the en-

Re: Latest test builds

2019-01-21 Thread Rory O'Farrell
On Mon, 21 Jan 2019 08:39:23 +0100 Peter Kovacs wrote: > Hi Rory, > > do we have a Bug for this? > > > All the Best > > Peter Seems to be bug 115156 I have added my earlier information to that bug. Rory > > On 20.01.19 17:45, Rory O'Farrell wrote: > > On Sun, 20 Jan 2019 10:28:53 -0500 >

Re: Latest test builds

2019-01-21 Thread Matthias Seidel
Hi Rory, Am 21.01.19 um 15:29 schrieb Rory O'Farrell: > On Mon, 21 Jan 2019 08:39:23 +0100 > Peter Kovacs wrote: > >> Hi Rory, >> >> do we have a Bug for this? >> >> >> All the Best >> >> Peter > > Seems to be bug 115156 > I have added my earlier information to that bug. Can you please attach a

Re: Latest test builds

2019-01-21 Thread Rory O'Farrell
On Mon, 21 Jan 2019 16:09:33 +0100 Matthias Seidel wrote: > Hi Rory, > > Am 21.01.19 um 15:29 schrieb Rory O'Farrell: > > On Mon, 21 Jan 2019 08:39:23 +0100 > > Peter Kovacs wrote: > > > >> Hi Rory, > >> > >> do we have a Bug for this? > >> > >> > >> All the Best > >> > >> Peter > > > > Seems t

Re: Latest test builds

2019-01-21 Thread Matthias Seidel
Am 21.01.19 um 16:18 schrieb Rory O'Farrell: > On Mon, 21 Jan 2019 16:09:33 +0100 > Matthias Seidel wrote: > >> Hi Rory, >> >> Am 21.01.19 um 15:29 schrieb Rory O'Farrell: >>> On Mon, 21 Jan 2019 08:39:23 +0100 >>> Peter Kovacs wrote: >>> Hi Rory, do we have a Bug for this? >>

Re: Latest test builds

2019-01-21 Thread Patricia Shanahan
On 1/21/2019 7:37 AM, Matthias Seidel wrote: Am 21.01.19 um 16:18 schrieb Rory O'Farrell: On Mon, 21 Jan 2019 16:09:33 +0100 Matthias Seidel wrote: Hi Rory, Am 21.01.19 um 15:29 schrieb Rory O'Farrell: On Mon, 21 Jan 2019 08:39:23 +0100 Peter Kovacs wrote: Hi Rory, do we have a Bug f

Re: Latest test builds

2019-01-21 Thread Jim Jagielski
I'm in the process of uploading Linux 32bit builds > On Jan 20, 2019, at 10:28 AM, Jim Jagielski wrote: > > I've uploaded the latest test builds for macOS and Linux 64. > These are based on ~r1851640 and include 2 main updates from > the earlier one: > > o beanshell now included > o macOS path

Re: Latest test builds

2019-01-21 Thread Rory O'Farrell
On Mon, 21 Jan 2019 16:37:17 +0100 Matthias Seidel wrote: > Am 21.01.19 um 16:18 schrieb Rory O'Farrell: > > On Mon, 21 Jan 2019 16:09:33 +0100 > > Matthias Seidel wrote: > > > >> Hi Rory, > >> > >> Am 21.01.19 um 15:29 schrieb Rory O'Farrell: > >>> On Mon, 21 Jan 2019 08:39:23 +0100 > >>> Peter

branch 4.1.7?

2019-01-21 Thread Jim Jagielski
Does it make sense to create a branch of 4.1.7 from 4.1.6...? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: branch 4.1.7?

2019-01-21 Thread Rory O'Farrell
On Mon, 21 Jan 2019 11:12:12 -0500 Jim Jagielski wrote: > Does it make sense to create a branch of 4.1.7 from 4.1.6...? No, unless for some urgent fix. I think better to continue with 4.2.0, then on to 5.0 4.2.0 editing OK in Writer (60k word file, book format, no illustrations/tables). A s

Re: branch 4.1.7?

2019-01-21 Thread Jim Jagielski
Gotcha. I was just thinking that if we had a 4.1.7 branch in a ready-to-go stage, if we needed to do another 4.1.x release it would be already there. But agree that the focus should be on 4.2.0 > On Jan 21, 2019, at 11:25 AM, Rory O'Farrell wrote: > > On Mon, 21 Jan 2019 11:12:12 -0500 > Jim J

Re: branch 4.1.7?

2019-01-21 Thread Patricia Shanahan
I agree that the focus should be on 4.2.0. However, I strongly favor having a ready-to-go 4.1.7. Any day, we could encounter a really serious, must-fix-immediately, security bug. Having as much as possible done ahead of time will reduce the delay from knowing the fix to end users having the fix

Navigator query

2019-01-21 Thread Rory O'Farrell
Can anyone tell me if, in the AOO code, there is a module for Navigator? If so, which module is it? My thinking is that Navigator could do with some additions, such as ability to display the word count for Chapters (helpful for an author to tweak his chapter lengths to be roughly the same), an

Re: branch 4.1.7?

2019-01-21 Thread F C. Costero
One "regression" that merits immediate attention is crashing on Windows when trying to edit a macro embedded in a Writer or Calc document ( I haven't checked Impress or Base yet). If I open a new document and try to make an embedded macro (menus Tools -> Macros -> Organize Macros -> OpenOffice Bas

Re: Navigator query

2019-01-21 Thread Damjan Jovanovic
Hi Here's how I found it: View -> Navigator to open the window. Look for the most complex unique text there, eg. "Heading Levels Shown" in a tooltip. Go to https://opengrok.libreoffice.org and search for "Heading Levels Shown" under full-text search. It finds 2 matches: core/sw/uiconfig/swrite

Re: Navigator query

2019-01-21 Thread Rory O'Farrell
On Mon, 21 Jan 2019 19:40:24 +0200 Damjan Jovanovic wrote: > Hi > > Here's how I found it: > > View -> Navigator to open the window. > > Look for the most complex unique text there, eg. "Heading Levels Shown" in > a tooltip. > > Go to https://opengrok.libreoffice.org and search for "Heading L

Re: branch 4.1.7?

2019-01-21 Thread Jim Jagielski
I'll just go ahead and create a branch. They are cheap. And, at least, we'll have a branch ready in case we need it. If not, no big deal. > On Jan 21, 2019, at 11:38 AM, Patricia Shanahan wrote: > > I agree that the focus should be on 4.2.0. However, I strongly favor having a > ready-to-go 4.1