Community

It looks like I'm hitting the max folks, but just want to confirm. Using an old version of TextPad (4.7.3) because the newer ones can't handle/display certain ancient DOS characters (like the heart, club, etc.) we use in production, even using the Terminal font. I can create up to 64 macros and 64 t...

Please fix display of DOS encoding in Clip File and Find box. Even if we specify DOS encoding in our Clip files, the system is defaulting to ANSI encoding when displaying the characters in the Clip file window. It is also defaulting to ANSI encoding in the Find box. This is a feature that worked in ...

Thanks for fixing this. Please fix DOS encoding/display in Clip Files and the Find box. ANSI encoding is used even even if specified in Clip file as DOS. The last version where this worked is 4.6.3.

TP6 is converting null characters authored in TP4.5.3 with a HEX A0, which is a real problem for our current workflows.

We use DOS encoding/PC compatibility on most files for a legacy system. We also have various clip files and they use a CHARSET=DOS. In previous versions, the bell character (HEX 07) would display as a bullet everywhere. It still does in the main document window, but not in the clip file window, or t...

I have a simple stupid script that accepts a filename as a parameter and makes a copy of that file with a current timestamp. I actually have it setup in my Send To 'folder'. So, whenever I'm about to make a (potentially stupid) change in TextPad, I wander over to Explorer, (re) find my file, 'stamp...