Apache OpenOffice (AOO) Bugzilla – Issue 122192
Some strings directing to Oracle
Last modified: 2013-07-02 12:30:44 UTC
Some en-US strings have informations directing to "Oracle". Are they: * dbumiscres.src#RID_STR_EXTENSION_NOT_PRESENT.string.text The report, "$file$", requires the extension Oracle Report Builder. * preload.src#RID_TP_WELCOME.FT_INFO.fixedtext.text Welcome to %PRODUCTNAME %PRODUCTVERSION OEM\n \n To start the %PRODUCTNAME %PRODUCTVERSION OEM, please enter your personal data in the dialog following the license text. Important information is contained in the readme files which are located in the %PRODUCTNAME product directory. Please read these files carefully. You can also find detailed information at the Oracle website \n \n http://www.oracle.com/us/products/applications/open-office. * docrecovery.src#RID_SVXPAGE_ERR_REP_WELCOME.FT_RECOV_DESCR.fixedtext.text This error report tool gathers information about how %PRODUCTNAME is working and sends it to Apache OpenOffice to help improve future versions.\n \n It's easy - just send the report without any further effort on your part by clicking 'Send' in the next dialog, or you can briefly describe how the error occurred and then click 'Send'. If you want to see the report, click the 'Show Report' button. No data will be sent if you click 'Do Not Send'.\n \n Customer Privacy\n The information gathered is limited to data concerning the state of %PRODUCTNAME %PRODUCTVERSION when the error occurred. Other information about passwords or document contents is not collected.\n \n The information will only be used to improve the quality of %PRODUCTNAME and will not be shared with third parties.\n For more information on Apache OpenOffice's privacy policy, visit\n www.oracle.com/html/services-privacy-policy.html I think that we need to change this URL/references. Bests, Claudio
I'm not sure they need to be fixed. #1: Reference to "Oracle Report Builder" is correct, it's the name of an extension still available on the Extensions site. #2: It seems to apply to what Oracle called "Oracle Open Office" (proprietary product) and it's probably never displayed. So the solution would be to remove it rather than modify it (but keeping it does no harm). #3: Similar situation: it refers to the crash reporting tool that we no longer enable in our builds.
#2: It seems to apply to what Oracle called "Oracle Open Office" (proprietary product) and it's probably never displayed. So the solution would be to remove it rather than modify it (but keeping it does no harm). Keeping it, can very well do harm...it can potentially be activated without us reflecting on it. If it is never displayed it should have been removed as part of the 4.0 cleanup, where obsolete strings was generally removed (at least that is what I was told). #3: Similar situation: it refers to the crash reporting tool that we no longer enable in our builds. But it can be enabled, so we should remove the tool from our source tree, or at least change the texts. I removed a lot of oracle references a couple of month ago, and left those that was called "active", based on a dev list discussion. rgds Jan I.
OK. As a conservative solution, I would suggest to: #1 dbumiscres.src#RID_STR_EXTENSION_NOT_PRESENT.string.text: Keep as it is. #2 preload.src#RID_TP_WELCOME.FT_INFO.fixedtext.text: Remove. #3 docrecovery.src#RID_SVXPAGE_ERR_REP_WELCOME.FT_RECOV_DESCR.fixedtext.text: Replace www.oracle.com/html/services-privacy-policy.html with http://www.openoffice.org (this can probably be done automatically in all translations too).
#2, #3. yes, it is a simple "sed" over all po files (we have them on translate-vm, and tomorrow on translate-vm2), but I do not know which files are "locked" because they are being offline edited (we really need a wiki page or something, so we can see who works on which files/languages). But anyhow when jsc gives green light I/he can do the sed. rgds jan I.
I changed the resource files I used the wrong issue number and the commits were logged to the wrong issue. Simply rerplace 122191 with 122192, the revision is ok: "jsc" committed SVN revision 1484668 into trunk: #122191# correct privacy link "jsc" committed SVN revision 1484675 into trunk: #122191# replace Oracle link with OpenOffice link, have to be checked if this...
The preload.src file is somewhat special because I don't know for sure where and how this is used. We have to check if this is used at all and can potentially remove it. But for now I have simply changed it to OpenOffice and the www.openoffice.org.
grant showstopper flag, fixed already