Your comments
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.
Hi, I've just recently discovered a bug that will be fixed in the next update.
Please try to limit the amount of concurrent connections to 1 (default is 3) in the FTP configuration screen. There's currently a bug that results in a crash when directory listings are parsed in several concurrent threads.
Customer support service by UserEcho
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.