Upstreaming FreeBSD ports patches before 4.2.0?
Hi Can we please upstream the patches from FreeBSD ports, before the 4.2.0 release? That idlc memory alignment SIGBUS crash from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216206 is Clang specific, not FreeBSD specific, and could happen on other operating systems. Thank you Damjan
Re: Minimum Ant version is now 1.9.1
Hi Damjan, Am 10.04.2018 um 13:46 schrieb Damjan Jovanovic: > I've also updated our Java policy wiki page with the new requirements: > https://wiki.openoffice.org/wiki/Policies/Java_Usage Is Java 1.7. a requirement of Ant >=1.9.1? I thought you mentioned Java 1.6 at some point as minimum. (Just asking and thinking of the OS/2 port) Regards, Matthias > > On Tue, Apr 10, 2018 at 1:20 PM, Matthias Seidel > wrote: >> Hi, >> >> Maybe we should set: >> >> ant_minver=1.7.0 >> >> in main/configure.ac to the new minimum version? >> >> Regards, >> >>Matthias >> >> >> Am 08.04.2018 um 14:59 schrieb Damjan Jovanovic: >>> Hi >>> >>> In porting main/jurt to gbuild in commits 1828636 and 1828638, I've ended >>> up doing considerable development in Ant, adding the ability to call IDL >>> tools (idlc, regmerge, javamaker) from Ant, and with the features I've >>> used, the minimum Ant version is now 1.9.1. >>> >>> Please let me know if you have any problems. >>> >>> Regards >>> Damjan >>> >> >> smime.p7s Description: S/MIME Cryptographic Signature
Re: Time to push on for 4.2.0
Jim Jagielski wrote: We then svn copy trunk to a AOO420 branch and start focusing on getting a 4.2.0 GA release out. On my side, this looks OK but localization is still lagging behind. Unless we deem it acceptable to get 4.2.0 out in English only (or with a significant percentage of English strings in the UI even for localized versions) this is still quite blocking, especially considering that there is an entire localization community that will need to be reactivated. Localization is, so to say, under my "ownership" (meaning: it's an area where I've volunteered to lead the effort); but I can't commit to getting it done by a certain deadline right now. Volunteers welcome, of course; even beginners. I do think we should try and get 4.2.0 out in all languages; but for a beta it would be acceptable to have English only, or incomplete translations. Localization doesn't have a big impact in terms of branches since what we have now is not aligned to the code anyway. And localization files live in their own directory so conflicts are not to be expected. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Time to push on for 4.2.0
Hi Andrea, Am 14.04.2018 um 15:31 schrieb Andrea Pescetti: > Jim Jagielski wrote: >> We then svn copy trunk to a AOO420 branch and >> start focusing on getting a 4.2.0 GA release out. > > On my side, this looks OK but localization is still lagging behind. > > Unless we deem it acceptable to get 4.2.0 out in English only (or with > a significant percentage of English strings in the UI even for > localized versions) this is still quite blocking, especially > considering that there is an entire localization community that will > need to be reactivated. > > Localization is, so to say, under my "ownership" (meaning: it's an > area where I've volunteered to lead the effort); but I can't commit to > getting it done by a certain deadline right now. Volunteers welcome, > of course; even beginners. You can count on me. But at the moment I am having troubles with po2oo or better how to get the en-US template. ;-) BTW: I managed to build Arabic and Ukrainian for Windows. There were problems with packaging (NSIS). I could work around it, but am still looking for a "real" solution... Regards, Matthias > > I do think we should try and get 4.2.0 out in all languages; but for a > beta it would be acceptable to have English only, or incomplete > translations. > > Localization doesn't have a big impact in terms of branches since what > we have now is not aligned to the code anyway. And localization files > live in their own directory so conflicts are not to be expected. > > Regards, > Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Time to push on for 4.2.0
> Localization is, so to say, under my "ownership" (meaning: it's an area > where I've volunteered to lead the effort); but I can't commit to > getting it done by a certain deadline right now. Volunteers welcome, of > course; even beginners. I have previously volunteered to get the Portuguese version ready for release. I am volunteering again. Is there any work to be done on Pootle? Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Time to push on for 4.2.0
Hi Pedro, Am 14.04.2018 um 16:32 schrieb Pedro Lino: >> Localization is, so to say, under my "ownership" (meaning: it's an area >> where I've volunteered to lead the effort); but I can't commit to >> getting it done by a certain deadline right now. Volunteers welcome, of >> course; even beginners. > I have previously volunteered to get the Portuguese version ready for release. > I am volunteering again. > Is there any work to be done on Pootle? There is always something to improve on Pootle. ;-) But that's not the point here: We need to get Pootle and the source code in sync again. After that is done, there will be *a lot* of work to be done on Pootle... Regards, Matthias > > Regards, > Pedro > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Upstreaming FreeBSD ports patches before 4.2.0?
On 14 Apr, Damjan Jovanovic wrote: > Hi > > Can we please upstream the patches from FreeBSD ports, before the 4.2.0 > release? > > That idlc memory alignment SIGBUS crash from > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216206 is Clang specific, > not FreeBSD specific, and could happen on other operating systems. That one is a bit complicated to upstream. In the FreeBSD port I only apply the patch conditionally when building with recent clang on amd64. I could be harmful in terms of memory consumption on 32-bit machines. The changes in the patch would need to be #ifdefed in order to import it. Also the changes for the internal allocator are lightly tested at best. https://svnweb.freebsd.org/ports/head/editors/openoffice-devel/files/extra-patch-align16?revision=432895&view=markup - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Help Needed
Hi; I have used your open office program for quite a few years with no problems. Last week I am not sure what happened but all of my saved documents have just disappeared. I really need your help to get them back as I use them for my work and photos. Can someone please get back to me as soon as possible so we can figure out what happened. I did not do anything new with the computer or add any new programs so cannot explain or figure out what happened to make all my documents just gone! Donnell -- Donnell Giambastiani (916) 878-6590 www.annamaet.com www.veruspetfoods.com www.fleago.com www.realmeatpet.com www.answerspetfood.com www.gentletouchproducts.com - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Help Needed
On Sat, 14 Apr 2018 12:51:32 -0700 Donnell Giambastiani wrote: > Hi; > I have used your open office program for quite a few years with > no problems. Last week I am not sure what happened but all of my saved > documents have just disappeared. I really need your help to get them > back as I use them for my work and photos. > > Can someone please get back to me as soon as possible so we can figure > out what happened. I did not do anything new with the computer or add > any > new programs so cannot explain or figure out what happened to make all > my > documents just gone! > > Donnell Your documents are still on the computer, in the directory in which they were saved. What has happened is that OpenOffice has lost the list of shortcuts to these documents, possibly due to a computer or program crash, or to an over-hasty power off of the computer before the internal housekeeping had been finally written to disk. If you use /File /Open to navigate to the directory n which you saved these documents, as you select each one and open it, it will then appear on the recent Documents list. -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Upstreaming FreeBSD ports patches before 4.2.0?
Alright thank you. Would it be better to just scrap cpprt, like gbuild modules already do? On Sat, Apr 14, 2018 at 4:59 PM, Don Lewis wrote: > On 14 Apr, Damjan Jovanovic wrote: > > Hi > > > > Can we please upstream the patches from FreeBSD ports, before the 4.2.0 > > release? > > > > That idlc memory alignment SIGBUS crash from > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216206 is Clang > specific, > > not FreeBSD specific, and could happen on other operating systems. > > That one is a bit complicated to upstream. In the FreeBSD port I only > apply the patch conditionally when building with recent clang on amd64. > I could be harmful in terms of memory consumption on 32-bit machines. > The changes in the patch would need to be #ifdefed in order to import > it. > > Also the changes for the internal allocator are lightly tested at best. > > https://svnweb.freebsd.org/ports/head/editors/openoffice- > devel/files/extra-patch-align16?revision=432895&view=markup > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: Minimum Ant version is now 1.9.1
Ant 1.9.x only needs Java 1.5, but the code I've written for the SDBC-JDBC bridge and PostgreSQL database driver needs Java 1.7. On Sat, Apr 14, 2018 at 1:13 PM, Matthias Seidel wrote: > Hi Damjan, > > Am 10.04.2018 um 13:46 schrieb Damjan Jovanovic: > > I've also updated our Java policy wiki page with the new requirements: > > https://wiki.openoffice.org/wiki/Policies/Java_Usage > > Is Java 1.7. a requirement of Ant >=1.9.1? > > I thought you mentioned Java 1.6 at some point as minimum. > (Just asking and thinking of the OS/2 port) > > Regards, >Matthias > > > > > On Tue, Apr 10, 2018 at 1:20 PM, Matthias Seidel < > matthias.sei...@hamburg.de > >> wrote: > >> Hi, > >> > >> Maybe we should set: > >> > >> ant_minver=1.7.0 > >> > >> in main/configure.ac to the new minimum version? > >> > >> Regards, > >> > >>Matthias > >> > >> > >> Am 08.04.2018 um 14:59 schrieb Damjan Jovanovic: > >>> Hi > >>> > >>> In porting main/jurt to gbuild in commits 1828636 and 1828638, I've > ended > >>> up doing considerable development in Ant, adding the ability to call > IDL > >>> tools (idlc, regmerge, javamaker) from Ant, and with the features I've > >>> used, the minimum Ant version is now 1.9.1. > >>> > >>> Please let me know if you have any problems. > >>> > >>> Regards > >>> Damjan > >>> > >> > >> > > >
