Community

Sure it would be nice if Helios would rewrite the program to use UTF8 natively but in the meantime, it is still better for me than Notepad++. There are simpler solutions than using UTF8 natively, such as using UTF32 natively, as explained in the long-running thread . Notepad++ does all that and ...

Does this version FINALLY support Unicode?

vwamenel wrote:@ccollins and rdcpro: will configuring the default file format to UTF-8 solve your issue?

Well, have you tried it yourself? Did it magically make TextPad support Unicode?

Thanks for the heads up. I couldn't find what I was asking searching. So it's not truly unique savy. Bummer. TextPad doesn't support Unicode. We've been asking for it for years but Helios refuse to answer us. See http://forums.textpad.com/viewtopic.php?t=4777 http://forums.textpad.com/viewtopic.php ...

Please, Helios, for the love of all that is holy, get this done, and soon. Could you at least give us an indication of where you are at with it? Or at least a clue of why whenever we ask this you refuse to answer? I think it would be to the point to link to some past threads on the whole issue ...

Create a UTF-8 file that has no special characters (e.g. hello). Open it in TextPad. There are no warnings since there are no special characters. Modify the file (e.g. add world) in TP and save it. TextPad saves it as an ANSI file instead of a UTF-8 without a notification that it changed formats. I ...

guess wrote:how do i get textpad to use utf-8 or unicode?

You don't.

TextPad doesn't support Unicode. Many of us have campaigned, so far unsuccessfully, for Helios to get out of the dark ages.

Unicode yet again - when and how it should be approached

Unicode Conformance

Judging form the number of respondents to this poll, this must not be that important of an issue. I think it means that there are actually far more in the "It's too late - I've already given up on TextPad" category, who aren't active here because they're just not interested now. I don't suppose we ...

Nice try. Now tell us when we're going to have a TextPad that supports Unicode.

Incidentally, not even the bug I reported in October 2008 that adds insult to this injury has been fixed.

It would appear from my records that it was back in April 2008 that I wrote to Helios asking when this is going to happen. Needless to say, no answer came.

Thinking about it now, maybe the poll question should've been: When should Helios unbury its head from the sand?

I am very afraid that the 3-minute backup may have kicked in, wiping out a month's worth of work, not yet sold and paid for. The automatic backup shouldn't be replacing the original file under any circumstances. I want to plead with you to post a warning very conspicuously, until you have a Unicode ...

I would argue that the features the developers include or not in an application are critical to it's success or failure. True, but surely that's a matter of matching the features to what the users want, rather than what the developers want? The important caveat is that all users are not looking for ...

Given the skills displayed by Helios, I think it telling that built-in handling of Unihan has not been done already. I see no substantial basis for bringing the hammer down on Bellringer's Tomb here. Maybe a short FlashWar - fun - but as the owner of the rights, it is right that they can do ...

For those who haven't found it already, there's a recent thread on how to approach it, with a poll on when it should be done. Your contribution would be appreciated!

This has gone on far too long. And while it's hard to believe that they're still trying to think up a strategy for getting it in, here's my proposal.... Freeze all development of new features in TextPad apart from Unicode support. Bug fixes could still be allowed. Do some initial bug fixes: whereby ...