Google Docs has added a bunch of new features. Two things which will stand-out among these features are AutoCorrect and Mobile edits. With AutoCorrect, you can type faster with fewer mistakes. Google Docs new documents editor supports editing on your mobile browser.
AutoCorrect
A feature to substitute text automatically. For example, if you type (c), the docs editor will replace it to ©. You can even add your own custom auto-corrects. To add custom auto-corrects, from your Google Docs editor go to Tools > Preferences. Add the word to be replaced in the ‘Replace’ field and the word to be used as replacement in the ‘With’ field. This feature is very much similar to what Microsoft Word offers except that there is no support for formatted replacement text yet. More details here.
LaTex in equations
Many LaTex shortcuts have been added to the equations editor. If you are familiar with the LaTex format, you will get to enjoy this feature. Check out the list of shortcuts added. Microsoft Word has good support for LaTex formatting with the help of plug-ins. More details here.
Mobile edits
Google Docs new documents editor supports editing documents on the go from your mobile browser. This is a much needed one and I no longer have to depend on any of the third party providers for this. This feature will be rolled in the next days to Android devices with Froyo (2.2) and iOS (3+). More details here.
-- Varun
Would you have any idea if this "mobile docs" offering would allow scripting in a spreadsheet accessed from a mobile (Droid X)?
ReplyDeleteThanks
Mike
PS: Authenticating with a Google account is a great idea but it needs a "redirect to a Google site for password entry" function. It appears that the Google API supports this but I don't see how to access it from your site.
Mike, scripts are not supported in the current version of mobile docs.
ReplyDeleteI don't get your question on the authentication part.
Thanks,
Varun
I was afraid mobile wouldn't handle scripts. Thanks anyway.
ReplyDeleteOn the authentication issue, if I enter my Google account password into a form on your site, I'd need to assume the password wasn't secret anymore. The way this is generally handled is to not request the password in your html but instead redirect to a secure Google authentication site. That site requests the password an returns a token that shows I'm who I claim to be.
If you take a look at the Interaction sequence section of http://code.google.com/apis/accounts/docs/OpenID.html, you'll see how Google wants it used.
In your case, it's possible that this mechanism should be provided by your host (i.e., blogger.com).