EDIT: Nope. Didn't work. False alarm everybody. The day I'm able to send this email and it shows up in the browser as proper HTML, I'll click my heals. (Work for Posterous or use Posterous? See the post comments for more details...). I originally thought Textile had been implemented when the last Get Satisfaction post that said "Textile!" was submitted. This was my enthusiastic, evangelistic shout out for Posterous.
Finally, you can reliably format the resulting HTML markup from a plain text email by using a few simple syntax rules in your Posterous post.
All of this HTML was spit out using the plain-text markup illustrated at these links: "for paragraphs (Examples of paragraph formatting...)":http://redcloth.org/textile/writing-paragraph-text/ here "for layout (Examples of layout formatting like bullets and blockquotes...)":http://redcloth.org/textile/page-layout/ and here "for text modifiers (Examples of text modifiers like html link formatting...)":http://redcloth.org/textile/phrase-modifiers/.
This is better because:
* All too often I had to go edit a post to fix formatting after submitting it by email.
This is another merging stream of the binary me. It may at times collide or overlap with the real me.
About Me:
I love to travel, then return home. In projects, I dig the details, when they compliment the greater perspective. I adore good design and applaud inspired implementation. Simplicity is king; functionally and in form.
This is another merging stream of the binary me. It may at times collide or overlap with the real me.
About Me:
I love to travel, then return home. In projects, I dig the details, when they compliment the greater perspective. I adore good design and applaud inspired implementation. Simplicity is king; functionally and in form.
Business services recommended by SwBratcher:
Comments 4 Comments
Really, though, I would like more of a dialogue from the Posterous guys about why this isn't able to be implemented. It's clean, easy to use, very simple to add to an application, and would save more resources than it would consume.
Here is what you guys need to consider:
* Let us indicate in the subject whether to process with textile or not by starting the subject with an asterisk.
* Processing my post with textile prior to posting will use less server process than my current work flow.
My current workflow is as follows:
# submit post
# load post to check formatting
# if post html formatting is foul, continue, else done
# log in if not already
# click to edit post
# click to edit html of post
# save edited post html
# go to step 2
Please rescue us. I cannot be the only one wasting your resources like this when textile is such a simple implementation.
I was blinded by optimism. As a test I posted the sharing of this news.
When the test didn't work, I was bummed and updated the post with an edit and elaborated on the need for it in my comment. Sorry about continuing the false alarm. Let the guys over at Posterous know you would benefit and maybe we can get a bump in priority.