Your comments

I've asked Apple's developers at WWDC 2011 and they confirmed that it's not possible right now. I've filed a bug report though and hope that they add an API. But honestly I doubt that they will implement it.

I've seen another app that hijacks the alt-space character and enables a "command mode". So you would press alt-space and then s to save. I could imagine adding something like that in the future.
Can you send me an example CoffeeScript file so I can have a look at it and compare it to the symbol list in TextMate? I've fixed a bug in the symbol list in Textastic 3.2 so maybe this issue is fixed in that version.


Textastic uses the CoffeScript TextMate bundle from 

https://github.com/jashkenas/coffee-script-tmbundle - It's possible to customize the symbol list by editing the bundle and using that instead of the default bundle that comes with the app. Here's how to add your own custom syntax definitions: http://bit.ly/oUK9Kc


In general, if the symbol list in Textastic looks different than in TextMate then it's probably a bug in Textastic.

This is on my todo list.

The password is stored in the iOS keychain, so it is stored rather safely.
If you use a bluetooth keyboard, the virtual keyboard is already hidden. Do you want to hide the toolbar at the top, too?
I've forwarded your feedback regarding the feedback forum to the UserEcho guys. They're going to optimize the site for iPad.
Thanks for the update. I'll consider drawing characters like this differently.
Here's a UTF-8 character table: http://www.utf8-chartable.de/unicode-utf8-table.pl?names=-&utf8=0x


For example, the copyright sign © is encoded as 0xc2 0xa9.

I'm pretty sure it is because of UTF-8 encoding. UTF-8 adds 0xC2 bytes to encode certain characters. 

So you should try to add something like this to your html head section so that the preview knows that the file is utf-8-encoded:

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

You can also choose to save files with a different encoding, but it is really the recommended encoding for text files.
Hello,


did you choose the correct character encoding when opening the file on your computer? By default, files are saved with UTF-8 encoding.


Can you send me an example file to support@textasticapp.com?

I don't think this is actually possibly with current APIs in iOS, but I'll keep looking.