OOXML
For information: http://www.themukt.com/2014/07/31/never-use-microsofts-ooxml-format/ -- Rory O'Farrell ofarr...@iol.ie - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: [RELEASE]: RC1 is available
Thank you for alerting us to this release. I will do some testing to ensure that we still have screen reader accessibility. I have access to the latest versions of JAWS and Window-eyes and I have NVDA on my home system. I would be happy to be of service to perform any accessibility testing which may prove helpful. -Original Message- From: Jürgen Schmidt [mailto:jogischm...@gmail.com] Sent: Friday, August 01, 2014 1:49 AM To: dev; q...@openoffice.apache.org; l...@openoffice.apache.org Subject: [RELEASE]: RC1 is available Hi, I would like to inform that AOO 4.1.1 RC1 is available for testing. The RC is based on revision 1614049 of branch AOO410. The builds can be found as always under [1]. An overview of fixed issues can be found under [2]. With this release we will have 3 new languages Catalan (ca), Catalan (Valencia RACV, ca-XR) and Catalan (Valencia AVL, ca-XV). AOO 4.1.1 is now available in 41 languages where the UI is 100% translated. Many thanks to all volunteers Please help us to improve the quality and test the RC in detail. Any kind of feedback is welcome and highly appreciated. Kind regards Juergen [1] https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds [2] http://ci.apache.org/projects/openoffice/milestones/4.1.1-rc1-r1614049/AOO4.1.1_fixes.html - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Building OpenOffice on illumos with gcc
Hello. I've just integrated OpenOffice component into OpenIndiana /hipster illumos distribution. I'd like to share some patches and to ask if they could be converted to bug reports, feature requests and which of them can be integrated. OpenIndiana distribution tries to be compatible with Solaris 11. However, there are several distinctions, the main one is system compiler. We use gcc (4.8) with illumos (former Sun Solaris) linker instead of Sun Studio. The work I've made was based on earlier work of Apostolos Syropoulos, which he described here: https://asyropoulos.wordpress.com/2014/02/05/compiling-openoffice4/ . The full component is available here: https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/openoffice/openoffice . And patches are in patches subdirectory: https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/openoffice/openoffice/patches . I had to make about 20 changes. 01.use-illumos-ld.patch OpenOffice configure script doesn't like illumos ld and GCC on Solaris, so I relaxed this restriction. 02.use-gcc.patch Patches to main solenv/* make files are mostly taken from Apostolos blog (perhaps, with some corrections) and IIRC are based on Linux makefiles. They are necessary to introduce Solaris/GCC platform. 03.g++-includes.patch Our boost live in /usr/g++, so we have to teach OpenOffice to search it there. We can't use CPPFLAGS, because this breaks icu compilation. It would be perfect if we can provide boost path with configure switch. 04.gmake-j.patch dmake is supposed to call gmake in several cases. But sometimes it calls dmake or make and it doesn't like -j flags. Don't know why it happens. So I just had to remove -j flags. 05.visibility.patch Without this patch some symbols are hidden during sc compilation. 06.ignore_mapfiles.patch Some mapfiles introduce symbols which are not present in OpenIndiana. 07.cstring.patch Missing cstring includes. 08.adsyms.awk.patch Complements 06.ignore_mapfiles.patch. _ZTI* symbols are not present in result libraries. 09.libxmlsec-ldflags.patch LDFLAGS are not passed during libxmlsec build 10.xinerama.patch Two issues - 1) saldisp defines MAXFRAMEBUFFERS only for XSUN. 2) neither USE_XINERAMA_XORG nor USE_XINERAMA_XSUN are defined. 11.wmadaptor-gcc48.patch It seems just gcc 4.8 doesn't like const_castchar*(pText) construction. 12.undefine-macroses.patch Some symbols used by OpenOffice are defined in our headers. Undefine them. 13.remove-studio-specific.patch Studio flags are unconditionally passed to the compiler. Fix this. 14.webdav-apr.patch On OpenIndiana we have /usr/apr/include, not /usr/include/apr. Also runpaths for APR and APR-UTIL are missing. Perhaps, adding some switch to set apr/apr-util runpath and include header.h instead of apr/header.h would help here. 15.icu.patch (in fact, patch to patch :)) There are two issues. 1) in uperf.cpp _XOPEN_SOURCE_EXTENDED is defined. This hides some symbols on Solaris/illumos. So, we don't receive _XPG6 and get an error Compiler or options invalid for pre-UNIX 03 X/Open applications \ and pre-2001 POSIX applications There's no need to define this guard on illumos. 2) We should add runpath to binaries, else compiling icu is linked to system icu in /usr/lib (compiled with Studio) and we receive binaries which are linked to both Studio and GCC C++ runtime simultaneously. 16.lstdc++.patch Binaries are unconditionally linked to lCstd on Solaris. Fix this. 17.nss.patch OpenOffice has hardcoded paths for nss libraries and headers. Set paths to our paths. One more time when having configure switch is desirable. 18.sal_osl_unx.patch 1) One more define supposing that the only Solaris compiler is Studio 2) We (as MACOSX) also have posix_madvise (just cutpaste Apostolos' change, don't know, why usual madvise fails to work, perhaps, missing headers). Post-install processing: bootstraprc has incorrect UserInstallation setting and tries to write user configs to installation directory (fix was taken from FreeBSD port). Alsoe some binaries have incorrect runpaths. Fix this. -- Best regards, Alexander Pyhalov, system administrator of Computer Center of Southern Federal University - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Building OpenOffice on illumos with gcc
On Fri, Aug 1, 2014 at 11:27 AM, Alexander Pyhalov a...@rsu.ru wrote: Hello. I've just integrated OpenOffice component into OpenIndiana /hipster illumos distribution. I'd like to share some patches and to ask if they could be converted to bug reports, feature requests and which of them can be integrated. This is great news. OpenIndiana distribution tries to be compatible with Solaris 11. However, there are several distinctions, the main one is system compiler. We use gcc (4.8) with illumos (former Sun Solaris) linker instead of Sun Studio. The work I've made was based on earlier work of Apostolos Syropoulos, which he described here: https://asyropoulos.wordpress.com/2014/02/05/compiling-openoffice4/ . We would need Apostolos to agree to contribute under the Apache License 2.0 as well, since this is based on his work. (Or did he already contribute the patches from his blog?) For example, it would be fine if he just sent a note to the mailing list, pointing to the blog posts, and saying that he contributes them to the AOO project under the Apache License 2.0. Thanks! -Rob The full component is available here: https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/openoffice/openoffice . And patches are in patches subdirectory: https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/openoffice/openoffice/patches . I had to make about 20 changes. 01.use-illumos-ld.patch OpenOffice configure script doesn't like illumos ld and GCC on Solaris, so I relaxed this restriction. 02.use-gcc.patch Patches to main solenv/* make files are mostly taken from Apostolos blog (perhaps, with some corrections) and IIRC are based on Linux makefiles. They are necessary to introduce Solaris/GCC platform. 03.g++-includes.patch Our boost live in /usr/g++, so we have to teach OpenOffice to search it there. We can't use CPPFLAGS, because this breaks icu compilation. It would be perfect if we can provide boost path with configure switch. 04.gmake-j.patch dmake is supposed to call gmake in several cases. But sometimes it calls dmake or make and it doesn't like -j flags. Don't know why it happens. So I just had to remove -j flags. 05.visibility.patch Without this patch some symbols are hidden during sc compilation. 06.ignore_mapfiles.patch Some mapfiles introduce symbols which are not present in OpenIndiana. 07.cstring.patch Missing cstring includes. 08.adsyms.awk.patch Complements 06.ignore_mapfiles.patch. _ZTI* symbols are not present in result libraries. 09.libxmlsec-ldflags.patch LDFLAGS are not passed during libxmlsec build 10.xinerama.patch Two issues - 1) saldisp defines MAXFRAMEBUFFERS only for XSUN. 2) neither USE_XINERAMA_XORG nor USE_XINERAMA_XSUN are defined. 11.wmadaptor-gcc48.patch It seems just gcc 4.8 doesn't like const_castchar*(pText) construction. 12.undefine-macroses.patch Some symbols used by OpenOffice are defined in our headers. Undefine them. 13.remove-studio-specific.patch Studio flags are unconditionally passed to the compiler. Fix this. 14.webdav-apr.patch On OpenIndiana we have /usr/apr/include, not /usr/include/apr. Also runpaths for APR and APR-UTIL are missing. Perhaps, adding some switch to set apr/apr-util runpath and include header.h instead of apr/header.h would help here. 15.icu.patch (in fact, patch to patch :)) There are two issues. 1) in uperf.cpp _XOPEN_SOURCE_EXTENDED is defined. This hides some symbols on Solaris/illumos. So, we don't receive _XPG6 and get an error Compiler or options invalid for pre-UNIX 03 X/Open applications \ and pre-2001 POSIX applications There's no need to define this guard on illumos. 2) We should add runpath to binaries, else compiling icu is linked to system icu in /usr/lib (compiled with Studio) and we receive binaries which are linked to both Studio and GCC C++ runtime simultaneously. 16.lstdc++.patch Binaries are unconditionally linked to lCstd on Solaris. Fix this. 17.nss.patch OpenOffice has hardcoded paths for nss libraries and headers. Set paths to our paths. One more time when having configure switch is desirable. 18.sal_osl_unx.patch 1) One more define supposing that the only Solaris compiler is Studio 2) We (as MACOSX) also have posix_madvise (just cutpaste Apostolos' change, don't know, why usual madvise fails to work, perhaps, missing headers). Post-install processing: bootstraprc has incorrect UserInstallation setting and tries to write user configs to installation directory (fix was taken from FreeBSD port). Alsoe some binaries have incorrect runpaths. Fix this. -- Best regards, Alexander Pyhalov, system administrator of Computer Center of Southern Federal University - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OO registrymodifications.xcu
Hi Rory, good question. Mine's got 787 KB. Max Am 01.08.2014 17:54, schrieb Rory O'Farrell: 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 (and grows...) I'm looking at one that is 386kb and have had reports of one that nears 500kb. In addition to the various housekeeping settings for the new installation of OO, is it necessary that it should continue to grow? Can someone please enlighten me about this? (A brief explanation will be adequate!) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Updated download stats
I've updated our stats page with the data for July: http://www.openoffice.org/stats/downloads.html The new total is 112,491,971. I'd expect a big pickup in volume in a few weeks, as students start returning to school. I wonder if a student-focused blog post might be good? For example, post on The Top 10 OpenOffice Templates for Students or something like that? Regards, -Rob - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: Building OpenOffice on illumos with gcc
We would need Apostolos to agree to contribute under the Apache License 2.0 as well, since this is based on his work. (Or did he already contribute the patches from his blog?) For example, it would be fine if he just sent a note to the mailing list, pointing to the blog posts, and saying that he contributes them to the AOO project under the Apache License 2.0. Hello, Of course I agree to include in the source tree anything you think is useful. So please go ahead and include these patches. Best regards, Apostolos -- Apostolos Syropoulos Xanthi, Greece
opengrok.adfinis-sygroup.org unavailable
Hi all, I cannot get http://opengrok.adfinis-sygroup.org/ returns Service Temporarily Unavailable But that is already some time so. Does someone know, what to do in those cases? Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Missing features
Dear developers, If I had any programming ability, I would try to create two features that would help me immensely when I use Open Office Writer. First, the program really needs a double indent command. This would be to indent both the left and right margins equally by pressing a single button. This would be repeatable. Word has this feature; WordPerfect has this feature; Writer does not have this feature. It is very important to anyone writing or translating scholarly documents, especially if the cannot afford to buy one of the paying suites. I believe that the absence of this feature is costing you a significant segment of your audience. Second, it is possible to format text in small capital letters, but it is tedious. I think this could also be reduced to a single button click. While I am no programmer, I would think that, if you can create a single-click hanging indent, you should be able to create a single-click small caps command. It would be nice to have this as a button that could be added to a toolbar. Even putting it in a fonts box would be helpful. Thank-you! Despite these two minor lacunae in the program, I enjoy using Open Office Writer. Please continue the good work. Best, Joe Henderson Ann Arbor, MI
