I'm working on an update that is going to fix this issue.

It looks like you are looking for help with Apple's Pages app. This feedback forum is for the app Textastic.

Please use Apple's support resources to ask for help with Pages: http://www.apple.com/support/ios/pages/

Thanks for the info. I didn't have this problem on my machine yet. Textastic uses the standard Cocoa mechanism (NSUserDefaults) to save its preferences.

The preference file is located at ~/Library/Containers/com.textasticapp.textastic-mac/Data/Library/Preferences/com.textasticapp.textastic-mac.plist

Please let me know if you find a way to reproduce the issue.

No, since this only works for syntax definitions and not for editor plugins.

Hello,

Textastic uses iOS's UIWebView which is the same WebKit engine as used by Safari on iPad. 

There are some differences in mobile browsers when compared to desktop browsers. For example, ":hover" doesn't make much sense on touch devices, because there is no cursor that could hover over an element. The browser doesn't know the location of the user's finger before he actually taps.

You can add custom syntax definitions to Textastic by using TextMate bundles. See

Thanks for bringing this to my attention.

I have an idea why this might happen and will try to fix it in an update.

Hrmm, actually Textastic does use the standard mechanisms for text entry on Mac OS X. It doesn't set any custom keyboard bindings for cursor movements but implements the standard text entry interfaces.

In this case, Textastic implements the methods "moveWordBackward:" and "moveWordForward:" which are called by the operating system automatically when the appropriate keyboard shortcut is pressed.

(The standard key binding for moving forward or backward a word is alt-arrows.)

Ok, scratch that... use "\\$". The "\\" is necessary because you need to escape the backslash for JSON.