Phrasing issue in Open Office

Bug #484014 reported by Isaac B
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Fix Released
Low
Unassigned
libreoffice (Ubuntu)
Fix Released
Low
Unassigned
openoffice.org (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: openoffice.org

Ubuntu 9.10
openoffice.org 1:3.1.1-5ubuntu1

When exporting as a PDF and overwriting an existing file, the question regarding "overwrite existing file?" in contained in quote marks.

This look kind of weird.

ProblemType: Bug
Architecture: i386
Date: Mon Nov 16 22:58:33 2009
DistroRelease: Ubuntu 9.10
Package: openoffice.org-core 1:3.1.1-5ubuntu1 [modified: var/lib/openoffice/basis3.1/program/services.rdb]
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: openoffice.org
Uname: Linux 2.6.31-14-generic i686

Revision history for this message
Isaac B (isaac-twopinesstudio) wrote :
Revision history for this message
Steve McGrath (smcgrath23) wrote :

I can confirm this after testing on my system. The dialog text is indeed displayed in quotes.

Changed in openoffice.org (Ubuntu):
status: New → Confirmed
Chris Cheney (ccheney)
tags: added: karmic
Revision history for this message
Robert Roth (evfool) wrote :

Bug #525670 should also be fixed at the same time.

Changed in hundredpapercuts:
status: New → Confirmed
Revision history for this message
Chris Wilson (notgary-deactivatedaccount) wrote :

Since OpenOffice is going to be replaced with LibreOffice in 11.04, this no longer counts as a paper cut. Can someone please confirm whether or not this bug is still present in the latest version of LibreOffice?

Changed in hundredpapercuts:
status: Confirmed → Incomplete
Revision history for this message
Jack Leigh (leighman) wrote :

I can still reproduce in Libreoffice 3.3

Changed in libreoffice (Ubuntu):
status: New → Confirmed
Changed in openoffice.org (Ubuntu):
status: Confirmed → Invalid
Changed in hundredpapercuts:
status: Incomplete → Triaged
importance: Undecided → Low
Revision history for this message
xapantu (xapantu) wrote :

It doesn't happen in LO git.

Revision history for this message
Chris Wilson (notgary-deactivatedaccount) wrote :

xapantu, do you mean it's fixed in the upstream source?

Revision history for this message
xapantu (xapantu) wrote : Re: [Bug 484014] Re: Phrasing issue in Open Office

Yes, or, at least, in git, it seems to be fixed, excepted if we don't
speak about the same thing :)

Le lundi 31 janvier 2011 à 21:45 +0000, Chris Wilson a écrit :
> xapantu, do you mean it's fixed in the upstream source?
>

Revision history for this message
Chris Wilson (notgary-deactivatedaccount) wrote :

I've had a cursory glance at the source code at "git://anongit.freedesktop.org/libreoffice/bootstrap" and am unable to find the string quoted in the OP's description. xapantu, can you please specify in which file the corrected line appears?

Revision history for this message
xapantu (xapantu) wrote :

It appears in several files:
dbaccess/source/ui/dlg/CollectionView.src: Text [ en-US ] = "The file already exists. Overwrite?" ;
cui/source/dialogs/hyperdlg.src: Text [ en-US ] = "The file already exists. Overwrite?" ;
fpicker/source/office/iodlg.src: Text [ en-US ] = "The file already exists. Overwrite?" ;
svx/source/form/fmstring.src: Text [ en-US ] = "The file already exists. Overwrite?" ;

I don't know which one is used for the PDFs, but it has been fixed :)

Revision history for this message
xapantu (xapantu) wrote :

Hum, mea culpa, it seems that it isn't fixed in LO wich is in the repositories.

Revision history for this message
Chris Wilson (notgary-deactivatedaccount) wrote :

LO in the repositories will eventually reflect the LO source, how long that takes remains to be seem. Nevertheless, since this isn't an issue upstream, so eventually it won;t be an issue for us, I'm closing this bug report.

Changed in hundredpapercuts:
status: Triaged → Invalid
Changed in libreoffice:
status: New → Invalid
Changed in libreoffice (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Vish (vish) wrote :

Not invalid, that would be fix committed.

We need to make sure it is fixed and that we do indeed pull the latest LibO

Changed in hundredpapercuts:
status: Invalid → Fix Committed
Changed in libreoffice:
status: Invalid → Fix Released
Changed in libreoffice (Ubuntu):
importance: Undecided → Low
status: Invalid → Fix Committed
Revision history for this message
Chris Wilson (notgary-deactivatedaccount) wrote :

Isn't it only fix committed if a fix was worked on in response to a bug report? If it was fixed independently of the filing of a report, wouldn't that make the report unnecessary, thus invalid?

Revision history for this message
Vish (vish) wrote :

Nope.. :)
This bug was filed on 2009-11-17, and is still present in the Ubuntu package, ie. bug is still valid in Ubuntu.
But the bug has been fixed upstream, hence we mark it as 'fix committed'. In this case it means "fix committed in upstream branch"
[Usually for desktop packages, we mark the bug 'fix committed' once it is fixed upstream. This is how the desktop team prefers, since they usually check regularly (mostly weekly?), for such fix committed bugs and pull the fixes from upstream. Makes it easier for them. But other universe packages 'fix committed' means fix has been committed in the Ubuntu release-updates/release-security repo, or some repo meant for Ubuntu. So you might wanna watch out for those universe package's status.]

Even, if it was fixed in the Ubuntu package, we can just mark such bugs as 'fix released'. :-)

Revision history for this message
Chris Wilson (notgary-deactivatedaccount) wrote :

Ah OK, thanks for the confirmation :)

Revision history for this message
Timothy Arceri (t-fridey) wrote :

Marking as fix released as fixed in LibreOffice 3.4 (Ubuntu Oneiric)

Changed in libreoffice (Ubuntu):
status: Fix Committed → Fix Released
Changed in hundredpapercuts:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.