i did not say it was a hardware issue, and i did not mean to imply that. it is apparently a software issue, and apple did not design the ios to handle rich text well. for example, safari seems to be missing some component that would have enabled developers to create something browser based to work around ios problems.
The most precise thing to say is that it's an API issue. The OS X codebase has an API for rich text that is not yet available in iOS.
Pages on the iPad does the equivalent of rich text -- inside of the app. A developer with a large amount of resources could do the same thing. A small development shop with a code base using the RTF API on the Mac would wait for iOS to have that API before porting their app.
I have no inside information on if or when RTF will be available, but it makes common sense that the iOS APIs will continue to get richer over time (to coin a phrase).
anyhow, as i said, writing with minimal markup seems to solve most of my formatting needs, it takes up less memory, and the final product is widely supported.
Palpatine's manual mechanism of doing markup is called
MultiMarkdown. MMD is based on the
Markdown syntax originally created by John Gruber. For those wishing to enter text an iPad for a larger project, it's an excellent way to add basic formatting as you go.
Palpatine also mentioned
Scrivener, which is a highly-regarded Mac application for gathering research for a project and writing papers. Scrivener works with MMD. It has a stellar reputation
in the MAS, but the developer recommends you download the 30-day trial on the website to try it out. The developer does most of the support through his own forums, which is an excellent way to learn about his philosophy and the product.
It is exactly the design and hardware of the iPad that make it VERY INCONVENIENT TO USE as a device to produce/write large masses of text, and the main reason is that it is (just) a tablet or just a screen, without a physical keyboard, which you are absolutely dependent on to make a longer text. Of course, you may have an external physical keyboard, but that is NOT the point here, because that makes it necessary to carry around TWO units, a screen (called iPad) AND a keyboard.
If you stick your head into college lecture halls, you'll see quite a few iPads with keyboards using one of the integrated holders (making everything one piece). At the same time, the iPad's built-in keyboard is more than sufficient for capturing a short idea or reference at the library.
I think Palpatine's approach of using an iPad as a satellite while regularly migrating the data to a Mac very smart. He's clearly taken a lot of time to research a workflow that works for him.
Palpatine: if you have a web-presence or blog somewhere, you might want to make a post showing your workflow. You could start a blog on blogger and just make one entry showing what you've got. It's difficult for people just starting out to visualize your solution from incomplete information. Once you did that, you could just put a link to it in any article discussing this topic.
Thank you for doing the research then discussing the workflow that you use on your iPad and Mac. It takes work to figure these things out and it takes time to share them with the community.