No announcement yet.

Copy&Paste function worse since update // suggestion for improvement on C&P function

  • Filter
  • Time
  • Show
Clear All
new posts

  • Bug Copy&Paste function worse since update // suggestion for improvement on C&P function


    Since the update to 11.1 the copy&paste function from PDFs seems to work worse. In my work I c&p a lot from PDFs into other documents (into my note-taking program and a text editor). I am c&p'ing from the same document I read from yesterday, but Foxit Reader now seems to do a worse job in parsing the text. When I paste from that PDF, I suddenly get pasted hashtags instead of "Th", $ signs instead of "tt", or other wrong characters. I did not have this problem before the update.
    This is not a catastrophe, but annoying because it slows down my work. I would very much appreciate a fix.

    I would also like to make a suggestion for an improvement on the c&p function: currently, Foxit Reader c&p's the text from PDFs including the line breaks of that document. It would be a significant help to my work if that were not the case. (And I imagine that I am not alone here.) While Adobe Reader and Wondershare PDFelement do the same, Mac Preview and PDF Reader Pro do not do this. If I c&p with the latter two programs, I get the text without any line breaks. If you could change this or add an option that the user can select which c&p style they want, that would be great.

    Thanks in advance.
    Last edited by mthjzm; 11-04-2021, 12:01 AM.

  • #2
    Does the copy&paste issue happen for every pdf file? Would you mind sending us one file sample you mentioned so we can have further testing? You can create a ticket from Create ticket and upload the file, thank you.

    Thank you for your suggestion, I will report it to our product team for future evaluation, hope it will be considered in future release.


    • #3
      Thanks for your reply. I submitted a ticket.


      • #4
        May I have the ticket number please so I will take care of it, thank you.


        • #5
          Yes. The ticket number is: 143808
          fwiw: In the ticket, I stated to use Mac OS 11. I upgraded to Mac OS 12 in the meantime and now I can tell that the problem also occurs with Mac OS 12.


          • #6
            Thank you, I will take care of it and reply to you by email if there is any news about it.