R.E.D. = Retired, Extremely Dangerous
Category: Uncategorized
-
entering XML or literal HTML in the Blogger article editor is a PITA
At least the “<" you have to enter as "<", which makes it rather unreadable. If you forget this, and enter tags, as you want to see them displayed, they simply get removed. Bad and sad!
-
DocBook: article.info.date … – why does date not get displayed?
Good question, isn’t it? No, it’s not a good question, I assume. Using here is apparently just not the right way (I assume). Why?
I have used this combination for quite some time now.
I have no idea, whether I ever convinced myself, whether … gets displayed.
Just today I wondered, why it doesn’t get displayed.
I went through the pain of searching the DocBook XSL documentation, and XSL files, and … .This is the file, that actually showed me, how I should do it and that I should use … instead:
…/html/titlepage.templates.xml
Whatever it makes you feel like, if you look at this file (it really shows me, how little I understand of all this, so I feel desperate), it clearly lists the tags, that are taken into account for constructing the article info, and it doesn’t include but , so simply go and use in your DocBook article and stop crying!
I am really not sure, it was always like that, but that’s the way it is now.
So what do we learn from this lesson?
Editing a DocBook file in emacs’ nxml-mode does present you the entire list of syntactically acceptable tags. But that doesn’t mean all these tags are being made use of by the stylesheets.
So either you always construct your DocBook files from the nice samples in TDG, or you keep verifying your files against the template files like the one quoted above, or …
-
my XML catalog had a prefer=”public” attribute
How did it slip in there? I can’t really say. All I can say is, that it got included with an entry for Apples’s PropertyList DTD. But how did I know then, there is such an attribute with such a value?
I removed it now, actually I put it inside an XML comment together with some words explaining my confusion. In case this action now will break any processing in the future, I hope, I will find this blog article then. -
observing the procmail LOGFILE
I am a fervent user of procmail, have been such a user, since I found out, that sieve is far less available in any such mail environment as mine at my provider’s site.
I really don’t know of a lot of others, that also use procmail. I think, Axel uses procmail as well, I worked with Axel like almost 15 years ago at ERNO. I only found out, that “Sven G.” (a rather prominent open source person living in Berlin) also uses procmail, when we had a pasta evening together in my kitchen last Friday.
Observing procmail LOGFILE is my way of finding out about new e-mail messages, that try to reach me. I think, usually people have a look at their single mailbox (in case they are POP3 users) or at their 5 IMAP folders (just guessing that “5”). I have like 50 IMAP folders, and because I quite often toggle the “READ flag” of messages back to “unread”, observing procmail LOGFILE and also keeping separate track of important messages in my diary is my way of attempting not to lose track.
Now why did I start this article today? Sven G. is a “procmail LOGFILE observer“, too. And by “observer” I mean using “tail -f” on that logfile – IYKWIM. I just remembered that and Sven G., when I restarted that command line yet once again, and that raised a smile in my heart, that I enjoyed.
-
“Open Office” -> “Libre Office”
I decided to go for the OpenOffice fork “LibreOffice”. I just hope, the names behind that organisation really mean, this is a steady thing.
I did not want to go through this entire customisation process with LibreOffice on my Mac (and so forth) again, so I copied OpenOffice.org/3 to (a fresh) LibreOffice/3. I am of course not sure, this is a good thing, but it seems to save time.