Your comments

One thing that would really help me: can you please send me one or two of those html files with many Japanese characters so I can test the performance with them? You can mail it to support@textasticapp.com

Thanks for the link to the ForMatKonaVe font. I've downloaded it and the readme says:

ライセンス
--------------------
この作品は、クリエイティブ・コモンズの帰属-同一条件許諾(Creative Commons Attribution-ShareAlike) 2.5ライセンスの下でライセンスされています。
この使用許諾条件を見るには、

http://creativecommons.org/licenses/by-sa/2.5/
http://creativecommons.org/licenses/by-sa/2.5/deed.ja

をチェックするか、クリエイティブ・コモンズに郵便にてお問い合わせください。
住所は:559 Nathan Abbott Way, Stanford, California 94305, USA です。
--------------------
これは元にした小夏フォントと同じライセンスです。


So, according to Google translate, the font is under the same creative commons license as Konatsu and I think I could use that.

I will try out if it works with Textastic and if it does, I will add it in an update.

Hello,

yes, sorry, this is a known problem: all characters that aren't in the monospaced fonts supported by Textastic, incur a performance hit. Basically, Textastic has to search for another font that can draw this character. Deja-Vu Sans Mono for example supports the following scripts according to http://dejavu-fonts.org/wiki/Main_Page:

The following scripts are supported:

  • Latin (including European and African alphabets, IPA, ...)
  • Greek (including polytonic)
  • Cyrillic
  • Armenian
  • Georgian

Following scripts aren't available in all the styles:

  • Hebrew
  • N'ko
  • Tifinagh
  • Lao
  • Canadian Aboriginal Syllabics
  • Ogham
  • Arabic

If you know of a monospaced font that also includes Japanese characters with a license that I can work with, this would solve the problem and I'd be happy to include it in an update of Textastic.

Currently, it's ok if you only use Japanese characters for a few code comments, but unfortunately it's not really suited for long texts with many Japanese characters.
Ah, I see. I'll consider it. The problem I see right now is how to fit this information in this small area, especially if a file is linked to more than one remote location.
I plan to do something like that for Textastic 3.0.

Apple seems to have the copyright for the Monaco and Menlo fonts and unfortunately, they are not included with iOS.

I asked Apple several months ago if I could use the fonts in Textastic, but after they referred me to their legal department I never got an answer.

Seems like I forgot to implement the "Verify SSL certificate" switch as it exists for FTPS connections. I'll add it in an update.

As a workaround, you can e-mail yourself the self-signed SSL certificate. Then retrieve it on your iPad and open the certificate file. iPad will ask if you want to install it. Check it to install SSL Certificate.

I've heard that you can also use the iPhone Configuration Utility to install certificates on devices. (http://support.apple.com/kb/DL851 (Mac) or http://support.apple.com/kb/DL926 (Windows)).
Hrmm, the file is only created if at least one byte is downloaded. So, yes, that probably means that you can't download empty files. I'll put it on my todo list.
Textastic already remembers when the remote file location when you upload or download files and displays this information in the File Information popover (section "Links to Remote Connections"). When you tap on the path, the full path is displayed in an alert.



Or are you referring to something else?