On Macs, Copy to Clipboard adds 1470 zero bytes at the end

Bug #933070 reported by Lenny P. Robert
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Excel2LaTeX
Invalid
Low
Unassigned

Bug Description

When you select the Copy to Clipboard option, 1470 bytes with value zero get added to the Latex code. In text editors that can display invisible characters these zero bytes show up invalid characters (in TextWrangler as inverted red questions marks, in SubEthaEdit as large red diamond). Pasting this into a .tex file and compiling it, one obtains an invalid character error. Deleting all text before the invalid characters and opening the file in Hex editor, one sees 1470 zeros.

The current workaround is to simply delete the last line of what one is pasting. I have tested that with three different text editors

This problem of Excel2Latex (on Macs) has existed for at least five if not ten years.

Revision history for this message
Kirill Müller (krlmlr) wrote :

Well, it's slightly more than one year since I have taken over the project, and I don't own a Mac. That said, I'm going to verify the problem as soon as I can get my hands on a Mac, but I'm not sure if I'll be able to find a solution for this other than disabling the button in Mac.

Have you tried the "Save to file" option, or the new "Stored tables" feature? Store your table definitions once (this includes a target file name), then convert all table definitions with just one click.

Revision history for this message
Kirill Müller (krlmlr) wrote :

This seems to be a problem in the DataObject used by the "copy to clipboard" function:

http://www.excelbanter.com/showthread.php?t=282307

http://www.textndata.com/forums/putinclipboard-method-errors-mac-24928.html

This means that we have to wait for Microsoft to fix this. In the meantime, please use "Save to file" or "stored tables".

Changed in excel2latex:
status: New → Invalid
importance: Undecided → Low
Revision history for this message
Naser Nikandish (n-nikandish) wrote :

This problem still exists and the suggested solution works just fine
https://bugs.launchpad.net/excel2latex/+bug/1071992

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.