Re: [PROPOSAL] Do not drop languages in minor releases
On 4/30/14 12:28 AM, Marcus (OOo) wrote: Am 04/29/2014 07:57 PM, schrieb Rob Weir: On Tue, Apr 29, 2014 at 1:47 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 04/29/2014 09:47 AM, schrieb jan i: On 29 April 2014 09:36, Jürgen Schmidtjogischm...@gmail.com wrote: On 4/29/14 9:20 AM, Tal Daniel wrote: On Tue, Apr 29, Andrea Pescetti wrote: I propose that, once a language reaches our release quality criteria (currently: UI translation at 100% and maintained), we do not drop it afterwards for the other minor releases. [...] I would remove unmaintained languages only when version 5.0 comes. Seems reasonable, to me, Andrea, I'm not sure that removing a language on major release should be so strict. What about removing a language only when a MINIMUM% of it isn't translated (e.g., 10%)? we had something like this before but defined a new rule to be 100% UI complete and I think this is quite easy and a good rule. The case Andrea described above should be more theoretical if an active community is behind a translation. We released Arabic with 3.4 but there was no active community and nothing happened later on. I would still prefer the 100% rule. But anyway it's my personal opinion. +1, not requiring 100% UI (which is quite easy to do for any translator) is a dangerous path. Nobody can today say when we do the next major release (5.x) meaning translations 100% could be ongoing for a long period. For a minor release, its typically only a handful of messages that are changed, so it not a big workload for any individual. However, from the view point of a normal user who just wants to update to the next version, it would be confusing why no localized install file is available anymore. So, from my side a clear +1 to keep these languages. How much we allow to be under 100% is just a question of definition (and agreement). ;-) We want quality releases. % translation is part of quality, of course. But there are other aspects as well. Certainly looking at % completeness is easy for to measure, but it is not necessarily the best criterion. We want to avoid a situation where a translation is rushed and done poorly, in order to meet an arbitrary % goal. I'd rather have a high quality 95% than a low quality 100%. You should have replied to my other mail. ;-) It seems we have the same direction of the vision. Of course, PMC members do not know all languages. So we need to rely on the translators and the local community. Maybe we can make a criterion from that? For example: If a translation is more than X% complete, AND if that language was downloaded in the beta release more than Y times, AND the RC was reviewed by the translator and Z other community members to vouch for having usable level of quality, then we include it in a release. Yes, sounds good. Or some other way of having the local community take ownership of making this decision. What about to include another AND: AND ZZ the language has recent activity on Pootle. Even when the language is a bit far away from 100%, with activity on Pootle we can be sure (somehow) that the language is maintained. we should first streamline the process and have a better integration process in place. Currently I am doing all then work but I am not interested in doing more. I will continue to integrate new languages and merge language back from time to time but better would be if genlang can be finished (and I am sure Jan needs help here and volunteers are welcome) or somebody else steps up to support me ;-) Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE] urgent request - activation of Update Notification for our AOO 4.1.0 release
Hi, On 29.04.2014 14:58, Rob Weir wrote: On Tue, Apr 29, 2014 at 8:12 AM, Oliver-Rainer Wittmann orwittm...@googlemail.com wrote: Hi, On 29.04.2014 14:09, Oliver-Rainer Wittmann wrote: Hi, I am in preparation of the activation of the update notification for our AOO 4.1.0 release for installed OpenOffice instances - versions 3.2.0, 3.2.1, 3.3.0, 3.4.0, 3.4.1, 4.0.0 and 4.0.1 Here is the list of the languages whose users will be guided to a localized website from the update notification in OpenOffice: - Czechhttp://www.openoffice.org/cs/download - Germanhttp://www.openoffice.org/de - Spanishhttp://www.openoffice.org/es/descargar - Frenchhttp://www.openoffice.org/fr/Telecharger - Italianhttp://www.openoffice.org/it/download - Japanesehttp://www.openoffice.org/ja/download - Dutchhttp://www.openoffice.org/nl/downloaden.html - Portuguese (European)http://www.openoffice.org/pt - Slovakhttp://www.openoffice.org/sk/download - Turkishhttp://www.openoffice.org/tr - Chinese (simplified)http://www.openoffice.org/zh-cn - Chinese (traditional)http://www.openoffice.org/zh-tw As far as I can see the websites for the following languages need an update for AOO 4.1.0 - French While written the initial post, Rob has made an update for the French website. Please review the made changes. I also updated the Japanese and Finnish websites, languages I know even more poorly than French. Thanks Rob. I will get my hands on the Dutch website. Please review the changes which I will make. Best regards, Oliver. I did this based on Google Analytics which showed a large number of downloads of 4.0.1 still in these languages. -Rob Best regards, Oliver. - Japanese - Dutch Request to all native speakers of the above languages: - Please have a look, if the localilzed website is ok. - Please update the localized website, if needed - esp. for French, Japanese and Dutch My plan is to go live with the update notification for AOO 4.1.0 tomorrow early afternoon (14:00 UTC+2). Please leave my a note, if the one or the other localized website should be dropped or kept for the update notification. Thanks in advance. Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[RELEASE]: missing Linux 64 bit language packs in AOO 4.1
Hi, I noticed that the Linux 64 bit language packs are missing in the AOO 4.1 release. I am currently pushing them on dist and SF to be available later. I am wondering why nobody have noticed this before. Because of a typo in my scripts they were not available in the RC builds as well and nobody have noticed this. Well they are for convenience only but I am still wondering. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Server status: What's Up; What's Down?
on Tuesday, April 29, 2014 10:10 PM Marcus (OOo) wrote: FYI The CMS builder is down again. When clicking on the [Follow Staging Build] link in CMS, I come to http://ci.apache.org/builders/ooo-site-site-staging; and the error message 503 Service Unavailable. The status montioring webpage tells the same for the aegis server. I just (30.04.2014 09:00 MESZ) the page: http://www.openoffice.org/de/ edited (a space character added), it worked. Greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[RELEASE]: kid language packs for AOO 4.1.0
Hi, I have uploaded kid language packs for AOO 4.1.0 under http://people.apache.org/~jsc/releases/4.1.0/kid_langpack/ I hope you can use them to improve the translation where necessary or to identify easier where the string have to be searched in Pootle. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE] urgent request - activation of Update Notification for our AOO 4.1.0 release
V Utorok, 29. apríl 2014 o 14:09 +0200, Oliver-Rainer Wittmann napísal(a): Hi Oliver, I tried yesterday download links you provided for Czech and Slovak, and looked functional. Deeper testing comes later this day, probably after yours desired time. Regards, Michal Hriň Hi, I am in preparation of the activation of the update notification for our AOO 4.1.0 release for installed OpenOffice instances - versions 3.2.0, 3.2.1, 3.3.0, 3.4.0, 3.4.1, 4.0.0 and 4.0.1 Here is the list of the languages whose users will be guided to a localized website from the update notification in OpenOffice: - Czech http://www.openoffice.org/cs/download - German http://www.openoffice.org/de - Spanish http://www.openoffice.org/es/descargar - French http://www.openoffice.org/fr/Telecharger - Italian http://www.openoffice.org/it/download - Japanesehttp://www.openoffice.org/ja/download - Dutch http://www.openoffice.org/nl/downloaden.html - Portuguese (European) http://www.openoffice.org/pt - Slovak http://www.openoffice.org/sk/download - Turkish http://www.openoffice.org/tr - Chinese (simplified)http://www.openoffice.org/zh-cn - Chinese (traditional) http://www.openoffice.org/zh-tw As far as I can see the websites for the following languages need an update for AOO 4.1.0 - French - Japanese - Dutch Request to all native speakers of the above languages: - Please have a look, if the localilzed website is ok. - Please update the localized website, if needed - esp. for French, Japanese and Dutch My plan is to go live with the update notification for AOO 4.1.0 tomorrow early afternoon (14:00 UTC+2). Please leave my a note, if the one or the other localized website should be dropped or kept for the update notification. Thanks in advance. Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [ANN] Apache OpenOffice 4.1.0 released
or browse to [1] to have every available file in one place. [1] http://www.openoffice.org/download/other.html This page is not very helpful for not native english end-users. I will create a specific page to have this info in french. Thanks - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE] urgent request - activation of Update Notification for our AOO 4.1.0 release
Hi Michal, On 30.04.2014 08:09, Michal Hriň wrote: V Utorok, 29. apríl 2014 o 14:09 +0200, Oliver-Rainer Wittmann napísal(a): Hi Oliver, I tried yesterday download links you provided for Czech and Slovak, and looked functional. Thanks for checking and confirming that at the first glance the website looks good. Deeper testing comes later this day, probably after yours desired time. No problem. As your first check went well, I propose to keep the localized websites for Czech and Slovak for the update notification. Best regards, Oliver. Regards, Michal Hriň Hi, I am in preparation of the activation of the update notification for our AOO 4.1.0 release for installed OpenOffice instances - versions 3.2.0, 3.2.1, 3.3.0, 3.4.0, 3.4.1, 4.0.0 and 4.0.1 Here is the list of the languages whose users will be guided to a localized website from the update notification in OpenOffice: - Czech http://www.openoffice.org/cs/download - Germanhttp://www.openoffice.org/de - Spanish http://www.openoffice.org/es/descargar - Frenchhttp://www.openoffice.org/fr/Telecharger - Italian http://www.openoffice.org/it/download - Japanese http://www.openoffice.org/ja/download - Dutch http://www.openoffice.org/nl/downloaden.html - Portuguese (European) http://www.openoffice.org/pt - Slovakhttp://www.openoffice.org/sk/download - Turkish http://www.openoffice.org/tr - Chinese (simplified) http://www.openoffice.org/zh-cn - Chinese (traditional) http://www.openoffice.org/zh-tw As far as I can see the websites for the following languages need an update for AOO 4.1.0 - French - Japanese - Dutch Request to all native speakers of the above languages: - Please have a look, if the localilzed website is ok. - Please update the localized website, if needed - esp. for French, Japanese and Dutch My plan is to go live with the update notification for AOO 4.1.0 tomorrow early afternoon (14:00 UTC+2). Please leave my a note, if the one or the other localized website should be dropped or kept for the update notification. Thanks in advance. Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[PROPOSAL][RELEASE]: remove 4.1.0 beta from Sourceforge and from Aapche dist
Hi, removing 4.1 Beta from dist is natural but I would like to propose that we drop remove the 4.1 beta from the SF server as well. Any opinions? Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [PROPOSAL][RELEASE]: remove 4.1.0 beta from Sourceforge and from Aapche dist
Hi, On 30.04.2014 09:33, Jürgen Schmidt wrote: Hi, removing 4.1 Beta from dist is natural but I would like to propose that we drop remove the 4.1 beta from the SF server as well. Any opinions? +1 for removing the 4.1 beta 'bits' from the SourceForge server. Best regards, Oliver. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Proposal] Update Icons for AOO 4.1
On 2/28/14 9:06 AM, Jürgen Schmidt wrote: On 2/27/14 11:53 PM, Samer Mansour wrote: I'm tweaking the source SVGs so that the pixels in lines aren't between two pixels and look blurry. Once the SVGs are done its only a few minutes to generate the different output types. I kept waiting to have free uninterrupted block of time to complete the icons in the two months, which never happened. This last week I realized I'm making better progress if I did one icon each night. I'll keep posting updated zips with source SVGs as each finish. Soon I'll have the source svg's done, then we can worry about generating assets. ok perfect, thanks for your support. We are running a little bit out of time and have made no tests so far with the new icons in place. I suggest that we prepare test builds during the beta phase and see how the new icons work. Important from my opinion is that they fit in the overall picture and potentially we have to change more ... But lets see what we can achieve in time and when we all agree to integrate them in the GA we can do that. Otherwise we should immediately continue the work and integrate them asap in trunk to test, verify, improve this highly visible UI changes for the next release. We should not forget that such visible UI changes are always sensible and many different people have many different opinions. I am in favor of having this new icons available as soon as possible. Juergen Samer On Tue, Feb 25, 2014 at 2:50 AM, Jürgen Schmidt jogischm...@gmail.comwrote: On 2/25/14 1:58 AM, Kay Schenk wrote: On 02/24/2014 07:32 AM, Jürgen Schmidt wrote: On 2/19/14 4:18 AM, Samer Mansour wrote: Good eye on the green, that was a mistake, correcting now and uploading a new copy shortly. Yeah @2 for their retina display basically twice the physical pixels per inch (not sure if that statement is true, but its how we figure out the icons.) I know we need windows format, we still have time before the release, Jurgen or if someone else knows what formats and sizes we need that would be a great help. I will check the needed formats asap but important is that you provide the svg's that others can help as well. As always it is not easy to identify how the process work and where the images are stored and where to used ... We have some in default_images and used in probably in the start center and ??? Then we have icons in sysui as *.ico and *.icns Means there is still some work to do but I would like to try to include them for AOO 4.1. Can you share the svg files asap? Juergen Hi Samer, now after the 4.1 release I would like to move this forward and integrate the new icons as soon as possible in trunk. This will give us enough time to review the new icons in real life, to fine tune the icons where necessary and to do proper testing. Do you have already an idea when you can provide the svg files, yes svg is best to have the source files in place for later use or minor changes. In general I would like to suggest that we provide the src files for any images that other have the chance later to work them. The experience have shown that otherwise it is hard or impossible to do minor changes. I looking forward to the first dev build where we have the new icons in place. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [ANN] Apache OpenOffice 4.1.0 released
On 30.04.2014 00:15, Marcus (OOo) wrote: Am 04/29/2014 02:15 PM, schrieb Rory O'Farrell: Announced on en-Forum. BTW: Time to create a 4.1.0 value for the Version field in BZ. Good point. I disabled the 4.1.0-Beta and 4.1.0-dev versions, disabled the 4.1.0 target milestone, added a 4.2.0-dev version, also created a new 4.2.0 target and disabled the 4.1.0-release-blocker flag. If we decide to pursue a 4.1.1 version too then that target can be added too. Herbert - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: svn commit: r1591060 [12/15] - in /openoffice/trunk/main: helpcontent2/source/text/scalc/01/ helpcontent2/source/text/shared/01/ helpcontent2/source/text/simpress/01/ helpcontent2/source/text/smat
On 4/29/14 10:56 PM, Pedro Giffuni wrote:
Fixed as of r1591100, thanks!.
Sorry, I knew some of this could happen.
Unfortunately AOO is broken with FreeBSD 10+ (clang/libc++ has bridge
issues) so
my testing was limited. It also means I won't be doing much AOO in a while.
mmh, I don't know if this kind of bulk commits are really helpful. It's
nearly impossible to review them. Ok we will see build breakers but I
would prefer if we can at least announce such changes in front of the
change. I was surprised when I updated my local repo ...
And of course I am not sure if it is really so useful. Yes it's nice to
have this spelling errors fixed and I do it as well when I notice them.
But I am no friend of whitespace cleanup or stuff like this without
substantial changes/fixes.
Juergen
Pedro.
On 04/29/14 15:46, Ariel Constenla-Haile wrote:
On Tue, Apr 29, 2014 at 07:12:03PM -, p...@apache.org wrote:
Modified:
openoffice/trunk/main/offapi/com/sun/star/embed/XTransactionListener.idl
URL:
http://svn.apache.org/viewvc/openoffice/trunk/main/offapi/com/sun/star/embed/XTransactionListener.idl?rev=1591060r1=1591059r2=1591060view=diff
==
---
openoffice/trunk/main/offapi/com/sun/star/embed/XTransactionListener.idl
(original)
+++
openoffice/trunk/main/offapi/com/sun/star/embed/XTransactionListener.idl
Tue Apr 29 19:11:53 2014
@@ -41,21 +41,21 @@ module com { module sun { module star
//
-/** makes it possible to receive events when a transacted object
is commited
+/** makes it possible to receive events when a transacted object is
committed
or reverted.
*/
published interface XTransactionListener:
com::sun::star::lang::XEventListener
{
//
-/** is called just before the object is commited.
+/** is called just before the object is committed.
*/
void preCommit( [in] com::sun::star::lang::EventObject aEvent )
raises( ::com::sun::star::uno::Exception );
//
-/** is called after the object is commited.
+/** is called after the object is committed.
*/
-void commited( [in] com::sun::star::lang::EventObject aEvent );
+void committed( [in] com::sun::star::lang::EventObject aEvent );
This breaks the build and is an incompatible change in a published API.
Regards
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Interested to join development group of apache.
Greetings! My name is A L Vindhya, I'm from India Bangalore.Interested in software development. Please let me know how to register in order to contribute to apache. Regards Vindhya
[CODE][DISCUSS]: new option to enable ODF 1.2 encryption AES-256
Hi, for AOO 3.4 we had already discussed and later on reverted a change to enable the ODF Document encryption AES-256 by default. Some time ago I played with a new option field to allow the user to enable this option as new default, see [1] By default the office still uses the old blowfish algorithm but with this new option the user can enable the ODF 1.2 encryption. Well it is a minimal change to improve the current situation and allow the user to make use of what we already have. What does it mean in detail when we integrate this change? 1. No change as long as this option is not enabled 2. Option enabled and ODF 1.2 encryption is now default 2.1 New documents stored with password can't be loaded on older office versions 2.2 New or existing documents stored in older versions can still be loaded in the new office 2.3 Documents stored in older version (with the old algorithm) and loaded in the new office works as expected. Changes made in the document and stored with the new office still use the old algorithm and the document can later on opened in older office versions. From my pov of view there is still room for improvements but it is a first useful step to move forward to a more secure algorithm and give the user the opportunity to tweak the settings in the preferred way. I would like to propose to integrate this change and test it how well it works. Any opinions? Well keep in mind it is a minimal enhancement to make use of what we already have. There is still room for improvements ... Juergen [1] http://people.apache.org/~jsc/test/encryption_aes256_odf12.png - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [PROPOSAL][RELEASE]: remove 4.1.0 beta from Sourceforge and from Aapche dist
+1 Shenfeng (Simon) 2014-04-30 15:37 GMT+08:00 Oliver-Rainer Wittmann orwittm...@googlemail.com : Hi, On 30.04.2014 09:33, Jürgen Schmidt wrote: Hi, removing 4.1 Beta from dist is natural but I would like to propose that we drop remove the 4.1 beta from the SF server as well. Any opinions? +1 for removing the 4.1 beta 'bits' from the SourceForge server. Best regards, Oliver. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Misleading Mac message
A User on en-Forum has posted this: After receiving notification of the availability of Open Office 4.1.0, in which it was stated that the update was suitable for Mac OS X 10.3 onwards, I downloaded the relevant file … noting that it stated: Download Apache OpenOffice 4.1.0 Click here to download (hosted by Sourceforge.net) for: Mac OS X (10.6 or older) and English (British) | ~159 MByte | Released: 2014-Apr-29. However when I attempted to run the instal, a message was displayed indicating that this could not proceed as my version of Mac OS X was not suitable - I run OS X 10.6.8. -- This is only entry on the thread at https://forum.openoffice.org/en/forum/viewtopic.php?f=17t=69463 -- 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: Misleading Mac message
On 4/30/14 1:42 PM, Rory O'Farrell wrote: A User on en-Forum has posted this: After receiving notification of the availability of Open Office 4.1.0, in which it was stated that the update was suitable for Mac OS X 10.3 onwards, I downloaded the relevant file … noting that it stated: Download Apache OpenOffice 4.1.0 Click here to download (hosted by Sourceforge.net) for: Mac OS X (10.6 or older) and English (British) | ~159 MByte | Released: 2014-Apr-29. However when I attempted to run the instal, a message was displayed indicating that this could not proceed as my version of Mac OS X was not suitable - I run OS X 10.6.8. -- This is only entry on the thread at https://forum.openoffice.org/en/forum/viewtopic.php?f=17t=69463 I agree that this is confusing and we have to improve this. We should try to avoid update notifications for older systems but it's not so easy. It is documented in the release notes but of course a bad user experience to offer an update and inform the user later. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Misleading Mac message
On Wed, Apr 30, 2014 at 01:48:38PM +0200, Jürgen Schmidt wrote: On 4/30/14 1:42 PM, Rory O'Farrell wrote: A User on en-Forum has posted this: After receiving notification of the availability of Open Office 4.1.0 Where did he get the notification? The update mechanism supported by the application itself hasn't been activated, AFAIK. This is only entry on the thread at https://forum.openoffice.org/en/forum/viewtopic.php?f=17t=69463 I agree that this is confusing and we have to improve this. We should try to avoid update notifications for older systems but it's not so easy. Well, the update feed has a way to tell the application architecture with inst:arch, so that inst:archX86_64/inst:arch for MacOSX will be the same as removing the whole MacOSX entry, because all previous MacOSX installations are x86; this will of course disable all notifications for MacOSX. Another alternative is to create a special page for MacOSX users and add it inst:update, so that user are not directed to the download page, but this special page explaining the situation, because It is documented in the release notes but we all know no one reads them, the proof is https://issues.apache.org/ooo/show_bug.cgi?id=119006 for the Restore windows problem on Mac OS X Another broken thing in MacOSX are C++ extensions, I have seen any mention of this in the release notes. Regards -- Ariel Constenla-Haile La Plata, Argentina pgpNLzxwulvWk.pgp Description: PGP signature
Re: Misleading Mac message
Hi, On 30.04.2014 15:00, Ariel Constenla-Haile wrote: On Wed, Apr 30, 2014 at 01:48:38PM +0200, Jürgen Schmidt wrote: On 4/30/14 1:42 PM, Rory O'Farrell wrote: A User on en-Forum has posted this: After receiving notification of the availability of Open Office 4.1.0 Where did he get the notification? The update mechanism supported by the application itself hasn't been activated, AFAIK. I also have this question, because the update notifications for OpenOffice instances 3.2.0, ... 4.0.1 had been activated a couple of minutes ago. Thus, this user got another one. May be it was a notification from SourceForge. This is only entry on the thread at https://forum.openoffice.org/en/forum/viewtopic.php?f=17t=69463 I agree that this is confusing and we have to improve this. We should try to avoid update notifications for older systems but it's not so easy. Well, the update feed has a way to tell the application architecture with inst:arch, so that inst:archX86_64/inst:arch for MacOSX will be the same as removing the whole MacOSX entry, because all previous MacOSX installations are x86; this will of course disable all notifications for MacOSX. Another alternative is to create a special page for MacOSX users and add it inst:update, so that user are not directed to the download page, but this special page explaining the situation, because Damn. Ariel, you are right. I have overseen this in my recent activation of the update notification. Thus, installed Mac OS X OpenOffice instance will not get an update notification about 4.1.0. Best regards, Oliver. It is documented in the release notes but we all know no one reads them, the proof is https://issues.apache.org/ooo/show_bug.cgi?id=119006 for the Restore windows problem on Mac OS X Another broken thing in MacOSX are C++ extensions, I have seen any mention of this in the release notes. Regards - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Misleading Mac message
On Wed, 30 Apr 2014 15:09:13 +0200 Oliver-Rainer Wittmann orwittm...@googlemail.com wrote: Hi, On 30.04.2014 15:00, Ariel Constenla-Haile wrote: On Wed, Apr 30, 2014 at 01:48:38PM +0200, Jürgen Schmidt wrote: On 4/30/14 1:42 PM, Rory O'Farrell wrote: A User on en-Forum has posted this: After receiving notification of the availability of Open Office 4.1.0 Where did he get the notification? The update mechanism supported by the application itself hasn't been activated, AFAIK. I also have this question, because the update notifications for OpenOffice instances 3.2.0, ... 4.0.1 had been activated a couple of minutes ago. Thus, this user got another one. May be it was a notification from SourceForge. The user posted to the en-Forum at 30 Apr 2014, 02:57 (time is UTC +1) This is only entry on the thread at https://forum.openoffice.org/en/forum/viewtopic.php?f=17t=69463 I agree that this is confusing and we have to improve this. We should try to avoid update notifications for older systems but it's not so easy. Well, the update feed has a way to tell the application architecture with inst:arch, so that inst:archX86_64/inst:arch for MacOSX will be the same as removing the whole MacOSX entry, because all previous MacOSX installations are x86; this will of course disable all notifications for MacOSX. Another alternative is to create a special page for MacOSX users and add it inst:update, so that user are not directed to the download page, but this special page explaining the situation, because Damn. Ariel, you are right. I have overseen this in my recent activation of the update notification. Thus, installed Mac OS X OpenOffice instance will not get an update notification about 4.1.0. Best regards, Oliver. It is documented in the release notes but we all know no one reads them, the proof is https://issues.apache.org/ooo/show_bug.cgi?id=119006 for the Restore windows problem on Mac OS X Another broken thing in MacOSX are C++ extensions, I have seen any mention of this in the release notes. Regards - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- 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] urgent request - activation of Update Notification for our AOO 4.1.0 release
Hi, I have committed new Update XML feeds. Update notifications for Mac OS X OpenOffice installed instances are now deactivated due to a oversight on my side. As I would like to consider the change in the supported architecture I will work on a solution in the next days. Best regards, Oliver. On 29.04.2014 14:09, Oliver-Rainer Wittmann wrote: Hi, I am in preparation of the activation of the update notification for our AOO 4.1.0 release for installed OpenOffice instances - versions 3.2.0, 3.2.1, 3.3.0, 3.4.0, 3.4.1, 4.0.0 and 4.0.1 Here is the list of the languages whose users will be guided to a localized website from the update notification in OpenOffice: - Czechhttp://www.openoffice.org/cs/download - Germanhttp://www.openoffice.org/de - Spanishhttp://www.openoffice.org/es/descargar - Frenchhttp://www.openoffice.org/fr/Telecharger - Italianhttp://www.openoffice.org/it/download - Japanesehttp://www.openoffice.org/ja/download - Dutchhttp://www.openoffice.org/nl/downloaden.html - Portuguese (European)http://www.openoffice.org/pt - Slovakhttp://www.openoffice.org/sk/download - Turkishhttp://www.openoffice.org/tr - Chinese (simplified)http://www.openoffice.org/zh-cn - Chinese (traditional)http://www.openoffice.org/zh-tw As far as I can see the websites for the following languages need an update for AOO 4.1.0 - French - Japanese - Dutch Request to all native speakers of the above languages: - Please have a look, if the localilzed website is ok. - Please update the localized website, if needed - esp. for French, Japanese and Dutch My plan is to go live with the update notification for AOO 4.1.0 tomorrow early afternoon (14:00 UTC+2). Please leave my a note, if the one or the other localized website should be dropped or kept for the update notification. Thanks in advance. Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Misleading Mac message
2014-04-30 15:09 GMT+02:00 Oliver-Rainer Wittmann orwittm...@googlemail.com : Hi, On 30.04.2014 15:00, Ariel Constenla-Haile wrote: On Wed, Apr 30, 2014 at 01:48:38PM +0200, Jürgen Schmidt wrote: On 4/30/14 1:42 PM, Rory O'Farrell wrote: A User on en-Forum has posted this: After receiving notification of the availability of Open Office 4.1.0 Where did he get the notification? The update mechanism supported by the application itself hasn't been activated, AFAIK. I also have this question, because the update notifications for OpenOffice instances 3.2.0, ... 4.0.1 had been activated a couple of minutes ago. Thus, this user got another one. May be it was a notification from SourceForge. While you download a program from SourceForge you can leave your email to get updates for that specific program. It's called 'keep me updated', and you can see that at the bottom of all projects' pages. Only if you subscribed to that service you might get an email from SourceForge when a new release is made available. Actually we just made 4.1 the new default, so people might have get that email now. Roberto This is only entry on the thread at https://forum.openoffice.org/en/forum/viewtopic.php?f=17t=69463 I agree that this is confusing and we have to improve this. We should try to avoid update notifications for older systems but it's not so easy. Well, the update feed has a way to tell the application architecture with inst:arch, so that inst:archX86_64/inst:arch for MacOSX will be the same as removing the whole MacOSX entry, because all previous MacOSX installations are x86; this will of course disable all notifications for MacOSX. Another alternative is to create a special page for MacOSX users and add it inst:update, so that user are not directed to the download page, but this special page explaining the situation, because Damn. Ariel, you are right. I have overseen this in my recent activation of the update notification. Thus, installed Mac OS X OpenOffice instance will not get an update notification about 4.1.0. Best regards, Oliver. It is documented in the release notes but we all know no one reads them, the proof is https://issues.apache.org/ooo/show_bug.cgi?id=119006 for the Restore windows problem on Mac OS X Another broken thing in MacOSX are C++ extensions, I have seen any mention of this in the release notes. Regards - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE] urgent request - activation of Update Notification for our AOO 4.1.0 release
On Wed, Apr 30, 2014 at 9:25 AM, Oliver-Rainer Wittmann orwittm...@googlemail.com wrote: Hi, I have committed new Update XML feeds. Update notifications for Mac OS X OpenOffice installed instances are now deactivated due to a oversight on my side. As I would like to consider the change in the supported architecture I will work on a solution in the next days. One possible solution: For the Mac OS update notifications, instead of sending the user to the download page, send them to a special Mac upgrade page. That page can explain that there is a new 4.1 release but it has a new prereq for OS X Lion. This would be a very simple, uncluttered page. Then it would have a link that says something like I have OS X 10.6 or above, which would then take them to the download site. If we keep it simple it could easily be translated for the native language sites. -Rob Best regards, Oliver. On 29.04.2014 14:09, Oliver-Rainer Wittmann wrote: Hi, I am in preparation of the activation of the update notification for our AOO 4.1.0 release for installed OpenOffice instances - versions 3.2.0, 3.2.1, 3.3.0, 3.4.0, 3.4.1, 4.0.0 and 4.0.1 Here is the list of the languages whose users will be guided to a localized website from the update notification in OpenOffice: - Czechhttp://www.openoffice.org/cs/download - Germanhttp://www.openoffice.org/de - Spanishhttp://www.openoffice.org/es/descargar - Frenchhttp://www.openoffice.org/fr/Telecharger - Italianhttp://www.openoffice.org/it/download - Japanesehttp://www.openoffice.org/ja/download - Dutchhttp://www.openoffice.org/nl/downloaden.html - Portuguese (European)http://www.openoffice.org/pt - Slovakhttp://www.openoffice.org/sk/download - Turkishhttp://www.openoffice.org/tr - Chinese (simplified)http://www.openoffice.org/zh-cn - Chinese (traditional)http://www.openoffice.org/zh-tw As far as I can see the websites for the following languages need an update for AOO 4.1.0 - French - Japanese - Dutch Request to all native speakers of the above languages: - Please have a look, if the localilzed website is ok. - Please update the localized website, if needed - esp. for French, Japanese and Dutch My plan is to go live with the update notification for AOO 4.1.0 tomorrow early afternoon (14:00 UTC+2). Please leave my a note, if the one or the other localized website should be dropped or kept for the update notification. Thanks in advance. Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [ANN] Apache OpenOffice 4.1.0 released
2014-04-30 0:02 GMT+02:00 Andrea Pescetti pesce...@apache.org: Tal Daniel wrote: FYI: at Sourceforge, the big green download button downloads the 4.0.1 version. It happened to me This must be fixed in the SourceForge OpenOffice mirror project by those who can administer it. Note: if I remember correctly, this will trigger notification e-mails to people who are following the OpenOffice project on SourceForge. As per my answer on another thread we have updated the default to AOO 4.1. And yes, people who subscribed to the 'Keep me updated' feature will automatically receive an email notifying them about the new release. Roberto Later, I noticed the dark red error message on the sourceforge page, which states that the 4.1.0/binaries/...86.exe file can't be found or isn't available. ... If this is still happening (maybe it was related to cache or propagation) can you please give us the exact link from the download page to SourceForge? I.e., the target of the Download Apache OpenOffice 4.1.0 link? Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [CODE][DISCUSS]: new option to enable ODF 1.2 encryption AES-256
On 4/30/14 10:53 AM, Jürgen Schmidt wrote: Hi, for AOO 3.4 we had already discussed and later on reverted a change to enable the ODF Document encryption AES-256 by default. Some time ago I played with a new option field to allow the user to enable this option as new default, see [1] By default the office still uses the old blowfish algorithm but with this new option the user can enable the ODF 1.2 encryption. Well it is a minimal change to improve the current situation and allow the user to make use of what we already have. What does it mean in detail when we integrate this change? 1. No change as long as this option is not enabled 2. Option enabled and ODF 1.2 encryption is now default 2.1 New documents stored with password can't be loaded on older office versions - stored with the new ODF 1.2 encryption And Oliver pointed out that AOO 3.4 of course is already able to read such documents 2.2 New or existing documents stored in older versions can still be loaded in the new office with the old blowfish encryption 2.3 Documents stored in older version (with the old algorithm) and loaded in the new office works as expected. Changes made in the document and stored with the new office still use the old algorithm and the document can later on opened in older office versions. From my pov of view there is still room for improvements but it is a first useful step to move forward to a more secure algorithm and give the user the opportunity to tweak the settings in the preferred way. I would like to propose to integrate this change and test it how well it works. Any opinions? Well keep in mind it is a minimal enhancement to make use of what we already have. There is still room for improvements ... Juergen [1] http://people.apache.org/~jsc/test/encryption_aes256_odf12.png - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: svn commit: r1591060 [12/15] - in /openoffice/trunk/main: helpcontent2/source/text/scalc/01/ helpcontent2/source/text/shared/01/ helpcontent2/source/text/simpress/01/ helpcontent2/source/text/smat
FWIW ... The change was announced ages ago: http://mail-archives.apache.org/mod_mbox/openoffice-dev/201404.mbox/raw/%3C5345E952.8060909%40apache.org%3E But of course there were good reasons to wait after the release before committing it. About the argument of the value behind the changes, some of the changes touched some user visible strings, but well ... by the sheer size you might imagine how long it took to get to it, time that would have otherwise been spent over a period of .. perhaps many years. It is rather unelegant for an Office suite to have such mistakes and I was not able to fix them all though. There are some really ugly issues that I am sure I am not the first to notice: some text files appear as binaries or are encoded in some format that break the tools I used or caused trouble to svn diff. In any case.. I don't forsee doing these type of titanic tasks again ;-). Pedro. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: EXTERNAL: Re: Extension Manager Add Crashes
Anyone out their willing and able to assist with this issue? We are not making any progress. -Original Message- From: Herbert Duerr [mailto:h...@apache.org] Sent: Wednesday, April 16, 2014 12:12 AM To: dev@openoffice.apache.org Subject: Re: EXTERNAL: Re: Extension Manager Add Crashes On 16.04.2014 01:16, Steele, Raymond wrote: Why do you mention the Solaris Sparc UNO C++ bridge below. Is it related to the x86/intel bridge. I am running Solaris 11 x86_64. Ah, ok. Looking at the directory main/bridges/source/cpp_uno there is no UNO bridge yet for Solaris Studio on a x86-64 CPU. But apparently your compile got through, so in order to know where to tweak you need to find out which bridge was actually used. Then you can adapt it to your platform (operating system, compiler, cpu architecture, ABI). As I mentioned the platform independence of AOO's UNO subsystem was unfortunately not designed in e.g. by using plain programming language constructs or using portable mechanisms like C-linking. Getting a bridge to work was accomplished by brute force :-/ (reverse engineering the vtable layouts, symbol mangling, calling conventions, implementation details of exception handling, etc.) but if we're lucky a few tweaks to the currently active bridge could suffice. For an idea on what tweaks might be needed please check the evolution of the related x86-64 bridges for Linux, FreeBSD or MacOSX. Herbert - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [ANN] Apache OpenOffice 4.1.0 released
Am 04/30/2014 10:06 AM, schrieb Herbert Duerr: On 30.04.2014 00:15, Marcus (OOo) wrote: Am 04/29/2014 02:15 PM, schrieb Rory O'Farrell: Announced on en-Forum. BTW: Time to create a 4.1.0 value for the Version field in BZ. Good point. I disabled the 4.1.0-Beta and 4.1.0-dev versions, disabled the 4.1.0 target milestone, added a 4.2.0-dev version, also created a new 4.2.0 target and disabled the 4.1.0-release-blocker flag. If we decide to pursue a 4.1.1 version too then that target can be added too. Thanks for this bigger update. :-) Do we still need the OOo 3.4.0 Beta? I would disable this as-well as IMHO it is no linger needed like 4.1.0 Beta. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Server status: What's Up; What's Down?
Am 04/30/2014 09:02 AM, schrieb Jörg Schmidt: on Tuesday, April 29, 2014 10:10 PM Marcus (OOo) wrote: FYI The CMS builder is down again. When clicking on the [Follow Staging Build] link in CMS, I come to http://ci.apache.org/builders/ooo-site-site-staging; and the error message 503 Service Unavailable. The status montioring webpage tells the same for the aegis server. I just (30.04.2014 09:00 MESZ) the page: http://www.openoffice.org/de/ edited (a space character added), it worked. right, I've done some changed already yesterday but forget to mentioned it here that it is working again. Luckily just an one-hour-outage. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [PROPOSAL][RELEASE]: remove 4.1.0 beta from Sourceforge and from Aapche dist
Am 04/30/2014 09:33 AM, schrieb Jürgen Schmidt: removing 4.1 Beta from dist is natural but I would like to propose that we drop remove the 4.1 beta from the SF server as well. Any opinions? a beta (or any other pre-release build) has a defined date of expiry and shouldn't be used after this. So +1 to delete from every mirror server. *Maybe* we can save it (or just a few files) on the archive for historical reasons. ;-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [PROPOSAL][RELEASE]: remove 4.1.0 beta from Sourceforge and from Aapche dist
+1 On 4/30/14, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 04/30/2014 09:33 AM, schrieb Jürgen Schmidt: removing 4.1 Beta from dist is natural but I would like to propose that we drop remove the 4.1 beta from the SF server as well. Any opinions? a beta (or any other pre-release build) has a defined date of expiry and shouldn't be used after this. So +1 to delete from every mirror server. *Maybe* we can save it (or just a few files) on the archive for historical reasons. ;-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Alexandro Colorado Apache OpenOffice Contributor http://www.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE]: kid language packs for AOO 4.1.0
Am 04/30/2014 09:01 AM, schrieb Jürgen Schmidt: Hi, I have uploaded kid language packs for AOO 4.1.0 under http://people.apache.org/~jsc/releases/4.1.0/kid_langpack/ I hope you can use them to improve the translation where necessary or to identify easier where the string have to be searched in Pootle. would it be more helpful to make this a part of the release? Then the kid files could be offered on [1] and we can point everybody who is interested to the files. Just make it centralized and visible. [1] http://openoffice.apache.org/downloads.html My 2 ct. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [PROPOSAL][RELEASE]: remove 4.1.0 beta from Sourceforge and from Aapche dist
Jürgen Schmidt wrote: Hi, removing 4.1 Beta from dist is natural but I would like to propose that we drop remove the 4.1 beta from the SF server as well. Any opinions?he usefulness of the beta has exop Juergen +1 The usefulness of the Beta has expired so there is no reason to keep it alive on the mirrors. Keith signature.asc Description: OpenPGP digital signature
Re: Misleading Mac message
Ariel Constenla-Haile wrote: On Wed, Apr 30, 2014 at 01:48:38PM +0200, Jürgen Schmidt wrote: On 4/30/14 1:42 PM, Rory O'Farrell wrote: A User on en-Forum has posted this: After receiving notification of the availability of Open Office 4.1.0 Where did he get the notification? The update mechanism supported by the application itself hasn't been activated, AFAIK. This is only entry on the thread at https://forum.openoffice.org/en/forum/viewtopic.php?f=17t=69463 I agree that this is confusing and we have to improve this. We should try to avoid update notifications for older systems but it's not so easy. Well, the update feed has a way to tell the application architecture with inst:arch, so that inst:archX86_64/inst:arch for MacOSX will be the same as removing the whole MacOSX entry, because all previous MacOSX installations are x86; this will of course disable all notifications for MacOSX. Another alternative is to create a special page for MacOSX users and add it inst:update, so that user are not directed to the download page, but this special page explaining the situation, because It is documented in the release notes but we all know no one reads them, the proof is https://issues.apache.org/ooo/show_bug.cgi?id=119006 for the Restore windows problem on Mac OS X Another broken thing in MacOSX are C++ extensions, I have seen any mention of this in the release notes. Ariel; If you can you point me to any discussion of this problem for MaxOSX I will add an action item to my to-do list to make a mention of this in the release notes for the next release. Regards Keith Regards signature.asc Description: OpenPGP digital signature
Re: [PROPOSAL][RELEASE]: remove 4.1.0 beta from Sourceforge and from Aapche dist
On 30/04/2014 Marcus (OOo) wrote: Am 04/30/2014 09:33 AM, schrieb Jürgen Schmidt: removing 4.1 Beta from dist is natural but I would like to propose that we drop remove the 4.1 beta from the SF server as well. Any opinions? a beta (or any other pre-release build) has a defined date of expiry and shouldn't be used after this. So +1 to delete from every mirror server. I agree we should remove it both from dist and from SF. *Maybe* we can save it (or just a few files) on the archive for historical reasons. ;-) We voted on 4.1.0-beta. This makes it a release we should archive. Our archive at http://archive.apache.org/dist/openoffice/4.1.0-beta/ already has the source and all checksums. Binary files are missing. They should be moved there too for completeness. And then we can forget about the beta. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE]: kid language packs for AOO 4.1.0
Marcus (OOo) wrote: Am 04/30/2014 09:01 AM, schrieb Jürgen Schmidt: I have uploaded kid language packs for AOO 4.1.0 under http://people.apache.org/~jsc/releases/4.1.0/kid_langpack/ Thanks for this, they will be very useful to localization volunteers. By the way, how do I enable kid? I installed the 64-bit RPM over the Italian version of OpenOffice 4.1.0 and I thought I would see an entry in Tools - Options - Language Settings - Languages. But it didn't list anything new. (After it, I installed a normal en-US language pack and this one worked as expected). I know kid is special, but how can I enable it? would it be more helpful to make this a part of the release? No need for that. They are really only for volunteers, even more than the snapshot builds. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Misleading Mac message
Hi Keith, On Wed, Apr 30, 2014 at 02:14:00PM -0400, Keith N. McKenna wrote: Another broken thing in MacOSX are C++ extensions, I have seen any mention of this in the release notes. Ariel; If you can you point me to any discussion of this problem for MaxOSX AFAIK there hasn't been any discussion on the topic, but is a logical consequence of switching the arch. from 32 to 64 bit. I will add an action item to my to-do list to make a mention of this in the release notes for the next release. The scenario is the following: - the user installed in 4.0.* an extension based on code written in C++, for example the PDF Import extension for Apache OpenOffice. OpenOffice and the extension code are both 32 bit on MacOSX - the user upgrades to 4.1.0, which is now 64 bit - OpenOffice 64 bit will use the same user profile as the previous 32 bit version, there is no profile migration; thus this profile contains a 32 bit extension that will not work with the new 64 bit OpenOffice. The Extensions Manager will display the 32 bit extension as disabled. Regards -- Ariel Constenla-Haile La Plata, Argentina pgp_jPCT1pQk8.pgp Description: PGP signature
Re: Misleading Mac message
Hi Oliver, On Wed, Apr 30, 2014 at 03:09:13PM +0200, Oliver-Rainer Wittmann wrote: I agree that this is confusing and we have to improve this. We should try to avoid update notifications for older systems but it's not so easy. Well, the update feed has a way to tell the application architecture with inst:arch, so that inst:archX86_64/inst:arch for MacOSX will be the same as removing the whole MacOSX entry, because all previous MacOSX installations are x86; this will of course disable all notifications for MacOSX. Another alternative is to create a special page for MacOSX users and add it inst:update, so that user are not directed to the download page, but this special page explaining the situation, because Damn. Ariel, you are right. I have overseen this in my recent activation of the update notification. Thus, installed Mac OS X OpenOffice instance will not get an update notification about 4.1.0. In this case, it is harmless and gives more time to think things through. IMO it would be better to change the inst:arch to x86 and point not to the download page but to an alternative one, explaining the switch to 64 bit and its consequences. Regards -- Ariel Constenla-Haile La Plata, Argentina pgpj9llZKhKnG.pgp Description: PGP signature
Re: Misleading Mac message
Keith N. McKenna wrote: will also start another thread here as to whether we should add it to the 4.1 notes. No need to discuss it. The Mac OS X C++ extensions compatibility is clearly something that must be added to the 4.1 Release Notes. The Known Issues are our way to tell users about changes that confused other users. We have already added items to the Known Issues in the past and we can do so for 4.1 too. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Misleading Mac message
Andrea Pescetti wrote: Keith N. McKenna wrote: will also start another thread here as to whether we should add it to the 4.1 notes. No need to discuss it. The Mac OS X C++ extensions compatibility is clearly something that must be added to the 4.1 Release Notes. The Known Issues are our way to tell users about changes that confused other users. We have already added items to the Known Issues in the past and we can do so for 4.1 too. Regards, Andrea. Andrea; Agreed; am off to the c-wiki to add the issue. Regards Keith signature.asc Description: OpenPGP digital signature
Re: Misleading Mac message
Ariel Constenla-Haile wrote: Hi Keith, On Wed, Apr 30, 2014 at 02:14:00PM -0400, Keith N. McKenna wrote: Another broken thing in MacOSX are C++ extensions, I have seen any mention of this in the release notes. Ariel; If you can you point me to any discussion of this problem for MaxOSX AFAIK there hasn't been any discussion on the topic, but is a logical consequence of switching the arch. from 32 to 64 bit. I will add an action item to my to-do list to make a mention of this in the release notes for the next release. The scenario is the following: - the user installed in 4.0.* an extension based on code written in C++, for example the PDF Import extension for Apache OpenOffice. OpenOffice and the extension code are both 32 bit on MacOSX - the user upgrades to 4.1.0, which is now 64 bit - OpenOffice 64 bit will use the same user profile as the previous 32 bit version, there is no profile migration; thus this profile contains a 32 bit extension that will not work with the new 64 bit OpenOffice. The Extensions Manager will display the 32 bit extension as disabled. Regards Ariel et al ; One question. Am I correct in assuming that the only fix is for the extension developer to re-write the extension for 64-bit for MacOSX? Regards Keith signature.asc Description: OpenPGP digital signature
Re: [ANN] Apache OpenOffice 4.1.0 released
Am 04/30/2014 09:21 AM, schrieb FR web forum: or browse to [1] to have every available file in one place. [1] http://www.openoffice.org/download/other.html This page is not very helpful for not native english end-users. I will create a specific page to have this info in french. Understood. But maybe it's helpful to get only the table? And build some own text around it. To give it a try do this: - include the download_other.js (note to get the correct sub-dir!) like this: script type=text/javascript src=download_other.js/script - call the function to print the table (1 = release version): write_table( 1 ); To get the complete context just have a look into the source code of the other.html file. Maybe it helps you not to do all the work on your own. ;-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Misleading Mac message
On Wed, Apr 30, 2014 at 04:14:18PM -0400, Keith N. McKenna wrote: Ariel et al ; One question. Am I correct in assuming that the only fix is for the extension developer to re-write the extension for 64-bit for MacOSX? Recompile the extension (and fix if something gets broken after the compiler switch from gcc to clang). Anyway, for end users I'd just say something like Please contact the original developer or Please report this problem with the original developer of the extension, etc. Regards -- Ariel Constenla-Haile La Plata, Argentina pgpuGdiiazgdp.pgp Description: PGP signature
Re: Misleading Mac message
Am 04/30/2014 01:42 PM, schrieb Rory O'Farrell: A User on en-Forum has posted this: After receiving notification of the availability of Open Office 4.1.0, in which it was stated that the update was suitable for Mac OS X 10.3 onwards, I downloaded the relevant file … noting that it stated: Download Apache OpenOffice 4.1.0 Click here to download (hosted by Sourceforge.net) for: Mac OS X (10.6 or older) and English (British) | ~159 MByte | Released: 2014-Apr-29. However when I attempted to run the instal, a message was displayed indicating that this could not proceed as my version of Mac OS X was not suitable - I run OS X 10.6.8. -- This is only entry on the thread at https://forum.openoffice.org/en/forum/viewtopic.php?f=17t=69463 I've investigated a bit and think I've found something that is not correct. I've fixed this now. Is it possible to ask the user to test again? Would be great. PS: An output of the table could be also very helpful: http://www.openoffice.org/download/test/analyze.html Thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
