I'm glad to see that I'm not the only one wondering if I was right to try XSLT to generate HTML. I'll have to persuade my customer to go with a technology that:
1 Is far, far slower than JSP.
2 Necessites learning a new, quirky language.
3 Generates HTML with Hebrew characters as &entities, so that the HTML is unreadable.
If my customer tells me, "Trash it. We'll go with JSP.", I couldn't blame him.
Eli Lato
Regarding Eli's remark on using XSLT for nationalization, I believe there is a _simple_ way to generate XML documents from proprietary documents: build proprietary2XML converter in any programming language like C with printf(). Once we have XML, use standard XML techniques like XSLT and DOM to process it.
As for Hebrew and other non-English specifics, I don't think this has much to do with XSLT as such. That's about encodings and Unicode, see W3C guidelines.