Community

Hi, I'm using TextPad 8.1.2 64-bit on Windows 10 1809.

I create exports using phpMyAdmin of 3 identically configured MySql WordPress databases as UTF-8 .sql files.

2 of them open with TextPad correctly as UTF-8 (Unix)

1 opens as ANSI - Latin I with all manner of corrupted characters.

Notepad opens all 3 files without problems as UTF-8, and all chars are Ok.

This appears to be a bug with TextPad specifically; please look into it. Thanks.

This is a long standing issue with TextPad.

It happens because textpad tries to determine what the character encoding is when it opens a file. Whenever in doubt it uses ANSI, which is the default.

Adding a BOM to your UTF-8 files might help, but that might not be practical. For instance, PHP doesn't like BOM's.

What seems to help in my PHP file is when I add this line:
but I do not garantee this. Check this forum for more help.

I do not expect Helios Software Solutions to solve this problem any time soon. The basis of this editor works in ANSI. The maker is English and therefore problably never needs to use anything but ANSI characters. I think Textpad is just a side-project, kept alive because there are some people who like it. I like it too, but wished it was better supported.

This actually works, thanks.

This particular file had only a few Unicode chars, so adding 3 more made a difference.

Open in Notepad (or even Word, I guess, which asks to confirm encoding), add the line, save, open with TextPad.

dchernik wrote:Notepad opens all 3 files without problems as UTF-8, and all chars are Ok.

If the files have no BOM I think you're confusing Notepad with Notepad++.

Seems to be working for me - stopping me tearing my hair out!

How does that code do it?

Check each document setup in Document classes, including the Default class and you will find the document that saves as ANSI.