Since starting this blog about a year ago, I am at a point where I think my choice of typical topics is more or less stable. I also have used the WordPress “categories” to add many of these topics and also hope to develop some of them into some sort of series. What these ‘series’ are for, is explained in the category descriptions now. The Ninja: A pseudonym Also, I wanted to quickly address another thing: My pseudonym. I have already talked about why I started this blog multiple times before. There is a basic mission statement in the about section. Long story short, the ‘LaTeX Ninja’ was a goal, not a label I put on myself. It doesn’t describe ultimate LaTeX wisdom (for that, I have sometimes used the term ‘LaTeX Guru’). If the LaTeX journey you can join on this blog were a computer game, you you start out as a ‘LaTeX Noob’. As you gain experience, you
Dear all, apparently the LaTeX Noob is not alone to be a noob 😉 I just realized I had to approve your comments before they are published. Oops 😉 Will see to that more quickly in the future. Also, I heard that some of you were not able to find contact information which maybe I might have messed up too 😉 I guess I just hadn’t really thought about having actual readers who want to contact me so far. And I am very happy that you exist and do wish to contact me! I will therefore add my contact info in the about section. Sorry, I am such a complete idiot not to have thought about this before 😉 Best and thanks again for all your positive feedback!
Dear all, just a little info that I am having trouble with the WordPress Markdown support. Which is actually not a correct statement because it really doesn’t work. So let’s say WordPress’s alleged-markdown-but-not-actually-supporting-markdown-thingy. Which has caused me hours of worry already. The code support works ok but not if written in MarkDown. I will do everything using keyboard shortcuts from now on so it will be ok in the future. However, I continue to find serious markdown problems in the old posts. I’m working hard to get rid of them. But some of them are really tricky and tedious, so this might take a while. Particularly horrible is the code support using XML. Because the editor will do some automatic whatever and ruin the XML, trying to make HTML out of it via auto-correct or something. I will not use that feature anymore to spare you and me the inconvenience. Until then, please bear with me until I have tidied