Dear Leo H,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/915059

Title:
  [Upstream] Compare Document highlighting unchanged words as changed

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 11.10
  Release:      11.10

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.4.4-0ubuntu1
    Candidate: 1:3.4.4-0ubuntu1
    Version table:
   *** 1:3.4.4-0ubuntu1 0
          500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 
Packages
          100 /var/lib/dpkg/status
       1:3.4.3-3ubuntu2 0
          500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages

  3) What is expected to happen in LibreOffice Writer via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915059/+attachment/2671476/+files/versions.zip
  && file-roller -h versions.zip && cd versions && lowriter -nologo
  version1.odt

  Edit -> Compare Document -> version2.odt -> Insert button

  is under Actions regarding the first Deletion top to bottom, one tan
  hyphen is shown to the left of "LibreOffice Writer" and "LibreOffice
  Writer" is not marked tan with a tan underline. An example of how it
  should look may be found via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915059/+attachment/2671477/+files
  /versions-space.zip && file-roller -h versions-space.zip && cd
  versions-space && lowriter -nologo version1-space.odt

  Edit -> Compare Document -> version2-space.odt -> Insert button

  4) What happens instead is the hyphen to the left of "LibreOffice
  Writer" is not shown and "LibreOffice Writer" is marked tan with a tan
  underline.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/915059/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to