Re: Bundled extensions
On 11.04.2012 09:40, drew jensen wrote: On Wed, 2012-04-11 at 03:28 +0200, Jürgen Schmidt wrote: On 4/10/12 3:45 PM, O.Felka wrote: Am 10.04.2012 15:28, schrieb Rob Weir: On Tue, Apr 10, 2012 at 6:43 AM, O.Felkaolaf-openoff...@gmx.de wrote: The bad news: - The error http://download.translate.org.za/spellchecker/dict-en_ZA-latest.update.xml does not exist. is still present - looks not very professional. That URL is an external one, not one that we control. Do you know what the behavior is in OOo 3.3 when checking for an update of that extension? No, I have no idea what OOo 3.3 will do. But I think it would behave the same. But I'm sure we wouldn't have bundled it. yes it should it be the same problem in OOo3.3. I would propose that we don't bundle extensions that will include an external update Url or something like that. We should bundle extension only that will be supported and completely handled by our extension repo. ah - ok, that sounds reasonable at it's face. Now if an extension is published at the AOO ext. repository and it's implemented in a scripted language (basic, js, python, etc) the oxt (extension body) is the source code, so that makes easy sense. Removed the extension from main/extensions.lst in revision is 1324590. -Andre What if the extension is in java or c++ or some other language where an external source repository is used, however the extension runtime and support vector are both through the AOO ext. repository - I would assume given a suitable license on the source that it would be, eligible, for consideration. Anyway - I'm putting forth a question that doesn't need to be answered today, just thinking out loud I suppose. //drew If no update Url is given in the extension and the extension is distributed via the ext repo the update info Was (and hopefully is, will be) generated on demand. Juergen
Linux Build Problem, Bug 119162 can be taken as NOT Show stopper with record the issue in release note
Hi all, We have talked a lot about linux build upgrade problem, as the issue 119162 reported. Personally I think it can be taken as NOT AOO 3.4 RC build show stopper. But we need document this limition and give workaround there in release note. Best regrads, Lily
Re: Bundled extensions
Felka, This should be old problem, another volunteer report the similar problem as well though I didn't catch it when I install English full package and Simple Chinese full package on Mac lion and Windows XP. For the bundle, which extension should be bundled should depend on the real usage. For example, for English package, the english related directories should be bundled. And for one specific lanauge package, the related language directory should be bundled as well. But if many directories for one language, say, English, should we bundle all of them? It should depend one user requirements and if it is handled by our extension pool. For other extension not related to directory, we may also bundle it depend on the if most user will need. Actually for one extension used by most people, I prefer driving it to become one feature of next release. Best Regrads, Lily 2012/4/10 O.Felka olaf-openoff...@gmx.de Moin, I've tested r1309668 en_US to verify the fix for issue 119114 [1]. The good news: - No crash when checking for updates. The bad news: - The error http://download.translate.**org.za/spellchecker/dict-en_** ZA-latest.update.xmlhttp://download.translate.org.za/spellchecker/dict-en_ZA-latest.update.xmldoes not exist. is still present - looks not very professional. - Clicking on 'Show all Updates' shows English (South Africa) spell checker as update available. The description field shows 'An error occurred: Not found!' - looks not very professional. - The presenter screen extension is not installed. Groetjes, Olaf [1] https://issues.apache.org/ooo/**show_bug.cgi?id=119114https://issues.apache.org/ooo/show_bug.cgi?id=119114
Re: ooo large commit breaks mirror sync !!
Hi Gavin, On 21.02.2012 00:21, Gavin McDonald wrote: If anyone wants to do large commits like below link shows [1] (over 8000 paths changed and lots of zips and tar files.) PLEASE notify infra first and schedule it for a WEEKEND. People have been struggling to commit to the EU mirror since this large commit was started 5 hours ago. Thanks Gav... [1] - http://svn.apache.org/viewvc?view=revisionsortby=revsortdir=downrevision= 1291394 sorry to come back to this one, but I've re-synched and built aw080 branch (https://svn.apache.org/repos/asf/incubator/ooo/branches/alg/aw080) which contains all the changes which lead to the first problems. Worse, this time even more changes are involved. I see no other chance to resync my branch (containing 1 1/2 years of work on OOo code) than to commit it to the branch. Please give advice when and how to do that, I'll be ready to commit in the next days. Sincerely, Armin -- ALG
Re: Linux builds
Hi Andre, * On Wed, Apr 11, 2012 at 09:57:35AM +0800, Andre Fischer wrote: Does anybody have tested an upgrade installation with these new Linux packages and can verify the reported problem, see https://issues.apache.org/ooo/show_bug.cgi?id=119162 I think we haven't noticed this problem before and I would be interested if others can confirm this problem. I will be offline for ~1 day because of traveling and I will make the call for VOTE depending on the feedback from you. Old basis package set remaining is the default behaviour, at least tested with OOo 3.0.0. On Fedora 16: - install OOo 3.0.0 (OOO300_m9 9358) - install OOo 3.1.1 (OOO310_m19 9420) 1) there is an issue with the desktop integration, same for AOO 2) the old basis3.0 remains: /opt/openoffice.org/basis3.0 /opt/openoffice.org/basis3.1 All ooobasis3.0 packages are kept. Strange. Here is what I would expect would happen on an update: - There is one top-level or meta package that has dependencies on all the other packages (directly or indirectly) - This meta package of OOo3.? is replaced by AOO3.4 - The packages of OOo3.? are not referenced anymore and get removed automatically. The new packages are installed. Everything is find. So one of the following things goes wrong: - The old meta package is not removed because the new one has no relationship to it (maybe because of a different application name) - The old meta package is removed but some other package keeps a reference to one of OOo3.? base packages. - Something else that I did not think of yet (I am currently on a business trip and am still adapting to the new time zone) There are different issues. The main one is that the package name containes %OOOBASEVERSION Example: module = gid_Module_Prg_Wrt_Bin main/setup_native/source/packinfo/packinfo_office.txt#88 packagename = %BASISPACKAGEPREFIX%OOOBASEVERSION-writer %BASISPACKAGEPREFIX -- ooobasis main/instsetoo_native/util/openoffice.lst#20 %OOOBASEVERSION -- 3.4 main/instsetoo_native/util/openoffice.lst#7 I have installed following packages: ooobasis3.4-writer 3.4.0-9590 ooobasis3.0-writer 3.0.0-9358 ooobasis3.1-writer 3.1.1-9420 ooobasis3.2-writer 3.2.1-9502 ooobasis3.3-writer 3.3.0-9567 Because the *package* name is different, they are indeed different packages, ooobasis3.2-writer is *not* regarded as an update for ooobasis3.1-writer, and so on. ooobasis3.2-writer 3.2.1-9502 can only be updated by a package with the same name, examples: ooobasis3.2-writer 3.2.1-9503 (increase BUILD in main/solenv/inc/minor.mk#23) ooobasis3.2-writer 3.2.2-9502 etc. Note that I'm not sure if this is an issue, or it is the way it was designed with the idea of having different basis installations. The only solution in this strange design is to declare a package obsoleting the other ones, for example ooobasis3.4-writer obsoleting ooobasis3.0-writer ooobasis3.1-writer ooobasis3.2-writer ooobasis3.3-writer This can be done using linuxreplaces in the files on main/setup_native/source/packinfo/ I've tried this is success (though minimal testing): http://people.apache.org/~arielch/packages/yum-update-fix.txt There are some caveats: * A meta package is not enough, this has to be done on a per-packages way, not only to be in the safe side (if the user tries to install some package without the rest), but mainly because previous versions (and the current one) do not have a *real* meta package. The package openoffice.org3 gid_Module_Root_Brand does not provide every package OOo shipped in the tar file, see next point. * gid_Module_Root_Brand requires %UREPACKAGEPREFIX-ure %BASISPACKAGEPREFIX%OOOBASEVERSION-core01 %BASISPACKAGEPREFIX%OOOBASEVERSION-core02 %BASISPACKAGEPREFIX%OOOBASEVERSION-core03 %BASISPACKAGEPREFIX%OOOBASEVERSION-core04 %BASISPACKAGEPREFIX%OOOBASEVERSION-core05 %BASISPACKAGEPREFIX%OOOBASEVERSION-core06 %BASISPACKAGEPREFIX%OOOBASEVERSION-core07 %BASISPACKAGEPREFIX%OOOBASEVERSION-images When you install openoffice.org3 from AOO 3.4.0 over openoffice.org3 from 3.3.0, it only gets updated because they have the same name. It also updates the URE (due to same name, too). It installs basis core01-07 and basis images, but does not update/remove previous packages because the name is different. Besides, this sort of meta package does not install the office modules (writer, calc, etc). * Apache OpenOffice orphans some packages that are no longer present: In the basis layer: oooimprovement kde-integration [yes, AOO has no KDE integration] In the brand layer, OOo 3.3 installed by default 3 dictionaries: openoffice.org3-dict-en openoffice.org3-dict-es openoffice.org3-dict-fr These can all be obsoleted in openoffice.org3 In short, gid_Module_Root_Brand can be made a real meta package, and linuxreplaces is the only solution to remove old basis packages. (I still didn't look at the desktop integration
Apache OpenOffice Project Twitter Account
Social media outreach, via Twitter, Facebook, Google+, etc., is an important part of outreach to users. Although the Apache developer community is firmly rooted in mailing lists, we know that our users live in a different world. If we want to engage with them we need to use the tools that they use, and communicate the way they communicate. Now that we're very close to the AOO 3.4 release, I'd like to start with a project Twitter account, under PPMC control. By under PPMC control I mean something similar to how we treat the project blog: -- Any PPMC member, upon request, can have write access. -- We can use the project's official logo in conjunction with the account. -- We would promote the account on our project's website. -- We would generally treat the account as an official voice of the project, not as a personal account. I'm not saying we need to pre-review and and approve every tweet sent through the account. But we should set expectations that the account is to be used in a professional fashion, upholding the standards of this project, not used to settle personal disputes, to promote personal business, etc. There are already several Twitter accounts that use the OOo name or trademarks: http://twitter.com/#!/openofficeorg --- This account has 1571 followers. But it is not sharing any AOO status, no links to blog posts, announcements, etc. Who controls it? Are we able to get it under PPMC control? Can we rebrand it as Apache OpenOffice? http://twitter.com/#!/openoffice -- This account seems unused. Only one tweet. http://twitter.com/#!/freeopenoffice -- spammer account. Links to http://www.downloadopenofficefree.com/. http://twitter.com/#!/ApacheOO -- I created this account, though have never used it. Unfortunately, Apache OpenOffice is too long for a Twitter account name. So ApacheOO is the closest I got. I would offer this account to the PPMC if we are not able to get use of the http://twitter.com/#!/openofficeorg account. Proposed actions: 1) I'll send note (or Tweet) to http://twitter.com/#!/openofficeorg acccount, asking if the owner would be willing to make the account available to the AOO PPMC for project use. If we get a favorable response then we would start using that account, rebrand it, promote it, etc. 2) If there is no favorable response to the above, then we would go forward with promoting the http://twitter.com/#!/ApacheOO account. 3) The PPMC could decide, at a later point, to invoke Twitter's trademark policy to register complaints about accounts that misuse our trademarks in ways that harm our users: https://support.twitter.com/articles/18367. But I don't see an imminent need for that. -Rob
Re: Question about OOo, AOO
Thank you, Andre! Yes, in different process, not threads. Do you think it is possible to make such AOO? If possible, could you suggest how to solve this problem? What source to look, what funstions, classes, etc. I'll be glad for any help) Regards, Nikolay 11 апреля 2012 г. 5:38 пользователь Andre Fischer a...@a-w-f.de написал: Hi Nikolay, On 11.04.2012 02:02, Ochirov Nikolay wrote: Thank you very much, Regina! I just noticed that the AOO open all documents in one process, it became interesting. But I would like to write code that would do so would AOO every single document open in a single process))) I began to look as it does AOO, found the function OfficeIPCThread :: EnableOfficeIPCThread (), changed code a bit. Hm, you are talking about running AOO in different processes not threads, right? Both approaches pose different difficulties. Using multiple threads (which we do to some small extend) would require our base libraries do be thread safe. Which they are not as far as I know. Using different processes might lead to all dlls loaded several times (from the top of my head I don´t know if they can be shared over process boundaries) and thereby multiplying our memory consumption. Regards, Andre But it didn't work - first document is opened, while others will not open. AOO gives a messgebox The application cannot be started. [context = user] caught unexpected exception! (user - my account in system, system - Ubuntu) I have no much experience in this question in particular and programming in general. If anyone will be willing to help with this - I will be very happy! Regards, Nikolay 10 апреля 2012 г. 21:09 пользователь Regina Henschel rb.hensc...@t-online.de написал: Hi Nikolay, Ochirov Nikolay schrieb: Hello! I hope I haven't t bothered with my questions. But I don't have anyone to ask for advice, so I rely on your wisdom, the Jedi of this mailing list So, Why AOO all documents open in a single process? Has anyone tried to make AOO open documents in different processes? Why do you want to do it? This things are possible: Generate a folder for a second user. Call AOO with the -env parameter. You get one process, but two different users. For example one user can use a German UI and the other user can use an English UI. Install the AOO in administrative mode with setting a different user path on bootstrap.ini. Then you can run two processes soffice.exe. If a user starts soffice.exe he gets a .lock file in his user directory, which prevents, that soffice.exe is started a second time for the same user. Kind regards Regina
Re: Linux builds
On 4/11/12 2:18 PM, Ariel Constenla-Haile wrote: Hi Andre, * On Wed, Apr 11, 2012 at 09:57:35AM +0800, Andre Fischer wrote: Does anybody have tested an upgrade installation with these new Linux packages and can verify the reported problem, see https://issues.apache.org/ooo/show_bug.cgi?id=119162 I think we haven't noticed this problem before and I would be interested if others can confirm this problem. I will be offline for ~1 day because of traveling and I will make the call for VOTE depending on the feedback from you. Old basis package set remaining is the default behaviour, at least tested with OOo 3.0.0. On Fedora 16: - install OOo 3.0.0 (OOO300_m9 9358) - install OOo 3.1.1 (OOO310_m19 9420) 1) there is an issue with the desktop integration, same for AOO 2) the old basis3.0 remains: /opt/openoffice.org/basis3.0 /opt/openoffice.org/basis3.1 All ooobasis3.0 packages are kept. Strange. Here is what I would expect would happen on an update: - There is one top-level or meta package that has dependencies on all the other packages (directly or indirectly) - This meta package of OOo3.? is replaced by AOO3.4 - The packages of OOo3.? are not referenced anymore and get removed automatically. The new packages are installed. Everything is find. So one of the following things goes wrong: - The old meta package is not removed because the new one has no relationship to it (maybe because of a different application name) - The old meta package is removed but some other package keeps a reference to one of OOo3.? base packages. - Something else that I did not think of yet (I am currently on a business trip and am still adapting to the new time zone) There are different issues. The main one is that the package name containes %OOOBASEVERSION Example: module = gid_Module_Prg_Wrt_Bin main/setup_native/source/packinfo/packinfo_office.txt#88 packagename = %BASISPACKAGEPREFIX%OOOBASEVERSION-writer %BASISPACKAGEPREFIX -- ooobasis main/instsetoo_native/util/openoffice.lst#20 %OOOBASEVERSION -- 3.4 main/instsetoo_native/util/openoffice.lst#7 I have installed following packages: ooobasis3.4-writer 3.4.0-9590 ooobasis3.0-writer 3.0.0-9358 ooobasis3.1-writer 3.1.1-9420 ooobasis3.2-writer 3.2.1-9502 ooobasis3.3-writer 3.3.0-9567 Because the *package* name is different, they are indeed different packages, ooobasis3.2-writer is *not* regarded as an update for ooobasis3.1-writer, and so on. ooobasis3.2-writer 3.2.1-9502 can only be updated by a package with the same name, examples: ooobasis3.2-writer 3.2.1-9503 (increase BUILD in main/solenv/inc/minor.mk#23) ooobasis3.2-writer 3.2.2-9502 etc. Note that I'm not sure if this is an issue, or it is the way it was designed with the idea of having different basis installations. The only solution in this strange design is to declare a package obsoleting the other ones, for example ooobasis3.4-writer obsoleting ooobasis3.0-writer ooobasis3.1-writer ooobasis3.2-writer ooobasis3.3-writer This can be done using linuxreplaces in the files on main/setup_native/source/packinfo/ I've tried this is success (though minimal testing): http://people.apache.org/~arielch/packages/yum-update-fix.txt There are some caveats: * A meta package is not enough, this has to be done on a per-packages way, not only to be in the safe side (if the user tries to install some package without the rest), but mainly because previous versions (and the current one) do not have a *real* meta package. The package openoffice.org3 gid_Module_Root_Brand does not provide every package OOo shipped in the tar file, see next point. * gid_Module_Root_Brand requires %UREPACKAGEPREFIX-ure %BASISPACKAGEPREFIX%OOOBASEVERSION-core01 %BASISPACKAGEPREFIX%OOOBASEVERSION-core02 %BASISPACKAGEPREFIX%OOOBASEVERSION-core03 %BASISPACKAGEPREFIX%OOOBASEVERSION-core04 %BASISPACKAGEPREFIX%OOOBASEVERSION-core05 %BASISPACKAGEPREFIX%OOOBASEVERSION-core06 %BASISPACKAGEPREFIX%OOOBASEVERSION-core07 %BASISPACKAGEPREFIX%OOOBASEVERSION-images When you install openoffice.org3 from AOO 3.4.0 over openoffice.org3 from 3.3.0, it only gets updated because they have the same name. It also updates the URE (due to same name, too). It installs basis core01-07 and basis images, but does not update/remove previous packages because the name is different. Besides, this sort of meta package does not install the office modules (writer, calc, etc). * Apache OpenOffice orphans some packages that are no longer present: In the basis layer: oooimprovement kde-integration [yes, AOO has no KDE integration] In the brand layer, OOo 3.3 installed by default 3 dictionaries: openoffice.org3-dict-en openoffice.org3-dict-es openoffice.org3-dict-fr These can all be obsoleted in openoffice.org3 In short, gid_Module_Root_Brand can be made a real meta package, and linuxreplaces is the only solution to remove old basis packages. (I still
Re: Sal Shadow API on Solaris
Hello I did that error when copypasting the path in the mail. The file actually is main/sal/osl/unx/system.h So the build-system should define OLD_SHADOW_API on OpenSolaris? Best, Jean On 02.04.2012, at 17:32, Pedro Giffuni wrote: Hmm... this sounds wrong:for Solaris you should be including sal/osl/unx/system.hnot the OS2 header. Pedro. --- Lun 2/4/12, Jean-Louis 'Hans' Fuchs jean-louis.fu...@adfinis-sygroup.ch ha scritto: ... Hello main/sal/osl/os2/system.h 586 #ifdef OLD_SHADOW_API587 if (getspnam_r(pszUserName, spwdStruct, buffer, sizeof buffer) != NULL)588 #else589 if (getspnam_r(pszUserName, spwdStruct, buffer, sizeof buffer, NULL) == 0)590 #endif The build on OpenSolaris 2009.06 fails because it has the 4 param function. I defined OLD_SHADOW_API and it works. IMO it should be defined by the build-env. Best, Jean-Louis -- Adfinis SyGroup AG Jean-Louis 'Hans' Fuchs, Software Engineer Keltenstrasse 98 | CH-3018 Bern Tel.: +41 31 550 31 11 | http://www.adfinis-sygroup.ch -- Adfinis SyGroup AG Jean-Louis 'Hans' Fuchs, Software Engineer Keltenstrasse 98 | CH-3018 Bern Tel.: +41 31 550 31 11 | http://www.adfinis-sygroup.ch signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Linux Build Problem, Bug 119162 can be taken as NOT Show stopper with record the issue in release note
On 04/11/2012 01:10 AM, xia zhao wrote: Hi all, We have talked a lot about linux build upgrade problem, as the issue 119162 reported. Personally I think it can be taken as NOT AOO 3.4 RC build show stopper. But we need document this limition and give workaround there in release note. Best regrads, Lily yes...my feeling as well...I am going to start working on an upgrade (a new page not an overwrite until we're ready) on our Installation Instruction page later today... http://www.openoffice.org/download/common/instructions.html I will include this info for Linux. -- MzK Women and cats will do as they please, and men and dogs should relax and get used to the idea. -- Robert Heinlein
Re: Apache OpenOffice Project Twitter Account
On Wed, Apr 11, 2012 at 4:09 PM, Rob Weir robw...@apache.org wrote: Social media outreach, via Twitter, Facebook, Google+, etc., is an important part of outreach to users. Although the Apache developer community is firmly rooted in mailing lists, we know that our users live in a different world. If we want to engage with them we need to use the tools that they use, and communicate the way they communicate. Now that we're very close to the AOO 3.4 release, I'd like to start with a project Twitter account, under PPMC control. By under PPMC control I mean something similar to how we treat the project blog: -- Any PPMC member, upon request, can have write access. -- We can use the project's official logo in conjunction with the account. -- We would promote the account on our project's website. -- We would generally treat the account as an official voice of the project, not as a personal account. I'm not saying we need to pre-review and and approve every tweet sent through the account. But we should set expectations that the account is to be used in a professional fashion, upholding the standards of this project, not used to settle personal disputes, to promote personal business, etc. An option could be to agree on a simple guideline for that, so that everyone knows how to handle it. I'm thinking not only about the style of communication, but also about who to follow, how to engage in conversations, improve outreach, etc. There are already several Twitter accounts that use the OOo name or trademarks: http://twitter.com/#!/openofficeorg --- This account has 1571 followers. But it is not sharing any AOO status, no links to blog posts, announcements, etc. Who controls it? Are we able to get it under PPMC control? Can we rebrand it as Apache OpenOffice? That could be a good starting point, I think. It seems like if you're the only one who can send DM to the actual owner's account. http://twitter.com/#!/openoffice -- This account seems unused. Only one tweet. I'd try to get that it too. It's better than ApacheOO, and you might want to put the full name in the Settings Account Name. Roberto http://twitter.com/#!/freeopenoffice -- spammer account. Links to http://www.downloadopenofficefree.com/. http://twitter.com/#!/ApacheOO -- I created this account, though have never used it. Unfortunately, Apache OpenOffice is too long for a Twitter account name. So ApacheOO is the closest I got. I would offer this account to the PPMC if we are not able to get use of the http://twitter.com/#!/openofficeorg account. Proposed actions: 1) I'll send note (or Tweet) to http://twitter.com/#!/openofficeorg acccount, asking if the owner would be willing to make the account available to the AOO PPMC for project use. If we get a favorable response then we would start using that account, rebrand it, promote it, etc. 2) If there is no favorable response to the above, then we would go forward with promoting the http://twitter.com/#!/ApacheOO account. 3) The PPMC could decide, at a later point, to invoke Twitter's trademark policy to register complaints about accounts that misuse our trademarks in ways that harm our users: https://support.twitter.com/articles/18367. But I don't see an imminent need for that. -Rob This e- mail message is intended only for the named recipient(s) above. It may contain confidential and privileged information. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and delete the message and any attachment(s) from your system. Thank you.
Re: Apache OpenOffice Project Twitter Account
On Apr 11, 2012, at 7:09 AM, Rob Weir wrote: Social media outreach, via Twitter, Facebook, Google+, etc., is an important part of outreach to users. Although the Apache developer community is firmly rooted in mailing lists, we know that our users live in a different world. If we want to engage with them we need to use the tools that they use, and communicate the way they communicate. Now that we're very close to the AOO 3.4 release, I'd like to start with a project Twitter account, under PPMC control. By under PPMC control I mean something similar to how we treat the project blog: -- Any PPMC member, upon request, can have write access. -- We can use the project's official logo in conjunction with the account. -- We would promote the account on our project's website. -- We would generally treat the account as an official voice of the project, not as a personal account. I'm not saying we need to pre-review and and approve every tweet sent through the account. But we should set expectations that the account is to be used in a professional fashion, upholding the standards of this project, not used to settle personal disputes, to promote personal business, etc. There are already several Twitter accounts that use the OOo name or trademarks: http://twitter.com/#!/openofficeorg --- This account has 1571 followers. But it is not sharing any AOO status, no links to blog posts, announcements, etc. Who controls it? Are we able to get it under PPMC control? Can we rebrand it as Apache OpenOffice? http://twitter.com/#!/openoffice -- This account seems unused. Only one tweet. http://twitter.com/#!/freeopenoffice -- spammer account. Links to http://www.downloadopenofficefree.com/. http://twitter.com/#!/ApacheOO -- I created this account, though have never used it. Unfortunately, Apache OpenOffice is too long for a Twitter account name. So ApacheOO is the closest I got. I would offer this account to the PPMC if we are not able to get use of the http://twitter.com/#!/openofficeorg account. Proposed actions: 1) I'll send note (or Tweet) to http://twitter.com/#!/openofficeorg acccount, asking if the owner would be willing to make the account available to the AOO PPMC for project use. If we get a favorable response then we would start using that account, rebrand it, promote it, etc. 2) If there is no favorable response to the above, then we would go forward with promoting the http://twitter.com/#!/ApacheOO account. 3) The PPMC could decide, at a later point, to invoke Twitter's trademark policy to register complaints about accounts that misuse our trademarks in ways that harm our users: https://support.twitter.com/articles/18367. But I don't see an imminent need for that. (4) Make the project's twitter feed show up as part of www.openoffice.org's main page. See http://www.apache.org/ Latest activity for an example about how this is done using the Apache CMS. Regards, Dave -Rob
Re: Apache OpenOffice Project Twitter Account
On Wed, 2012-04-11 at 17:43 +0200, Roberto Galoppini wrote: On Wed, Apr 11, 2012 at 4:09 PM, Rob Weir robw...@apache.org wrote: Social media outreach, via Twitter, Facebook, Google+, etc., is an important part of outreach to users. Although the Apache developer community is firmly rooted in mailing lists, we know that our users live in a different world. If we want to engage with them we need to use the tools that they use, and communicate the way they communicate. Now that we're very close to the AOO 3.4 release, I'd like to start with a project Twitter account, under PPMC control. By under PPMC control I mean something similar to how we treat the project blog: -- Any PPMC member, upon request, can have write access. -- We can use the project's official logo in conjunction with the account. -- We would promote the account on our project's website. -- We would generally treat the account as an official voice of the project, not as a personal account. I'm not saying we need to pre-review and and approve every tweet sent through the account. But we should set expectations that the account is to be used in a professional fashion, upholding the standards of this project, not used to settle personal disputes, to promote personal business, etc. An option could be to agree on a simple guideline for that, so that everyone knows how to handle it. I'm thinking not only about the style of communication, but also about who to follow, how to engage in conversations, improve outreach, etc. There are already several Twitter accounts that use the OOo name or trademarks: http://twitter.com/#!/openofficeorg --- This account has 1571 followers. But it is not sharing any AOO status, no links to blog posts, announcements, etc. Who controls it? Are we able to get it under PPMC control? Can we rebrand it as Apache OpenOffice? That could be a good starting point, I think. It seems like if you're the only one who can send DM to the actual owner's account. http://twitter.com/#!/openoffice -- This account seems unused. Only one tweet. I'd try to get that it too. It's better than ApacheOO, and you might want to put the full name in the Settings Account Name. Hi Roberto, Rob I just did so now, and followed up with an email to the account contact in the whois database for the domain listed, the linked sub-domain has been dead for a while IIRC, though the main site is alive - anyway, I'll report back when (or if) I hear anything back. //drew snip
Re: Apache OpenOffice Project Twitter Account
On Wed, Apr 11, 2012 at 10:09 AM, Rob Weir robw...@apache.org wrote: Social media outreach, via Twitter, Facebook, Google+, etc., is an important part of outreach to users. Although the Apache developer community is firmly rooted in mailing lists, we know that our users live in a different world. If we want to engage with them we need to use the tools that they use, and communicate the way they communicate. Now that we're very close to the AOO 3.4 release, I'd like to start with a project Twitter account, under PPMC control. By under PPMC control I mean something similar to how we treat the project blog: -- Any PPMC member, upon request, can have write access. -- We can use the project's official logo in conjunction with the account. -- We would promote the account on our project's website. -- We would generally treat the account as an official voice of the project, not as a personal account. I'm not saying we need to pre-review and and approve every tweet sent through the account. But we should set expectations that the account is to be used in a professional fashion, upholding the standards of this project, not used to settle personal disputes, to promote personal business, etc. There are already several Twitter accounts that use the OOo name or trademarks: http://twitter.com/#!/openofficeorg --- This account has 1571 followers. But it is not sharing any AOO status, no links to blog posts, announcements, etc. Who controls it? Are we able to get it under PPMC control? Can we rebrand it as Apache OpenOffice? Hi Alexandro -- Is the above your Twitter account? If so, would you be willing to contribute it to the AOO project, so we can rebrand it and allow other PMC members to have write access to it, etc.? -Rob http://twitter.com/#!/openoffice -- This account seems unused. Only one tweet. http://twitter.com/#!/freeopenoffice -- spammer account. Links to http://www.downloadopenofficefree.com/. http://twitter.com/#!/ApacheOO -- I created this account, though have never used it. Unfortunately, Apache OpenOffice is too long for a Twitter account name. So ApacheOO is the closest I got. I would offer this account to the PPMC if we are not able to get use of the http://twitter.com/#!/openofficeorg account. Proposed actions: 1) I'll send note (or Tweet) to http://twitter.com/#!/openofficeorg acccount, asking if the owner would be willing to make the account available to the AOO PPMC for project use. If we get a favorable response then we would start using that account, rebrand it, promote it, etc. 2) If there is no favorable response to the above, then we would go forward with promoting the http://twitter.com/#!/ApacheOO account. 3) The PPMC could decide, at a later point, to invoke Twitter's trademark policy to register complaints about accounts that misuse our trademarks in ways that harm our users: https://support.twitter.com/articles/18367. But I don't see an imminent need for that. -Rob
Re: Apache OpenOffice Project Twitter Account
On Wed, Apr 11, 2012 at 11:50 AM, Dave Fisher dave2w...@comcast.net wrote: On Apr 11, 2012, at 7:09 AM, Rob Weir wrote: Social media outreach, via Twitter, Facebook, Google+, etc., is an important part of outreach to users. Although the Apache developer community is firmly rooted in mailing lists, we know that our users live in a different world. If we want to engage with them we need to use the tools that they use, and communicate the way they communicate. Now that we're very close to the AOO 3.4 release, I'd like to start with a project Twitter account, under PPMC control. By under PPMC control I mean something similar to how we treat the project blog: -- Any PPMC member, upon request, can have write access. -- We can use the project's official logo in conjunction with the account. -- We would promote the account on our project's website. -- We would generally treat the account as an official voice of the project, not as a personal account. I'm not saying we need to pre-review and and approve every tweet sent through the account. But we should set expectations that the account is to be used in a professional fashion, upholding the standards of this project, not used to settle personal disputes, to promote personal business, etc. There are already several Twitter accounts that use the OOo name or trademarks: http://twitter.com/#!/openofficeorg --- This account has 1571 followers. But it is not sharing any AOO status, no links to blog posts, announcements, etc. Who controls it? Are we able to get it under PPMC control? Can we rebrand it as Apache OpenOffice? http://twitter.com/#!/openoffice -- This account seems unused. Only one tweet. http://twitter.com/#!/freeopenoffice -- spammer account. Links to http://www.downloadopenofficefree.com/. http://twitter.com/#!/ApacheOO -- I created this account, though have never used it. Unfortunately, Apache OpenOffice is too long for a Twitter account name. So ApacheOO is the closest I got. I would offer this account to the PPMC if we are not able to get use of the http://twitter.com/#!/openofficeorg account. Proposed actions: 1) I'll send note (or Tweet) to http://twitter.com/#!/openofficeorg acccount, asking if the owner would be willing to make the account available to the AOO PPMC for project use. If we get a favorable response then we would start using that account, rebrand it, promote it, etc. 2) If there is no favorable response to the above, then we would go forward with promoting the http://twitter.com/#!/ApacheOO account. 3) The PPMC could decide, at a later point, to invoke Twitter's trademark policy to register complaints about accounts that misuse our trademarks in ways that harm our users: https://support.twitter.com/articles/18367. But I don't see an imminent need for that. (4) Make the project's twitter feed show up as part of www.openoffice.org's main page. See http://www.apache.org/ Latest activity for an example about how this is done using the Apache CMS. There is an RSS feed associated with each Twitter account. So we could also integrate that into an OpenOffice Planet if we decide to create that. -Rob Regards, Dave -Rob
fetch_tarball.sh on FreeBSD
Hi Pedro, Do you know some fix for following error message? /work/a/ports/editors/openoffice-3-devel/work/ooo/main/fetch_tarballs.sh: line 54: break: only meaningful in a `for', `while', or `until' loop It looks even though the error, not harm. thanks -- Nakata Maho http://accc.riken.jp/maho/ , JA OOO http://ja.openoffice.org/ http://blog.goo.ne.jp/nakatamaho/ ,GPG: http://accc.riken.jp/maho/maho.pgp.txt
Re: Apache OpenOffice Project Twitter Account
On Wed, Apr 11, 2012 at 11:43 AM, Roberto Galoppini rgalopp...@geek.net wrote: http://twitter.com/#!/openofficeorg --- This account has 1571 followers. But it is not sharing any AOO status, no links to blog posts, announcements, etc. Who controls it? Are we able to get it under PPMC control? Can we rebrand it as Apache OpenOffice? That could be a good starting point, I think. It seems like if you're the only one who can send DM to the actual owner's account. Interesting. I'm one of only two people followed by that account. So I took advantage of that by sending the owners a DM, pointing to this thread and saying we could have a confidential discussion on ooo-private if they preferred. -Rob
Re: Apache OpenOffice Project Twitter Account
On Apr 11, 2012, at 10:41 AM, Rob Weir wrote: On Wed, Apr 11, 2012 at 11:50 AM, Dave Fisher dave2w...@comcast.net wrote: On Apr 11, 2012, at 7:09 AM, Rob Weir wrote: Social media outreach, via Twitter, Facebook, Google+, etc., is an important part of outreach to users. Although the Apache developer community is firmly rooted in mailing lists, we know that our users live in a different world. If we want to engage with them we need to use the tools that they use, and communicate the way they communicate. Now that we're very close to the AOO 3.4 release, I'd like to start with a project Twitter account, under PPMC control. By under PPMC control I mean something similar to how we treat the project blog: -- Any PPMC member, upon request, can have write access. -- We can use the project's official logo in conjunction with the account. -- We would promote the account on our project's website. -- We would generally treat the account as an official voice of the project, not as a personal account. I'm not saying we need to pre-review and and approve every tweet sent through the account. But we should set expectations that the account is to be used in a professional fashion, upholding the standards of this project, not used to settle personal disputes, to promote personal business, etc. There are already several Twitter accounts that use the OOo name or trademarks: http://twitter.com/#!/openofficeorg --- This account has 1571 followers. But it is not sharing any AOO status, no links to blog posts, announcements, etc. Who controls it? Are we able to get it under PPMC control? Can we rebrand it as Apache OpenOffice? http://twitter.com/#!/openoffice -- This account seems unused. Only one tweet. http://twitter.com/#!/freeopenoffice -- spammer account. Links to http://www.downloadopenofficefree.com/. http://twitter.com/#!/ApacheOO -- I created this account, though have never used it. Unfortunately, Apache OpenOffice is too long for a Twitter account name. So ApacheOO is the closest I got. I would offer this account to the PPMC if we are not able to get use of the http://twitter.com/#!/openofficeorg account. Proposed actions: 1) I'll send note (or Tweet) to http://twitter.com/#!/openofficeorg acccount, asking if the owner would be willing to make the account available to the AOO PPMC for project use. If we get a favorable response then we would start using that account, rebrand it, promote it, etc. 2) If there is no favorable response to the above, then we would go forward with promoting the http://twitter.com/#!/ApacheOO account. 3) The PPMC could decide, at a later point, to invoke Twitter's trademark policy to register complaints about accounts that misuse our trademarks in ways that harm our users: https://support.twitter.com/articles/18367. But I don't see an imminent need for that. (4) Make the project's twitter feed show up as part of www.openoffice.org's main page. See http://www.apache.org/ Latest activity for an example about how this is done using the Apache CMS. There is an RSS feed associated with each Twitter account. So we could also integrate that into an OpenOffice Planet if we decide to create that. I'm not talking about a planet. I'm talking about twitter content on the main page updated every hour. We can similarly show the most recent svn commits on the project site. Regards, Dave -Rob Regards, Dave -Rob
Re: fetch_tarball.sh on FreeBSD
--- Mer 11/4/12, Maho NAKATA m...@apache.org ha scritto: Hi Pedro, Do you know some fix for following error message? /work/a/ports/editors/openoffice-3-devel/work/ooo/main/fetch_tarballs.sh: line 54: break: only meaningful in a `for', `while', or `until' loop It looks even though the error, not harm. It's a warning that only appears with bash: the script works silently when using FreeBSD's bin/sh. I was going to say that some bash expert would clean it sooner or later and then I noticed that Dave gave a solution :-P . cheers, Pedro.
Re: Sal Shadow API on Solaris
On 04/11/12 09:48, Jean-Louis 'Hans' Fuchs wrote: Hello I did that error when copypasting the path in the mail. The file actually is main/sal/osl/unx/system.h So the build-system should define OLD_SHADOW_API on OpenSolaris? Best, Jean The outdated OpenGrok didn't find the OLD_SHADOW_API :( Let's see: grep -R OLD_SHADOW_API main/* sal/osl/unx/security.c:#ifdef OLD_SHADOW_API sal/osl/unx/security.c:#ifdef OLD_SHADOW_API apparently no other platform uses OLD_SHADOW_API I would try to reuse any of these two headers included in sal/osl/security.c : #include system.h #include osl/security.h cheers, Pedro. On 02.04.2012, at 17:32, Pedro Giffuni wrote: Hmm... this sounds wrong:for Solaris you should be including sal/osl/unx/system.hnot the OS2 header. Pedro. --- Lun 2/4/12, Jean-Louis 'Hans' Fuchsjean-louis.fu...@adfinis-sygroup.ch ha scritto: ... Hello main/sal/osl/os2/system.h 586 #ifdef OLD_SHADOW_API587 if (getspnam_r(pszUserName,spwdStruct, buffer, sizeof buffer) != NULL)588 #else589 if (getspnam_r(pszUserName,spwdStruct, buffer, sizeof buffer, NULL) == 0)590 #endif The build on OpenSolaris 2009.06 fails because it has the 4 param function. I defined OLD_SHADOW_API and it works. IMO it should be defined by the build-env. Best, Jean-Louis -- Adfinis SyGroup AG Jean-Louis 'Hans' Fuchs, Software Engineer Keltenstrasse 98 | CH-3018 Bern Tel.: +41 31 550 31 11 | http://www.adfinis-sygroup.ch
Re: Apache OpenOffice Project Twitter Account
On Wed, Apr 11, 2012 at 2:42 PM, Dave Fisher dave2w...@comcast.net wrote: On Apr 11, 2012, at 10:41 AM, Rob Weir wrote: On Wed, Apr 11, 2012 at 11:50 AM, Dave Fisher dave2w...@comcast.net wrote: On Apr 11, 2012, at 7:09 AM, Rob Weir wrote: Social media outreach, via Twitter, Facebook, Google+, etc., is an important part of outreach to users. Although the Apache developer community is firmly rooted in mailing lists, we know that our users live in a different world. If we want to engage with them we need to use the tools that they use, and communicate the way they communicate. Now that we're very close to the AOO 3.4 release, I'd like to start with a project Twitter account, under PPMC control. By under PPMC control I mean something similar to how we treat the project blog: -- Any PPMC member, upon request, can have write access. -- We can use the project's official logo in conjunction with the account. -- We would promote the account on our project's website. -- We would generally treat the account as an official voice of the project, not as a personal account. I'm not saying we need to pre-review and and approve every tweet sent through the account. But we should set expectations that the account is to be used in a professional fashion, upholding the standards of this project, not used to settle personal disputes, to promote personal business, etc. There are already several Twitter accounts that use the OOo name or trademarks: http://twitter.com/#!/openofficeorg --- This account has 1571 followers. But it is not sharing any AOO status, no links to blog posts, announcements, etc. Who controls it? Are we able to get it under PPMC control? Can we rebrand it as Apache OpenOffice? http://twitter.com/#!/openoffice -- This account seems unused. Only one tweet. http://twitter.com/#!/freeopenoffice -- spammer account. Links to http://www.downloadopenofficefree.com/. http://twitter.com/#!/ApacheOO -- I created this account, though have never used it. Unfortunately, Apache OpenOffice is too long for a Twitter account name. So ApacheOO is the closest I got. I would offer this account to the PPMC if we are not able to get use of the http://twitter.com/#!/openofficeorg account. Proposed actions: 1) I'll send note (or Tweet) to http://twitter.com/#!/openofficeorg acccount, asking if the owner would be willing to make the account available to the AOO PPMC for project use. If we get a favorable response then we would start using that account, rebrand it, promote it, etc. 2) If there is no favorable response to the above, then we would go forward with promoting the http://twitter.com/#!/ApacheOO account. 3) The PPMC could decide, at a later point, to invoke Twitter's trademark policy to register complaints about accounts that misuse our trademarks in ways that harm our users: https://support.twitter.com/articles/18367. But I don't see an imminent need for that. (4) Make the project's twitter feed show up as part of www.openoffice.org's main page. See http://www.apache.org/ Latest activity for an example about how this is done using the Apache CMS. There is an RSS feed associated with each Twitter account. So we could also integrate that into an OpenOffice Planet if we decide to create that. I'm not talking about a planet. I'm talking about twitter content on the main page updated every hour. I know you are not talking about a planet. I am. And so were others on a previous thread. That is why I mentioned it. -Rob We can similarly show the most recent svn commits on the project site. Regards, Dave -Rob Regards, Dave -Rob
[WWW] Download button on home page footer modification
Hi all-- Right now when you click on the I want to download OpenOffice.org on the home page, you get a LARGE button to click to start the download, but also have an additional footer area with the following links: * Get all platforms and languages * Release notes * MD5 checksums * ISO images * order CD-ROM * P2P downloads I am contemplating chagng Release Notes to More Download Information and routing folks to http://www.openoffice.org/download/index.html which HAS release notes in addition to other information -- installation guides, etc. Does anyone take issue with this relatively minor edit? -- MzK Women and cats will do as they please, and men and dogs should relax and get used to the idea. -- Robert Heinlein
Re: Apache OpenOffice Project Twitter Account
On 4/11/12, Rob Weir robw...@apache.org wrote: On Wed, Apr 11, 2012 at 10:09 AM, Rob Weir robw...@apache.org wrote: Social media outreach, via Twitter, Facebook, Google+, etc., is an important part of outreach to users. Although the Apache developer community is firmly rooted in mailing lists, we know that our users live in a different world. If we want to engage with them we need to use the tools that they use, and communicate the way they communicate. Now that we're very close to the AOO 3.4 release, I'd like to start with a project Twitter account, under PPMC control. By under PPMC control I mean something similar to how we treat the project blog: -- Any PPMC member, upon request, can have write access. -- We can use the project's official logo in conjunction with the account. -- We would promote the account on our project's website. -- We would generally treat the account as an official voice of the project, not as a personal account. I'm not saying we need to pre-review and and approve every tweet sent through the account. But we should set expectations that the account is to be used in a professional fashion, upholding the standards of this project, not used to settle personal disputes, to promote personal business, etc. There are already several Twitter accounts that use the OOo name or trademarks: http://twitter.com/#!/openofficeorg --- This account has 1571 followers. But it is not sharing any AOO status, no links to blog posts, announcements, etc. Who controls it? Are we able to get it under PPMC control? Can we rebrand it as Apache OpenOffice? Hi Alexandro -- Is the above your Twitter account? If so, would you be willing to contribute it to the AOO project, so we can rebrand it and allow other PMC members to have write access to it, etc.? Not sure what u mean to contribute it to AOO project, is that a specific email? I can rebrand it, the account used to sit on a service that allow multiple people to manage it, unfortunately the service is no longer being offered. So I need to look for something similar. -Rob http://twitter.com/#!/openoffice -- This account seems unused. Only one tweet. http://twitter.com/#!/freeopenoffice -- spammer account. Links to http://www.downloadopenofficefree.com/. http://twitter.com/#!/ApacheOO -- I created this account, though have never used it. Unfortunately, Apache OpenOffice is too long for a Twitter account name. So ApacheOO is the closest I got. I would offer this account to the PPMC if we are not able to get use of the http://twitter.com/#!/openofficeorg account. Proposed actions: 1) I'll send note (or Tweet) to http://twitter.com/#!/openofficeorg acccount, asking if the owner would be willing to make the account available to the AOO PPMC for project use. If we get a favorable response then we would start using that account, rebrand it, promote it, etc. 2) If there is no favorable response to the above, then we would go forward with promoting the http://twitter.com/#!/ApacheOO account. 3) The PPMC could decide, at a later point, to invoke Twitter's trademark policy to register complaints about accounts that misuse our trademarks in ways that harm our users: https://support.twitter.com/articles/18367. But I don't see an imminent need for that. -Rob -- Alexandro Colorado OpenOffice.org Español http://es.openoffice.org
Re: Linux builds
On 04/11/2012 07:45 AM, � wrote: On 4/11/12 2:18 PM, Ariel Constenla-Haile wrote: Hi Andre, * On Wed, Apr 11, 2012 at 09:57:35AM +0800, Andre Fischer wrote: Does anybody have tested an upgrade installation with these new Linux packages and can verify the reported problem, see https://issues.apache.org/ooo/show_bug.cgi?id=119162 I think we haven't noticed this problem before and I would be interested if others can confirm this problem. I will be offline for ~1 day because of traveling and I will make the call for VOTE depending on the feedback from you. Old basis package set remaining is the default behaviour, at least tested with OOo 3.0.0. On Fedora 16: - install OOo 3.0.0 (OOO300_m9 9358) - install OOo 3.1.1 (OOO310_m19 9420) 1) there is an issue with the desktop integration, same for AOO 2) the old basis3.0 remains: /opt/openoffice.org/basis3.0 /opt/openoffice.org/basis3.1 All ooobasis3.0 packages are kept. Strange. Here is what I would expect would happen on an update: - There is one top-level or meta package that has dependencies on all the other packages (directly or indirectly) - This meta package of OOo3.? is replaced by AOO3.4 - The packages of OOo3.? are not referenced anymore and get removed automatically. The new packages are installed. Everything is find. So one of the following things goes wrong: - The old meta package is not removed because the new one has no relationship to it (maybe because of a different application name) - The old meta package is removed but some other package keeps a reference to one of OOo3.? base packages. - Something else that I did not think of yet (I am currently on a business trip and am still adapting to the new time zone) There are different issues. The main one is that the package name containes %OOOBASEVERSION Example: module = gid_Module_Prg_Wrt_Bin main/setup_native/source/packinfo/packinfo_office.txt#88 packagename = %BASISPACKAGEPREFIX%OOOBASEVERSION-writer %BASISPACKAGEPREFIX -- ooobasis main/instsetoo_native/util/openoffice.lst#20 %OOOBASEVERSION -- 3.4 main/instsetoo_native/util/openoffice.lst#7 I have installed following packages: ooobasis3.4-writer 3.4.0-9590 ooobasis3.0-writer 3.0.0-9358 ooobasis3.1-writer 3.1.1-9420 ooobasis3.2-writer 3.2.1-9502 ooobasis3.3-writer 3.3.0-9567 Because the *package* name is different, they are indeed different packages, ooobasis3.2-writer is *not* regarded as an update for ooobasis3.1-writer, and so on. ooobasis3.2-writer 3.2.1-9502 can only be updated by a package with the same name, examples: ooobasis3.2-writer 3.2.1-9503 (increase BUILD in main/solenv/inc/minor.mk#23) ooobasis3.2-writer 3.2.2-9502 etc. Note that I'm not sure if this is an issue, or it is the way it was designed with the idea of having different basis installations. The only solution in this strange design is to declare a package obsoleting the other ones, for example ooobasis3.4-writer obsoleting ooobasis3.0-writer ooobasis3.1-writer ooobasis3.2-writer ooobasis3.3-writer This can be done using linuxreplaces in the files on main/setup_native/source/packinfo/ I've tried this is success (though minimal testing): http://people.apache.org/~arielch/packages/yum-update-fix.txt There are some caveats: * A meta package is not enough, this has to be done on a per-packages way, not only to be in the safe side (if the user tries to install some package without the rest), but mainly because previous versions (and the current one) do not have a *real* meta package. The package openoffice.org3 gid_Module_Root_Brand does not provide every package OOo shipped in the tar file, see next point. * gid_Module_Root_Brand requires %UREPACKAGEPREFIX-ure %BASISPACKAGEPREFIX%OOOBASEVERSION-core01 %BASISPACKAGEPREFIX%OOOBASEVERSION-core02 %BASISPACKAGEPREFIX%OOOBASEVERSION-core03 %BASISPACKAGEPREFIX%OOOBASEVERSION-core04 %BASISPACKAGEPREFIX%OOOBASEVERSION-core05 %BASISPACKAGEPREFIX%OOOBASEVERSION-core06 %BASISPACKAGEPREFIX%OOOBASEVERSION-core07 %BASISPACKAGEPREFIX%OOOBASEVERSION-images When you install openoffice.org3 from AOO 3.4.0 over openoffice.org3 from 3.3.0, it only gets updated because they have the same name. It also updates the URE (due to same name, too). It installs basis core01-07 and basis images, but does not update/remove previous packages because the name is different. Besides, this sort of meta package does not install the office modules (writer, calc, etc). * Apache OpenOffice orphans some packages that are no longer present: In the basis layer: oooimprovement kde-integration [yes, AOO has no KDE integration] Ariel -- Well...my kde integration seems to be provided in: openoffice.org3.4-suse-menus-3.4-9590.noarch.rpm from the desktop-integration directory using the older kde3 integration which works just fine. But maybe this is referring to is some older holdover that is no longer viable. In the brand layer, OOo 3.3 installed by default 3 dictionaries: openoffice.org3-dict-en openoffice.org3-dict-es
Re: Apache OpenOffice Project Twitter Account
On Wed, Apr 11, 2012 at 4:16 PM, Alexandro Colorado j...@apache.org wrote: On 4/11/12, Rob Weir robw...@apache.org wrote: On Wed, Apr 11, 2012 at 10:09 AM, Rob Weir robw...@apache.org wrote: Social media outreach, via Twitter, Facebook, Google+, etc., is an important part of outreach to users. Although the Apache developer community is firmly rooted in mailing lists, we know that our users live in a different world. If we want to engage with them we need to use the tools that they use, and communicate the way they communicate. Now that we're very close to the AOO 3.4 release, I'd like to start with a project Twitter account, under PPMC control. By under PPMC control I mean something similar to how we treat the project blog: -- Any PPMC member, upon request, can have write access. -- We can use the project's official logo in conjunction with the account. -- We would promote the account on our project's website. -- We would generally treat the account as an official voice of the project, not as a personal account. I'm not saying we need to pre-review and and approve every tweet sent through the account. But we should set expectations that the account is to be used in a professional fashion, upholding the standards of this project, not used to settle personal disputes, to promote personal business, etc. There are already several Twitter accounts that use the OOo name or trademarks: http://twitter.com/#!/openofficeorg --- This account has 1571 followers. But it is not sharing any AOO status, no links to blog posts, announcements, etc. Who controls it? Are we able to get it under PPMC control? Can we rebrand it as Apache OpenOffice? Hi Alexandro -- Is the above your Twitter account? If so, would you be willing to contribute it to the AOO project, so we can rebrand it and allow other PMC members to have write access to it, etc.? Not sure what u mean to contribute it to AOO project, is that a specific email? I can rebrand it, the account used to sit on a service that allow multiple people to manage it, unfortunately the service is no longer being offered. So I need to look for something similar. Hi Alexandro, Sorry, this probably makes more sense if you read the thread from the start: http://markmail.org/message/f3o37t2ostyqe3sy By contribute to the AOO project I mean give control to the AOO PMC, so we can use it as a project-wide account, similar to how we treat the blog: -- Any PPMC member, upon request, can have write access. -- We can use the project's official logo in conjunction with the account. -- We would promote the account on our project's website. -- We would generally treat the account as an official voice of the project, not as a personal account. To implement this sort of group control we would need to look at some service like BirdHerd or similar for individual authors, and then have the root login given to Apache Infra to store securely. Or something like that. -Rob -Rob http://twitter.com/#!/openoffice -- This account seems unused. Only one tweet. http://twitter.com/#!/freeopenoffice -- spammer account. Links to http://www.downloadopenofficefree.com/. http://twitter.com/#!/ApacheOO -- I created this account, though have never used it. Unfortunately, Apache OpenOffice is too long for a Twitter account name. So ApacheOO is the closest I got. I would offer this account to the PPMC if we are not able to get use of the http://twitter.com/#!/openofficeorg account. Proposed actions: 1) I'll send note (or Tweet) to http://twitter.com/#!/openofficeorg acccount, asking if the owner would be willing to make the account available to the AOO PPMC for project use. If we get a favorable response then we would start using that account, rebrand it, promote it, etc. 2) If there is no favorable response to the above, then we would go forward with promoting the http://twitter.com/#!/ApacheOO account. 3) The PPMC could decide, at a later point, to invoke Twitter's trademark policy to register complaints about accounts that misuse our trademarks in ways that harm our users: https://support.twitter.com/articles/18367. But I don't see an imminent need for that. -Rob -- Alexandro Colorado OpenOffice.org Español http://es.openoffice.org
Re: [WWW] Download button on home page footer modification
Am 04/11/2012 10:07 PM, schrieb Kay Schenk: Hi all-- Right now when you click on the I want to download OpenOffice.org on the home page, you get a LARGE button to click to start the download, but also have an additional footer area with the following links: * Get all platforms and languages * Release notes * MD5 checksums * ISO images * order CD-ROM * P2P downloads I am contemplating chagng Release Notes to More Download Information and routing folks to http://www.openoffice.org/download/index.html which HAS release notes in addition to other information -- installation guides, etc. I remember there was already the link Other platforms and languages which referred to the other.html webpage. I just added some others (over the time) to point the users directly to the wished information, so that they don't need to go over the download area. Today it's maybe a bit too much information. I don't know. ;-) Does anyone take issue with this relatively minor edit? You mean under the green download button there will be only the following? Get all platforms and languages | More Download Information If so, go for it. Marcus
Re: [WWW] Download button on home page footer modification
On 04/11/2012 02:52 PM, Marcus (OOo) wrote: Am 04/11/2012 10:07 PM, schrieb Kay Schenk: Hi all-- Right now when you click on the I want to download OpenOffice.org on the home page, you get a LARGE button to click to start the download, but also have an additional footer area with the following links: * Get all platforms and languages * Release notes * MD5 checksums * ISO images * order CD-ROM * P2P downloads I am contemplating chagng Release Notes to More Download Information and routing folks to http://www.openoffice.org/download/index.html which HAS release notes in addition to other information -- installation guides, etc. I remember there was already the link Other platforms and languages which referred to the other.html webpage. I just added some others (over the time) to point the users directly to the wished information, so that they don't need to go over the download area. Today it's maybe a bit too much information. I don't know. ;-) I understand. Oddly this page you're referring to does not include either release notes, or installation instructions which I why I want to do this. Does anyone take issue with this relatively minor edit? You mean under the green download button there will be only the following? Get all platforms and languages | More Download Information oh hey! I was going to leave the other stuff on DL options but your suggestion is even better since the page I want to use already contains that! Good call, Marcus! :) If so, go for it. Marcus -- MzK Women and cats will do as they please, and men and dogs should relax and get used to the idea. -- Robert Heinlein
Re: Linux builds
Hi Kay, On Wed, Apr 11, 2012 at 01:28:38PM -0700, Kay Schenk wrote: * Apache OpenOffice orphans some packages that are no longer present: In the basis layer: oooimprovement kde-integration [yes, AOO has no KDE integration] Ariel -- Well...my kde integration seems to be provided in: openoffice.org3.4-suse-menus-3.4-9590.noarch.rpm from the desktop-integration directory using the older kde3 integration which works just fine. But maybe this is referring to is some older holdover that is no longer viable. KDE integration is the package ooobasis3.3-kde-integration It provides /opt/openoffice.org/basis3.3/program/kdebe1.uno.so source code on main/shell/source/backends/kdebe It is the shell/desktop integration, allowing to get some information from the KDE desktop env., like the default external mailer program, etc. See main/shell/source/backends/kdebe/kdeaccess.cxx#51 main/shell/source/backends/kdebe/kdebackend.cxx#180 And I also mean the VCL plugin that makes AOO look like a KDE 3/4 application, and the KDE file dialog. KDE 4 was never integrated in OOo (there was a CWS trying to do so), and last time I tried to compile with kde4 enabled, the plug-in was rather broken (we need someone to maintain it, otherwise it's death code). Regards -- Ariel Constenla-Haile La Plata, Argentina pgplOaAUrVDhW.pgp Description: PGP signature
Re: Linux builds
On Wed, Apr 11, 2012 at 09:18:14AM -0300, Ariel Constenla-Haile wrote: In short, gid_Module_Root_Brand can be made a real meta package, and linuxreplaces is the only solution to remove old basis packages. (I still didn't look at the desktop integration package issue) The desktop integration is built on trunk/main/sysui without the epm thingy. The root problem was the same: file $FILE from install of openoffice.org3.1-redhat-menus-3.1-9420.noarch conflicts with file from package openoffice.org3.0-redhat-menus-3.0-9354.noarch The package names are different, so a newer package is not regarded by default as update to the older package: openoffice.org3.0-redhat-menus openoffice.org3.1-redhat-menus The solution: openoffice.org3.4-redhat-menus must obsolete the following packages openoffice.org3.0-redhat-menus openoffice.org3.1-redhat-menus openoffice.org3.2-redhat-menus openoffice.org3.3-redhat-menus http://people.apache.org/~arielch/packages/rpm-desktop-integration-fixed.txt Regards -- Ariel Constenla-Haile La Plata, Argentina pgptRm3y6zqqs.pgp Description: PGP signature
[BUILD][RELEASE] Dictionaries on language packs
Hi *, IIRC language packs came with dictionaries. That way you could install a generic en-US install set and then add language packs providing translated Help, resource strings, and dictionaries. Now the dictionaries are installed only on full localized install sets, but not in the language packs, at least on Linux (didn't try on Win). Is this as-designed or an issue with the Linux builds? Are language packs still supposed to install dictionaries? Regards -- Ariel Constenla-Haile La Plata, Argentina pgponwHvO48XU.pgp Description: PGP signature
Re: [ooo-site]
On Mon, Apr 9, 2012 at 5:58 AM, Lars Bo Christensen lar...@it.dk wrote: This link on danish frontpage does not work: http://download.services.openoffice.org/files/localized/da/3.2.1/OOo_3.2.1_Win_x86_install_da.exe Thanks Hi Lars, I don't see this link to the 3.2.1 version of OpenOffice.org. I only see links to the 3.3.0 version. Am I missing something? http://www.openoffice.org/da/ But in general this page is out of date. It does not mention the move to Apache at all, though it announces LibreOffice releases. A curious thing for an AOO website. Is anyone maintaining this page? Does anyone want to volunteer? -Rob
Re: [ooo-site]
Rob, You are missing that Kay changed the subject and then had a back and forth with Marcus to solve this trouble. Best Regards, Dave On Apr 11, 2012, at 6:25 PM, Rob Weir wrote: On Mon, Apr 9, 2012 at 5:58 AM, Lars Bo Christensen lar...@it.dk wrote: This link on danish frontpage does not work: http://download.services.openoffice.org/files/localized/da/3.2.1/OOo_3.2.1_Win_x86_install_da.exe Thanks Hi Lars, I don't see this link to the 3.2.1 version of OpenOffice.org. I only see links to the 3.3.0 version. Am I missing something? http://www.openoffice.org/da/ But in general this page is out of date. It does not mention the move to Apache at all, though it announces LibreOffice releases. A curious thing for an AOO website. Is anyone maintaining this page? Does anyone want to volunteer? -Rob
Re: Linux Build Problem, Bug 119162 can be taken as NOT Show stopper with record the issue in release note
Thanks Kay, installation instruction is one good place to document the linux upgrade issue. Lily 2012/4/11 Kay Schenk kay.sch...@gmail.com On 04/11/2012 01:10 AM, xia zhao wrote: Hi all, We have talked a lot about linux build upgrade problem, as the issue 119162 reported. Personally I think it can be taken as NOT AOO 3.4 RC build show stopper. But we need document this limition and give workaround there in release note. Best regrads, Lily yes...my feeling as well...I am going to start working on an upgrade (a new page not an overwrite until we're ready) on our Installation Instruction page later today... http://www.openoffice.org/**download/common/instructions.**htmlhttp://www.openoffice.org/download/common/instructions.html I will include this info for Linux. -- --**--** MzK Women and cats will do as they please, and men and dogs should relax and get used to the idea. -- Robert Heinlein
Re: [ooo-site]
On Wed, Apr 11, 2012 at 9:33 PM, Dave Fisher dave2w...@comcast.net wrote: Rob, You are missing that Kay changed the subject and then had a back and forth with Marcus to solve this trouble. And the end result is that the page still says nothing about Apache, incubation or how to get involved with the project? I dunno about you, but I think we still have a problem. -Rob Best Regards, Dave On Apr 11, 2012, at 6:25 PM, Rob Weir wrote: On Mon, Apr 9, 2012 at 5:58 AM, Lars Bo Christensen lar...@it.dk wrote: This link on danish frontpage does not work: http://download.services.openoffice.org/files/localized/da/3.2.1/OOo_3.2.1_Win_x86_install_da.exe Thanks Hi Lars, I don't see this link to the 3.2.1 version of OpenOffice.org. I only see links to the 3.3.0 version. Am I missing something? http://www.openoffice.org/da/ But in general this page is out of date. It does not mention the move to Apache at all, though it announces LibreOffice releases. A curious thing for an AOO website. Is anyone maintaining this page? Does anyone want to volunteer? -Rob
Re: update fails
Hi William, Would you please try the r1309668 or the r1310206 build on: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots? I never use build 9567, but for AOO 3.4, three latest dev builds ago, the package name is still dev package name and not the production name. And upgrade will install a new version on it. I have tried the above two build on my Mac lion and the upgrade work well. Best regards, Lily 2012/4/12 william kenneweg wkenne...@cablespeed.com Hi. Everytime I try to check for update it fails on my mac. 'm using build 9567. help.
Re: [ooo-site]
Am 12.04.12 03:40, schrieb Rob Weir: On Wed, Apr 11, 2012 at 9:33 PM, Dave Fisher dave2w...@comcast.net wrote: Rob, You are missing that Kay changed the subject and then had a back and forth with Marcus to solve this trouble. And the end result is that the page still says nothing about Apache, incubation or how to get involved with the project? I dunno about you, but I think we still have a problem. The Feed is from the http://www.oooforum.dk/ so it's not maintained by OOo. I think we have no danish people here atm who can make a update. I propose to delete this feed on the dk site to avoid confusion. The update from the site is a different storry. but this problem exist on the moast NLC pages Greetings Raphael -- My private Homepage: http://www.raphaelbircher.ch/
Re: [WWW] Translating branding and navigation
On Wed, Apr 11, 2012 at 11:47 AM, Dave Fisher dave2w...@comcast.net wrote: Hi - es, de, nl, fi, pt-br, ru, and ja are now setup for committers to make translations to brand.mdtext and topnav.mdtext. I still have the question about Chinese / zh split regarding traditional / simplified (Taiwan / Mainland) Next languages? cs, hu? Please respond for the next NL set. brand.mdtext === home: home search: search name: Apache OpenOffice (incubating) tagline: (incubating) | The Free and Open Productivity Suite logo: AOO_logos/OOo_Website_v2_copy.png domain: www.openoffice.org divid: bannera topnav.mdtext divid: topnava - [Product][m0] - [Download][m1] - [Support][m2] - [Extend][m3] - [Develop][m4] - [Focus Areas][m5] - [Native Language][m6] [m0]: /product/index.html Apache OpenOffice product description [m1]: /download/index.html Download OpenOffice.org [m2]: /support/index.html Find Support for OpenOffice.org [m3]: /extensions/index.html Extensions and Templates for OpenOffice [m4]: http://incubator.apache.org/openofficeorg/get-involved.html Get involved in Apache OpenOffice (incubating) [m5]: /projects/accepted.html Apache OpenOffice development focus areas [m6]: /projects/native-lang.html Apache OpenOffice in your Native Language Dave, I speak English and I have no idea what you are talking about here. We need to *radically simplify* how the web pages are translated. No MDText. No Apache CMS. No command line. No markup. No angle brackets. These are translators, not web designers. Your instructions might help programmers translate a website, but that will only help us with a handful of the 100+ languages OpenOffice supports. Would something like this work instead: 1) Have an ODF text document (or spreadhseet) that has a table listing the strings in the standard webpage template, English in one column, translations to go in another column. Poor man's Pootle. 2) Translators fill out the translations and submit them as a patch. 3) Volunteers then cut paste them into the actual mdtext files and check them in. Or it wold be simple enough to automate this using the ODF Toolkit. Make sense? We need to get to the point where knowing Albanian is sufficient to translate the Albanian page. Requiring someone to know Albanian, MDText and the Apache CMS is asking for a combination of skills that may not readily be available. -Rob Regards, Dave On Apr 7, 2012, at 1:55 PM, Dave Fisher wrote: Hi Andrea, On Apr 7, 2012, at 11:48 AM, Andrea Pescetti wrote: On 05/04/2012 Dave Fisher wrote: Here is what you would do to effect all of the FR site at once for translated branding and navigation buttons: Thanks for the detailed instructions, that should definitely be put on the wiki. I tried to apply them to the IT site: http://svn.apache.org/viewvc?view=revisionrevision=1310806 Everything seems OK, but I can't see the changes at http://ooo-site.staging.apache.org/it/ or http://www.openoffice.org/it/ I think that there was a hiccup with the CMS. Joe asked that you trigger your build again. I went ahead and added the files for French. I also made a change to a comment in ooo-site/trunk/lib/view.pm. This is a trick that will cause the staging build to do a full build causing all of the IT and FR sites to be changed to the new SSI. (1) Create trunk/templates/fr/ssi.mdtext from templates/ssi.mdtext ... Change /brand.mdtext to /fr/brand.html Change /topnav.mdtext to /fr/topnav.mdtext I did this, just replacing fr - it. (2) Copy /trunk/content/brand.mdtext from content/brand.mdtext Here I actually copied content/brand.mdtext to content/it/brand.mdtext (which is probably what you meant) and edited accordingly. (3) Copy /trunk/content/topnav.mdtext from content/topnav.mdtext Same as (2). Commit all three changes at once and the whole of the FR part of the site takes these changes at once. O(1) operation. I committed, the build was triggered and succeeded but I don't see the changes. The trick with lib/view.pm may be required. If you would like I'll create the mdtext files and then you can translate. This would probably be helpful to all native-lang projects, since even those not familiar with SVN could simply submit the translated version of their mdtext files. Yes, but I want to wait until we do a couple and make sure all the proper details are covered. We may be adding a news.mdtext and index.mdtext for the main index page, but that will be a separate thread of work. And it is not a reason to wait. I'll look into doing it for many NLs this
Re: update fails
Am 12.04.12 03:44, schrieb xia zhao: Hi William, Would you please try the r1309668 or the r1310206 build on: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots? I never use build 9567, This is a 3.3 Version, I can confirm, that the updater don't work there. update36.services.openoffice.org is dead. but for AOO 3.4, three latest dev builds ago, the package name is still dev package name and not the production name. And upgrade will install a new version on it. I have tried the above two build on my Mac lion and the upgrade work well. Best regards, Lily 2012/4/12 william kenneweg wkenne...@cablespeed.com Hi. Everytime I try to check for update it fails on my mac. 'm using build 9567. help.
Re: update fails
Raphael, Thanks for clarify, I understand it as upgrade manually. Yes, for OOo 3.3 version, the upgrade service is dead. Best regards, Lily 2012/4/12 Raphael Bircher rbirc...@apache.org Am 12.04.12 03:44, schrieb xia zhao: Hi William, Would you please try the r1309668 or the r1310206 build on: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots ? I never use build 9567, This is a 3.3 Version, I can confirm, that the updater don't work there. update36.services.openoffice.org is dead. but for AOO 3.4, three latest dev builds ago, the package name is still dev package name and not the production name. And upgrade will install a new version on it. I have tried the above two build on my Mac lion and the upgrade work well. Best regards, Lily 2012/4/12 william kenneweg wkenne...@cablespeed.com Hi. Everytime I try to check for update it fails on my mac. 'm using build 9567. help.
Re: [BUILD][RELEASE] Dictionaries on language packs
Ariel, On Windows build, it works same way. I understand it is design. Language package only providing translated help, resource strings but nothing with directory. You have to install dictionary separately. Maybe in further release, the language packages can come with dictionaries. Best regards, Lily 2012/4/12 Ariel Constenla-Haile arie...@apache.org Hi *, IIRC language packs came with dictionaries. That way you could install a generic en-US install set and then add language packs providing translated Help, resource strings, and dictionaries. Now the dictionaries are installed only on full localized install sets, but not in the language packs, at least on Linux (didn't try on Win). Is this as-designed or an issue with the Linux builds? Are language packs still supposed to install dictionaries? Regards -- Ariel Constenla-Haile La Plata, Argentina
Re: Bundled extensions
Josef, The bundled extension is easy to remove. After you install AOO, select Tools-Extension Manager. In the extension manager dialog, you can Disable or Remove the extension very easily. Best regards, Lily 2012/4/11 Josef Latt josef.l...@gmx.net Hi, Am 11.04.2012 12:17, schrieb Andre Fischer: On 11.04.2012 18:05, Josef Latt wrote: Hi, Am 11.04.2012 10:26, schrieb xia zhao: I would prefer that no extensions are bundled. Can you provide reasons for that ? As you can see below, there are IMHO some unnecessary extensions for a German user. I prefer installing only needed extensions. The problem comes up every time if you install a new version of OOo. In this package Apache_OpenOffice_incubating_**3.4.0_Linux_x86-64_install-**deb_de.tar these extensions are bundled: dict-de_DE-frami_2011-06-03.**oxt dict-de_AT-frami_2011-06-03.**oxt dict-de_CH-frami_2011-06-03.**oxt dict-en.oxt dict-it.oxt ooo-dictionnaire-fr-moderne-**v4.2.oxt presentation-minimizer.oxt presenter-screen.oxt They are in this package 'ooobasis3.4-core01_3.4.0-1_**amd64.deb' and will be automaticly installed when OOo is started the first time. IMHO not so good. Why? If you remain to bundle extensions it would be easier to prevent (with a separate package) that they will be installed. Regards Josef -- PGP Schlüssel: 311D1055 http://keyserver.pgp.com
Re: [ooo-site]
On Wed, 2012-04-11 at 22:50 -0400, drew wrote: On Thu, 2012-04-12 at 03:47 +0200, Raphael Bircher wrote: Am 12.04.12 03:40, schrieb Rob Weir: On Wed, Apr 11, 2012 at 9:33 PM, Dave Fisher dave2w...@comcast.net wrote: Rob, You are missing that Kay changed the subject and then had a back and forth with Marcus to solve this trouble. And the end result is that the page still says nothing about Apache, incubation or how to get involved with the project? I dunno about you, but I think we still have a problem. The Feed is from the http://www.oooforum.dk/ so it's not maintained by OOo. I think we have no danish people here atm who can make a update. I propose to delete this feed on the dk site to avoid confusion. The update from the site is a different storry. but this problem exist on the moast NLC pages Hi Raphael Well, I wouldn't necessarily go along with that idea. I'd say http://www.oooforum.dk/ is every bit as valid a community resource as the user services forums every were or are. They are acting at that forum in all material respects the same as the user services forums, the only difference being a somewhat more prominent LibO image (not an official one btw). So, does the sub-domain need upkeep - I guess, but I can see no reason to remove the feed from that forum. my opinion, Well, while your at it the same situation exists in Norway: http://www.openofficeorg.no/Forumsider/ Another long time OO.o forum, with historic links to/from the no.oo.o sub-domain (or did in the past at least) which supports both packages (or all ODF packages if you prefer) again as does the user services forum. In Germany things are different - there was two forums for a long time, now there are three (one specific to OO.o still, one specific to LibO and one that states it covers both, both really more LibO) There is also an ongoing discussion for example in the German OpenOffice.org Group at Xing (which is rather like linkeIN of Europe) about whether that group will rename itself to Apache OpenOffice or whether it should just go with LibreOffice (all though there is already a LibreOffice group) or should attempt to be for 'FOSS Office Suites' and attempt not to choose... anyway - it is the situation. //drew
Re: Bundled extensions
On 11.04.2012 21:27, Josef Latt wrote: Hi, Am 11.04.2012 12:17, schrieb Andre Fischer: On 11.04.2012 18:05, Josef Latt wrote: Hi, Am 11.04.2012 10:26, schrieb xia zhao: I would prefer that no extensions are bundled. Can you provide reasons for that ? As you can see below, there are IMHO some unnecessary extensions for a German user. Which ones and why? Do you want to drop any non-german dictionary, or any extension that is not de-DE? I prefer installing only needed extensions. The problem comes up every time if you install a new version of OOo. In this package Apache_OpenOffice_incubating_3.4.0_Linux_x86-64_install-deb_de.tar these extensions are bundled: dict-de_DE-frami_2011-06-03.oxt dict-de_AT-frami_2011-06-03.oxt dict-de_CH-frami_2011-06-03.oxt dict-en.oxt dict-it.oxt ooo-dictionnaire-fr-moderne-v4.2.oxt presentation-minimizer.oxt presenter-screen.oxt They are in this package 'ooobasis3.4-core01_3.4.0-1_amd64.deb' and will be automaticly installed when OOo is started the first time. IMHO not so good. Why? If you remain to bundle extensions it would be easier to prevent (with a separate package) that they will be installed. Would that really be the right place to make extensions optional? I am not so sure. -Andre
Re: Maybe stupid questions and summary of my comments (fwd)
Hannu, 2012/4/7 Hannu Puhakka ha...@vetokonsultit.fi Hi OpenOffice developers I joined this list a day ago. I am not familiar with your groups and not sure if I am on the right list at all. Maybe someone can comment. I am using oof OOO330m20 (Build: 9567). I have heard rumors that there are several OpenOffice projects - no idea what they might be and what to use - that my version is created by Oracle. You may try the AOO 3.4 new ones, which is on the way to publish. You can get it from: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots I am running a small software company in Finland and used normally MsOffice for presentations, sheets and documents. Because of HW crash I now started to manage by OpenOffice. Then I have got some problems and ideas to improve OpenOffice. I suppose I myself do not have resources for programming OpenOffice. Welcome the problems and ideas. It will help to improve AOO quality. I means Apache OpenOffice. Where should I send my comments? What you did is one good place. ooo-dev mail list. Another good place for problem and suggestion is BugZilla. https://issues.apache.org/ooo/ Where is the database to check if my comments have already been handled? BugZilla is the database to report bugs, including problem or some enhancements request. What version I should use to be useful with my comments? https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots r1310206http://people.apache.org/%7Earielch/packages/r1310206/linux_x86-64/Apache_OpenOffice_incubating_3.4.0_Linux_x86-64_install-deb_en-US.tar.gzis proposed AOO 3.4 RC build, you may use itfor your comments. How should I title my comments? Each comment with one bug. Some of my comments: 1) bug: / Impress: I insert a new slide. I click a text element and change the text size from default 32 to 22 (rigth click on the frame and choose Character size 22). If I move the mouse on the first text row to start writing, but do not write even a letter and THEN I select the frame, font size will be changed again 32 although the character size shows 22. I have to change the size to maybe 15 and back to 22 to be able to continue. You may modify the master page of impress if you plan modify the text size from 32 to 22 for whole slides. 2)improvement / Impress /Writer: Changing of picture size by mouse is very annoying. If you have inserted a picture from file into your presentation or document, you in 96 % of the cases need to modify the size - smaller or bigger. And 99% of those cases you expect that the picture should keep the original shape - it meens to Keep ratio!!! But now in Open Office when you resize the image, it never keeps the ratio - even if the Keep ratio checkbox is checked. I suppose this feature has been five years. If I do not work properly, still the feature should be changed because nobody cannot understand. See the attachments keep_ratio.jpg,resize.jpg. I don't have this kind of problem against AOO 3.4, maybe you can try again. 3) bug: / Impress: Text area. Many times when I try to insert a new line on my list pressing Enter, the application do not add a new line, instead tries to continue writing the same line and the letters appear at the same character at the end of the line. I can fix it by selection another text area and after that coming back. The problems appears many times a day, not for every text area. See the attachment open_office_text_area.jpg. Also I haven't this kind of problem against AOO 3.4, you can try and if you still have it, report it in BugZilla. 4) development proposal: Every open office program should have on the Help menu two selections: Send a bug report, Send a development proposal which should order a link where you could send your comments with automatic information of the version you used. Well, seems one good suggestion. Also post it in BugZilla as enhancement request. Regards Hannu --**--** -- Hannu Puhakka, +358 40 59 68 159, hannu.puha...@vetokonsultit.fi Vetokonsultit Oy,+358 9 2747 400, Kultasepänkatu 4 B, 04250 KERAVA,FINLAND --**--** --
