Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#5515 closed defect (fixed)

Copying and pasting text puts a BOM at the beginning

Reported by: ari Owned by:
Milestone: 2.5.0 Component: pidgin (gtk)
Version: 2.4.1 Keywords:


From Debian bug report

Copying text from pidgin (either from the text input pane or the received message pane) and pasting it back into the text input pane results in a UTF-8 BOM character added to the beginning. In addition to putting garbage into sent messages if not noticed, this also prevents interpretation of slash commands such as /msg. You can tell if a BOM is present with any of the following:

  1. By cursor movement: hit home to go to the beginning of the line, then note that pressing the right arrow key once does not seem to move the cursor past the first visible character, but pressing right a second time does.
  2. By attempting a command starting with slash (such as /me or /msg), but doing select-all, cut, nd paste before sending it; the text of the command will go out as a message without getting interpreted, and with the additional BOM at the beginning.
  3. By checking the log file in ~/.purple/logs/ after sending a message, which will have the BOM in it.

Change History (2)

comment:1 Changed 11 years ago by sadrul

  • Milestone set to 2.5.0
  • Resolution set to fixed
  • Status changed from new to closed

Fixed with revision da43d671 for next release.

comment:2 Changed 11 years ago by sadrul@…

(In 000a0fa4bca9f18691f0a61e01bbac1aa76437c1):
* Plucked rev da43d671 (sadrul@…): Do not prepend the BOM when converting from UTF-8 to UTF-16, since g_convert seems to do that for us. Closes #5915. Fixes #5515.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!