vslavik / poedit

Translations editor for Mac, Windows and Unix
https://poedit.net
MIT License
1.76k stars 274 forks source link

Poedit error when copying text #692

Open milotype opened 3 years ago

milotype commented 3 years ago

I've just updated my Poedit app to: Poedit 2.4.3 - OS X Verzija 10.11.6 (Izdanje 15G22010)~ -

I get the following error message. It happens when I try to copy some text from the source string as well as from the translated string.

error2

After that, when I paste the copied text into the search dialog, the text is longer then what I've selected (see screenshot below). I selected only the word "features", but the pasted string is longer ...!?

error3

vslavik commented 3 years ago

Can you please follow these instructions and provide steps to reproduce, i.e. the file and exact steps to take?

vslavik commented 3 years ago

I've just updated my Poedit app to:

Also, updated to 2.4.3 beta version from what previous version?

vslavik commented 3 years ago

I am able to partially reproduce this - copying from source text when the selected part is within syntax-highlighted portion of text (but that's not the case in your screenshot).

I'm still unable to reproduce the copying problem (could it be that you selected the longer text previously?), nor can I reproduce the exception when selecting non-highlighted source text...

milotype commented 3 years ago

I'm still unable to reproduce the copying problem (could it be that you selected the longer text previously?),

No. At least I don't think so ...

vslavik commented 3 years ago

Again, this high-level overview is insufficient. I tried doing this kind of guessed steps. I couldn't reproduce what you report. There are relevant details that matter and that are omitted above. That is why I asked for the file and precise reproduction steps (incl. what item to select, what exactly to select, how to select (shortcut, mouse, menu, all this could result in subtle differences) etc. I also really do need to know what is the last known-good version you used that did not exhibit this.

milotype commented 3 years ago

Again, this high-level overview is insufficient. I tried doing this kind of guessed steps. I couldn't reproduce what you report. There are relevant details that matter and that are omitted above. That is why I asked for the file and precise reproduction steps (incl. what item to select, what exactly to select, how to select (shortcut, mouse, menu, all this could result in subtle differences) etc. I also really do need to know what is the last known-good version you used that did not exhibit this.

vslavik commented 3 years ago

my last version was the one prior to my update

Do you think you're funny?

I'm closing this as not reproducible, then. Life's too short to deal with vague drive-by bug reports by uncooperative submitters.

The small subset that I could reproduce will be dealt with. Hopefully it will address the non-reproducible rest too. If not, the real fix will have to wait until somebody else provides reproduction instructions.

milotype commented 3 years ago

Pleeeease excuse my comment about my last version ... I completely forgot to specify it ... sorry. I was definitely not trying to be funny ...

I just updated to version 2.4.3 (6086). I don't experience the problem any more, so I think this issue is resolved :-))

P.S I had two Poedit versions installed. Some time ago, you suggested I could use two different copies of the Poedit app (becuase of testing beta releases). Maybe there was a problem with my "mixed" installations ...

I have now decided to only use "one" version of Poedit in my MacOS "Applications" folder ...

vslavik commented 3 years ago

I overreacted and should have known better; sorry.

I don't experience the problem any more, so I think this issue is resolved :-))

c8cbc834a3342efe62c5e19b7eb75151e851627d is definitely bad, then. Can't re-introduce it if it breaks things in scenarios I don't fully understand, so I'll have to figure out something else. Oh well.

Maybe there was a problem with my "mixed" installations ...

I don't think it could plausibly explain this. Would rather suspect language or perhaps keyboard differences.