favicon.ico
Wednesday, May 31st, 2006I’m tired of “favicon.ico” entries in error_logs of my sites, so I’ve decided to fix this problem.
I’m tired of “favicon.ico” entries in error_logs of my sites, so I’ve decided to fix this problem.
For important texts, I prefer to print them on paper and read in peace. The last time I did it was for the XTech 2006 slides. Unfortunately, I didn’t find how to print several slides on page in ooimpress, so I implemented a workaround:
The slides of my XTech 2006 presentation “XSieve: extending XSLT with the roots of XSLT” are online as PDF. The paper is available as HTML and PDF.
I got a positive feedback after presenting XSieve. But why I’m not blogged? I sure I mentioned something worth noting or discussing. For example:
* If we implement an XML transformation library in some traditional language, we get a poorly re-implemented XPath and XSLT.
* Buzzword candidate “gestalt entity”.
* S-expressions and XML are different, incompatible creatures.
* XML virtual machine as Scheme plus SXML.
Meanwhile, I’d like to say thanks to Eric van der Vlist. I borrowed a laptop from him for the presentation.
What I disliked most during XTech, it’s absence of printed proceedings. It’s a great fault. But probably I’m the only one who needs it.
I leave the home today and go to Amsterdam. The bad news is that I can’t take my notebook with me, so Developers Corner might miss TeXML. I hope I’ll be able to borrow a notebook at the place, but the probability of this solution is low.
Yet again, I’ve been affected by an xsltproc bug. If the result is empty, then the output file isn’t changed. As result, sometimes chained transformations continue with the wrong data. It is reported to libxslt bugzilla, but, unfortunately, it’s WONTFIX.
$ xmllint --noout http://googletalk.blogspot.com/atom.xml http://googletalk.blogspot.com/atom.xml:32: namespace error : Namespace prefix o on p is not defined <o:p/>We've been collecting suggestions ...
XTech conference starts 16 May, today is 9 May. Time to prepare. I’ve searched inet for “conference checklist” and, surprise, found near nothing. Anyway, I was able to compile something useful.
I think the specification is enough to convert Open Office documents, but the books also might be useful:
* OASIS OpenDocument Essentials
* OpenOffice.org XML Essentials
The most popular type of postings in xml-dev starts with “[ANNOUNCE] Hello Everyone, Stylus Studio has just…” And now I found them in my Russian-speaking (!) forum. Now I’m in doubt. Should I say kudos to their marketing department, or should I treat them as usual spammers?