[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: DOCBOOK-APPS: Character encoding problems in text files includedwith Saxon extensions
On Mon, Feb 19, 2001 at 12:05:57PM -0500, Norman Walsh wrote: > Yikes. Maybe it's time to promote the linespecific hack to a proper > text-include element. Or maybe it's time to support XInclude. Or > something. That "something" should ideally work together with requirement 2.5 in http://www.w3.org/TR/2001/WD-xslt20req-20010214 2.5 Should Include Unparsed Text from an External Resource Frequently stylesheets must import text from external resources. Today users have to resort to extension functions to accomplish this because XSLT 1.0 only provides the document() function which, while useful, can only read external resources that are well-formed XML documents. -- The idea is that the first face shown to people is one they can readily accept - a more traditional logo. The lunacy element is only revealed subsequently, via the LunaDude. [excerpted from the Lunatech Identity Manual]
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC