GerixSoft

In the previous article I have shown how to convert JSON to XML using XSLT 2.0 capabilities.

The problem w/ implementing parsers in XSLT, is conversion from flat structure to tree structure. XSLT was simply NOT created for such kind of conversions. For example, JSON to XML transformation is using XML Pipeline of mode1, mode2, mode3 to build a tree structure from a sequence of tokens generated by regexp in mode0.

I am pleased to announce XSLT Lint -- a tool for performing static code analysis of XSLT.

Idea of the project is to unscramble poorly coded XSLT, and patch the code accurately, so changes can be viewed nicely displayed line-by-line in file comparison tool.

Canonical has a very ugly habit of removing from repositories applications that you use and love, but they think these are not "canonical".

For example:

In my previous article I have shown how to preprocess XSLT using custom SAX ContentHandler that transforms XSLT source code on-the-fly.

The reason SAX transformation was chosen instead of simpler XSLT transformation is because SAX transformations preserve line and column information: if you will make an error in a preprocessed XSLT, XSLT processor will report exact line and column position of the error; if XSLT preprocessing was implemented in XSLT, line and column information would be distorted.

v1.4 of Drupal OpenID Selector is released.

The main point of this release is integration with various Drupal modules implementing OAuth authentication to various services, such as:

The need to constantly write xsl: prefix, angle brackets, verbose instructions make XSLT syntax somewhat odd for a newbie. Though the fact that XSLT is also an XML is a big plus.

The question is, can XSLT syntax be refactored to resemble syntax of regular programming language, yet without losing compatibility w/ XML?

v1.3 of Drupal OpenID Selector is released and v1.2 of Javascript OpenID Selector is released.

v1.1 of Javascript OpenID Selector is released and so is v1.1 of Drupal OpenID Selector.

OpenID Selector module is now official on Drupal.org at http://drupal.org/project/openid_selector

It is very often when you enable OpenID module in Drupal and try to login with OpenID, you receive Page not found, whilst everything works quite fine at localhost.

Next version of Ubuntu will include a new font, named "Ubuntu font", that will be used as default user interface font:

If you'll upgrade to Delphi 2010, you'll quickly notice that old code you were using to create threads, such as

XSLT 2.0 is powerful enough to process even non-XML input. For example, I have created a transformation that converts JSON text to well structured XML output:

Drupal's OpenID module is somewhat not complete.

If you enable OpenID module in Drupal, it modifies user/login screen with "Log in using OpenID" link:

I am astonished of FOR XML feature in MSSQL. Oracle, despite claiming they had XML support first, has nothing like that; and XML support in PgSQL and MySQL is just ridiculuos: