Bug 53506

Summary: Page FORMATTING modified after copy/paste of contents from other document
Product: LibreOffice Reporter: jlader
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: jlader, LibreOffice
Priority: medium    
Version: 3.6.0.4 release   
Hardware: Other   
OS: Windows (All)   
Whiteboard: BSA
Crash report or crash signature: Regression By:
Attachments: screen shots of what happens
Sample Document

Description jlader 2012-08-14 20:45:13 UTC
Created attachment 65567 [details]
screen shots of  what happens

Problem description: If I copy text from an outside source, ai a .pdf file,not created by LO and paste it into writer, the page margins are changed to 1.25"/1.25"/1.00"/1.00".  For example, if the document has margins set to .5/.5/.5/.5", you copy text from an outside source source and then paste into the LO document, the margins are reset as described.  This has been the case for all 3.5 releases & now 3.6.  It also happens on every Win 7 64-bit system I try it on.

Steps to reproduce:
1. ....Copy text from a .pdf on other text source not created by LO
2. ....open a writer document whose margins are not 1.25/1.25/1.00/1.00"
3. ....right click and select paste to paste text

Current behavior:Page margins are re-sized

Expected behavior:margins should remain the same with all text formatting left in tact

Platform (if different from the browser): Win 7 6-bit
              
Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20100101 Firefox/14.0.1
Comment 1 Rainer Bielefeld Retired 2012-10-01 04:28:35 UTC
NOT  reproducible with Server Installation of "LibreOffice 3.6.2.2 rc  German UI/ German Locale [Build-ID:  da8c1e6] on German WIN7 Home Premium (64bit) 

I opened attached Sample document and added at the end by copy paste some contents from this page (in Seamonkey 12 Browser):

a) comment input Heading "Additional Comments:"
b) 3 Paragraphs of report, "Problem description: ..... are re-sized"
c) this complete page (before I started my comment) selected with <control+a>

Addtionally from a PDF created by printing Bug 53509 from Browser by FreePDF:
d) "Show dependency ..... Additional Comments:"
e) complete PDF documet's content  selected with <control+a>

@reporter:
Thank you for your report – unfortunately important information is missing.
May be hints on <http://wiki.documentfoundation.org/BugReport> will help you to find out what information will be useful to reproduce your problem? If you believe that that  is really sophisticated please as for Help on a user mailing list
Please:
- Write a meaningful Summary describing exactly what the problem is
- Attach a sample document (not only screenshot) or refer to an existing 
  sample document in an other Bug with a link; to attach a file to this 
  bug report, just click on "Add an attachment" right on this page.
- detailed info what contents from what source you copied
- Contribute a document related step by step instruction containing every 
  key press and every mouse click how to reproduce your problem 
  (similar to example in Bug 43431)
– if possible contribute an instruction how to create a sample document 
  from the scratch
- add information 
  -- what EXACTLY is unexpected
  -- and WHY do you believe it's unexpected (cite Help or Documentation!)
  -- concerning your PC (video card, ...)
  -- concerning your OS (Version, Distribution, Language)
  -- concerning your LibO version (with Build ID if it's not a public release)
     and localization (UI language, Locale setting)
  –- Libo settings that might be related to your problems 
    (video hardware acceleration ...)
  -- how you launch LibO and how you opened the sample document
  –- Whether your problem persists when you renamed your user profile 
     before you launch LibO (please see
     <https://wiki.documentfoundation.org/UserProfile#User_profile_location>)
  –- If you can contribute an AOOo Issue that might be useful
  -- everything else crossing your mind after you read linked texts
Comment 2 Rainer Bielefeld Retired 2012-10-01 04:29:14 UTC
Created attachment 67909 [details]
Sample Document

See comment before how to use!
Comment 3 jlader 2012-10-08 14:25:04 UTC
LibreOffice 3.6.2 under Windows 7 64-bit.  Same results
Comment 4 QA Administrators 2013-05-29 23:04:53 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


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


Warm Regards,
QA Team
Comment 5 QA Administrators 2013-07-08 21:20:50 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO