Test post, please ignore.
Created: 11th May 2014
This post is just to test of the formatting function of the postach.io parser.
I've been having a little trouble with line feeds not showing up. The postach.io team have been trying to help me overcome this problem. They've made some adjustments to the parser and we hope that everything is sorted out now.
Just so that everyone feels better about this, here is a picture of a cat:
I thought I'd better put some bullet points in, so:
- This has been one of many tests.
- I thank you for your patience.
- I don't know why you're reading this rubbish.
- These bullet points are all duds.
"I can't stress enough how important it is to test every part of the parser." - Brad Lemon, today.
There is no point in doing a partial test, so we'll just throw in a couple of curly ones to try to trick the formatting:
Some of the content on the blog is tricky for the parser to interpret. I'm fond of throwing in formatting changes, to make content stand out, and to break it up. It can be boring to read a whole, long piece of boring test. And there is no more boring a test than writing nonsense just to please an editor. I will admit the postach.io software is great, when it's all working correctly. It's much easier to drive than other blogs because I simply edit a document in Evernote, and tag it 'published'. Postach.io does all the indexing and presents it in a very nice format.
But wait, there's more (text).
This guy has too much time on his hands:
Thanks for putting up with this silly post. The parser is working fine. We can all get back to work now. Why are you still reading this? Gosh, that's desperate...