Sublime Forum

Difficulties converting from cp 1252 to cp 437 in ST3

#1

When I attempt to resave a previously win1252 character encoded file into cp 437 encoding, I’m seeing this dreaded dialog.http://i.imgur.com/lvBzwag.png

So I remove all lines, but a handful, checking if this still happens and at removal of one line, the file is properly saved. However, there is nothing strange on this line. Bringing it back and attempting save, again renders the same message.

However, keeping this line that previously when removed made a proper save possible and removing one other line that previously had no issues to be saved in cp 437 encoding, will still save properly.

Clearly this is not about the characters not being able to be represented in cp 437 encoding and this behavior must be considered a bug.

Thoughts?

0 Likes
#2

So I went all down just having “7” on one line. Still this dialog. Replacing it by typing in a “7” somehow makes the document savable into cp 437 encoding.

The original character strings have been pasted from another document that likely was in win 1252 format. Why would a paste from this format render an issue when saving to cp 437 given that the ST document already successfully has been saved in win 1252 encoding? Once saved isn’t the document then ensured to be in win 1252? Can there somehow be local characters in utf-8 in a win 1252 document that Sublime Text 3 has created? This is quite baffling.

I’m of course not sure where the bug is exactly. Could it be OS X interplay? If so, how could I route around this issue?

0 Likes
#3

After having analyzed the files in hexadecimal it seems some odd characters are coming form the originating openOffice file. These are not visible in Sublime Text even as I show hidden characters.

If this is indeed is a bug it would seem the issue is with OS X or OpenOffice. It would be wonderful if SublimeText could say which characters are involved of course.

0 Likes