From: Colin A. <col...@ho...> - 2007-09-30 07:42:45
|
I am in the process of making the XSLT serializer a separate component (alt= hough still dependent on the xslt library.xace) , so that other programs ca= n make use of the various serialization options offered by XSLT (see http:/= /www.w3.org/TR/xslt20/#element-output). Although this isn't quite finished yet, I am writing an example program ill= ustrating its usage (it will take an xml file name plus a series of command= -line arguments specifying serialization options). naturally I am using the= arguments library. Now the xsl:output attribute cdata-section-elements takes a list of qnames.= The natural way to specify this in the example program is: --cdata-section-elements=3D(qname1,qname2,qname3) I can do this with an AP_STRING_OPTION and parse the resulting string, but = it seems to me it is a reusable pattern and it looks worth creating a class= AP_STRING_OPTION_LIST. Do people agree? _________________________________________________________________ Celeb spotting =96 Play CelebMashup and win cool prizes https://www.celebmashup.com= |