olpa, OSS developer

From “Poor Man’s Trackback“:

$ curl -d url=[my entry's URL] [trackback URL]

You can also specify the title, excerpt, and blog_name using additional -d parameters.

Seems interesting: plasTeX is a LaTeX document processing framework written entirely in Python. It currently comes bundled with an XHTML renderer (including multiple themes), as well as a way to simply dump the document to a generic form of XML. Other renderers can be added as well and are planned for future releases.

I’ll need it as soon as I start working on the DocBook stylesheets: Tennison Tests (XSLT Unit Testing).

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

LuaTeX is an extended version of pdfTeX using Lua as an embedded scripting language.

It seems that I like DokuWiki in advance. It supports utf8 and has nonparsed blocks and syntax highlighting for typesetting code. To be used for a next project.

Unicode Font Guide For Free/Libre Open Source Operating Systems

This paper describes a technique for implementing first-class continuations in languages that do not support stack inspection and manipulation. … This may result in better performance than CPS-conversion for those programs that make only occasional use of first-class continuations.

I’m sad I didn’t find the article “Incorporating Guile into your C program” before. It would save me a lot of time. Although the author annotates the article as “a old howto I wrote (very probably terribly out of date at this point as I gave up on Guile a long time ago)”, the article is still correct and very useful (especially in the GC part).

1 October 2005, update

The document is inaccessable today due to problems with the server. Instead, the document can be downloaded from Unofficial Guile Docbits.

My project is accepted for the Google Summer of Code project, and now it’s time to ask for money. From discussions: “Figuring out that damn tax thing appears to be the hardest part of the project.” The post with preliminary instructions.

A list of papers related to PreScheme and VLISP: http://www.coyotos.org/pipermail/bitc-dev/2004-October/000003.html. Should be useful for my future developments.

Unicode site is well-known. But sometimes it’s not enough. Here are some more links.

(more…)

And although not supporting the whole Scheme standard, the compiler supports fully optimized proper tail calls, continuations, and (of course) full closures. http://www.iro.umontreal.ca/~boucherd/mslug/meetings/20041020/minutes-en.html