Joe K.>Last time I checked, the answer was "No, but if someone has time
to
rattle off an implementation of an
integer-to-traditional-Hebrew-representation
algorithm, we'd be glad to plug it in..."
Judah W.>Done...I put this together a little while back let me know if
there are any
problems.
I
The question was about referring to bundles of parameters when calling a
named template repeatedly.
You could do what you want if you used the node-set() extension function.
The problem comes when you attempt
where $globalSettings is a Result Tree Fragment, which cannot be used in a
path expre
Praveen Maruvekere writes:
>I have written a code to perform the comparison but it takes significant
amount of time.
>If you want to look at the code I can send it too.
I think you should send it along, especially if you can make a formal
Apache contribution out of it. Those of us interested in
>...Why did it select imported template B with a lower priority versus
imported template C?
If they were imported from different places, then their import precedence
differs. But it appears that you really want to switch over to
xsl:include, since you want to avoid the effects of import precede
Edward Knoll writes:
>The templates at issues are actually distributed across multiple files.
>A master XSL file references these templates using . If I
>change the to an , the prioritization works.
>...should I expect this behavior?
Yes, import precedence outweighs template priority. We have a
I vote +1
.David Marston
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+1
.David Marston
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
John G writes:
>...I have a variable definition as follows:
>
>Text Here
>
>When the variable is declared in a template, the variable value is
>exactly what I expected, $extTest = "Something Else";
>When the variable is defined in the global space, the value of extText
>is a copy of the l
Dmitry Hayes wrote:
>...I would like to
nominate her for committer status on the Xalan-C subproject.
+1
David Marston
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Henry Zongaro wrote:
>Over the past six months, Joanne Tong has contributed in various ways
>to the Xalan-Java, particularly by investigating bug reports,
>reviewing some patches, and by submitting patches for [many] bugs...
To which I would add that she is working on necessary expansions of
the
John Gentilin writes:
>I need a way to run a transformation, that contains extension elements,
>then after the transformation have the ability to re-execute,
>selectively some of the templates. i.e. the equivalent of a
>call-template where I supply the Source Node and the template name.
XSLT 2.0 s
Igor Hersht wrote:
>Maybe it could be good idea to have package
>(e.g. org.apache.xalan.common) where we could have such code
[for internationalization]
>as well as any code which is common for
>XSLT2.0, XPath 2.0, XQuery 1.0 and XPath 2.0 Functions and Operators.
Given that all the above specs tr
See conflictres19 and 20 for ns:* in match patterns.
.David Marston
The Working Draft can be found at
http://www.w3.org/TR/xslt-xquery-serialization/
and the Data Model (describing what is to be serialized) is at
http://www.w3.org/TR/xpath-datamodel/
Quoting from the Serialization document:
"Serialization can be regarded as involving four phases of processing,
car
>I'm about to start filing bugs against the [conformance test] suite,
>but there's no category for it.
I think the ideal global solution is for OASIS to run a Bugzilla for
this, since it would allow filing of bugs against all conformance tests,
including those not originated here. Over time, expec
Continuing the saga of the "xalan" namespace prefix, Peter Janker
writes:
>In the generated script the 'xalan' prefix is needed because of the
>nodeset extension, but in the generating script it is simply a string
>and will therefor not be replaced (as is with the 'xsl:vendor'
>problem in the ex
Peter Janker writes:
>I try to write an xslt-script that outputs an xslt-script
[His example shows xsl:namespace-alias being used for the "xsl"
elements.]
>...Furthermore xalan is always deleting its own namespace-prefix
>declaration (xmlns:xalan="http://xml.apache.org/xalan"; ) from the
>styl
>What is not clear in my mind is how is XQuery positioned against XSLT.
>There seems to be quite an overlap between them. Is XQuery supposed to
>replace XSLT in the future?
I think the two are expectecd to co-exist for the indefinite future.
XQuery is about extracting data without ornate restructu
Yuri de Wit writes (about XUpdate):
>This new language being defined is supposed to describe document updates
>as opposed to document transformations. The key thing here is the
>assumption that the source document is the same as the result document.
I think the W3C intends to address this under XQ
Scott Lamb asks:
>What's the preferred way to make regression tests? I noticed the
>xml-xalan/test/tests/bugzilla directory, but there haven't been any
>tests added there in 15 months. Is there a new system?
Typically, we prefer to write a "conformance" or "acceptance" test
that is small and foc
>I am currently using xalan 1.2.2. and I have problems with the
>writing of html meta tags
>My html file needs to be compliant to xhtml DTD
Aha!
When writing XHTML, its need to be XML-compliant takes precedence
over the HTML requirements. You should use method="xml" in your
xsl:output t
If you are on the "To" list of this email, please respond by
January 25!
The following bugs should now be fixed in the 2.2 release of
Xalan-Java. These are the ones that are best verified by the people
who originally reported the respective bugs. For each one, I show
the Bugzilla bug number, pers
Jeff N. writes:
>I was trying to generate:
>
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
> xmlns:xalan="http://xml.apache.org/xslt"; version="1.0">
>
>But the obvious:
>
>
> name="xmlns:xsl">http://www.w3.org/1999/XSL/Transform
[etc.]
>
>didn't work.
The designers
Rob Stanley writes:
>Can any guru-types out there tell me if it is possible to use the key
>function against nodes in a NodeSet generated by an extension function?
The trick is the relationship between the "match" node and the "use"
node. Since a NodeSet is just a collection of nodes with no str
Cory asks about
>If the var is set to 'abc xxx' it should return item1 only. If the var
>is set to 'abc xyz' it should find item1, item2, and item3. However,
>it doesn't find any, because its only matching on the first
>within an item. If I change the order of the elements it
>does work.
[A
>I am querying an XML file with the XPath Query
> /descendant::*
>It should return all elements but i get the error:
>Programmer's assertion in getNextStepPos: unknown step Type: -2
You didn't say which processor you were using. The above works fine
with the latest versions of XalanJ and XalanC
Kai Ojansu writes (excerpted):
>...is there going to be some kind
>of xalan:content-type attribute in future versions of Xalan?
>...In my point of view (hope I'm not lost), stylesheet's output rarely
>can have (I can't think of any) multiple content-types.
The XSL Working Group of the W3C is lik
Tim Keen (a.k.a. Keen Tim) writes:
>I have a need for it and therefore I'm going to do it, but being new to
>Java I don't expect it to be a brilliant piece of work. My job would
>certainly be easier if I could piggy-back off the work that somebody
>else has already done, even if it's only thought
>I looked at the XSL-LIST FAQ and archive, and found no discussion
>unqualified element in match (at least, a search for "unqualified"
>turned up nothing).
It probably doesn't use the term "unqualified" as that word is not
common in pure XSLT discussions. I'm sure that something is there
in the
Brian Atkins writes:
>I'm confused about how unqualified locals in an instance document
>should match against node tests.
This type of question belongs on xsl-list rather than here. It's the
inverse of a FAQ about unqualified names in match patterns.
>Here is a valid instance document:
>
>
>Hi men,
There are ladies here, too!
>I need do a xsl that sometimes calls a template and other times
>calls another one
This looks like a job for xsl:choose or, depending on how you know
when the "other times" occur, maybe it could naturally fall out of
apply-templates and matching.
.
>...this means that I can´t use a variable for de name [of the template in]
>a xsl:call-template directive?
That is correct. This question is a "generic XSLT" question that could
be answered by reading any of the XSLT books now in print.
.David Marston
Julio writes:
>...I get the following error message:
>Fatal Error at (file , line 1, char1747): Expected comment or
>processing instruction
>...
>I believe the problem comes from the XML, I use strange ascii [sic]
>characters like á é í ó ú ñ.
[Note: the above look correct in my email reader. YMM
Vikram asks:
>Like the Math transformations in XSLT, are there any ways in which
>strings can be manipulated?
This is a FAQ.
In some sense, the math/string/boolean/node-set functions aren't "in"
XSLT, except for a few in Chapter 12 of the XSLT spec. The rest of the
expression language is XPath.
Matt Robinson writes:
>The problem stylesheet is Chapter5\crossref1.xsl, which when run against
>the input terms.xml appears to go into an infinite loop. However, it
>works fine with Xalan 1 and Saxon.
>The problem seems to be centred around the following in the match for
> , specifically the la
It appears that Hanaa Barakatis trying to sneak some special characters
into the output.
>select="root/{{$idName;}}"
>...cause[s] this exception:
>Illegal decimal character reference.
As the parser goes through
}
the next character must be either another decimal digit or a semicolon.
Instead, i
>Dave, did you know this gold file namespace85.out checkin would fail?
>Everything else seems happy and passing.
>- Shane
Yes, I knew that. The problem has bug #3464 on it.
Do I have to add namespace85 to some list in some props file?
.David Marston
You want to say
and generate only text nodes.
.David Marston
>I am looking for non-presentation oriented usage scenarios for XSLT
One scenario that I often give in presentations involves a generic
business that does on-line purchasing. Among other things, they buy
their office supplies on-line, and they have internally adopted some
xml.org standard th
Tom Amiro wrote:
>But I kinda like "output" as the function/element name better than
>"redirect". XSLT users would find "output" easier to remember,
>since it already controls various aspects of the output from
>a transformation. Saxon also uses "output".
I think we should be careful to make ou
Paul ([EMAIL PROTECTED]) writes:
>...The user types in some numbers and clicks on a button, which adds
>more data to the source. The transformer is invoked again, but instead
>of regenerating the entire result, it determines which parts of the
>result are dependent on the changed source elements
Rahel Luethy writes:
>for one of the templates i use in the XSL, i'd like to read the XPath
>pattern that's used in the "match"-attribute from the command line...
>just to give you an idea (i know that it doesn't work like this..):
>
[where $myXPathPattern was passed in from the command line
>Is there any way to get an xsl:sort to work on a Date (a value such as
>'01/01/2001')...?
Try looking at the XSL FAQ at
http://www.dpawson.co.uk
for answers to "generic" XSLT questions.
Working from memory, I recall that the substring() function can be
used in the select attribute of xsl:sort,
Nuri Besen writes:
>I also use xsl:output tag with method="text" and the difference is that
>the 1.2.2 version produced raw data in the encoding whereas the 2.1.0
>produces "İ" still. Is this correct behaivour?
No. XSLT 16.3 says that if method="text" and the character cannot be
output as the by
Stephen Cranefield ([EMAIL PROTECTED]) writes:
>Does Xalan-Java apply keys to additional source documents loaded using
>the document() function?
and later, he wrote:
>I missed all of this [12.2 context-node stuff], but now that I have
>added the for-each to my code it works.
Could you please sh
Stephen Cranefield ([EMAIL PROTECTED]) writes:
>Does Xalan-Java apply keys to additional source documents loaded using
>the document() function?
>In an article at
>
http://www-106.ibm.com/developerworks/library/ws-trans/index.html?dwzone=ws
,
>Uche Ogbuji states that "every time an additional sou
>> is Stephane Bailliez
> is Gary Peskin
>>However what is supposed to be the behavior when a decimal-format does
>>not define all characters used in the pattern ? In this case it could
>>simply mean that we decided to go with the locale separators...
>Yes. I think that XalanJ should internall
Stephane Bailliez wrote:
>It looks like in xalan 1, it was able to cope w/ a different separator
>than the locale one when none was defined explicitely.
You forgot to tell us about your locale. Also, we need to know if you used
xsl:decimal-format to change any characters. The JRE in use might al
Mike Hostetler says he's getting a bad number from
We have quite a few tests for xsl:number, so I'm concerned that this was
able to slip through. Since count is a pattern, you should be able to say
count="chapter"
and get the same result. Mike: can you try that and report if it makes
any differ
Regarding the fact that is one of the elements subject to
special treatment when the output method is HTML:
>This is an interesting issue. The element is being produced
>by an extension function. So the output method of the extension
>function is "xml" but the output of the transformation is "
We already got this question from "Raj" - is that a colleague of yours?
(And several answers have been posted)
Raj writes:
>I checked examples that are given along with the product, I found that
>it takes a XML document and XSL both stored on the hard drive and
>transforms into HTML or FO and result can be attached to the servlet's
>response. In our case we can have only the XSL on the hard drive and
>DOM
>I would get the correct tree except that the node was only an
>open tag, there was no corresponding close tag. While trying to debug
>the problem, I changed the depth to make col at the same level as
>column-header and it was still broken, then I changed the name and it
>worked just fine.
>A gr
Here's another generic XSLT question which may be in the FAQ, but I'll
give a hint here:
Given
>If I have the 'C' Element, how do I get a list which contains the 'a'
>and 'b' namespace desclarations, which are in scope?
General idea:
;
Get that working, then alter it to suit your
Everett Stauffer asks:
>What is the exact format of the "numeric" data as text?
But the expression that started this thread is:
>
If you break down that expression as Xalan would, the top of the
expression is > (or > if you will), which says that a boolean
will result. According to XPath 3.4,
Fabrizio writes:
>...I need the CDATA Sections in the XML source document not to be
>processed by Xalan...
By the time Xalan gets the input, the parser will have removed the CDATA
characteristics. But I think your real question is about how to control
what gets output as CDATA, and you know how
Shruti writes:
>I am querying the following xml document using the xpath expression
>//my:book .
>It does not return anything
>
>xmlns:my="http://www.placeholder-name-here.com/schema/";>
> ...
Does the "my" prefix map to the same URI in the stylesheet?
For more help, try the XSL-list
Shane wrote:
>*All* Xalan-J 2.x code, documentation, builds, etc. is contained
>under xml-xalan/java.
I contend that there is documentation which should be considered
common between Xalan-J and Xalan-C (and Xalan-other, if someone
wants to do another language). The sensible place to put it is
xm
> quotes Shane:
>One admitted difficulty with xml-xalan is that the 1.x code was
>rooted at the top level, which makes it hard to separate from other
>bits of Xalan.
A great example of how poor planning hurts you down the road. I am
adamantly opposed to saying "Let's just do it; we can fix it l
>> is Erwin Bolwidt, > is Morten Jorgensen
>>* Change in XslAttribute; an xsl:attribute is allowed anywhere and adds
>> the attribute to the nearest containing result element. The check in
>> XslAttribute is not needed.
>I am not sure if I agree 100% here. Section 7.1.3 of the XSLT 1.0 spec
>st
This test case involves the "currency character" mentioned in the spec.
As I read the spec (12.3, first paragraph), this pattern should throw
an error, but nobody does. They just treat the character as they do
all other non-special characters, making part of the fixed prefix string.
Anyone want
Hergert writes:
>what is wrong if i tell Xalan as an Example instead of "foo.xml" using
"d:\xyz\hdghei\foo.xml" in this example foo.xml is there yes I am sure
^^^
I'll borrow the answer from the Xalan-Java FAQ:
Q: Why do I get 'file not found' when I pass c:\path\filename.txt?
A: Xalan often re
Benoit Aumars asks:
>Any suggestion where to find books, tutorials, tips, etc
>about Xalan-Java ?
There are no books specifically about Xalan, but a few about XSLT,
with more on the way.
First, check the "Getting up to speed" section of
http://xml.apache.org/xalan-j/overview.html
for leads on t
> The uncompression produces the directory structure intact, but
> ALL the files are of 0 bytes. I am using Winzip 6.2 32-bit.
This happens to me, too. Apparently, not all ZIP tools of the past
few years interoperate. I had to get PKzip.
.David Marston
Maruthi Rao asks:
>How can i append content to the existing content of an xml file using
>ReDirect extension of Xalan.
I gather that you want to splice more branches onto an existing tree.
That may be safer with file-manipulation tools. Right now, all that XSLT
(Xalan or other) offers is the pos
Alex Nikulshin writes:
>The Xalan mishandles the tag. The error
>message says:
>... Could not resolve namespace prefix: xml. ...
>I am a little surprised - since this is the reserved namespace and it
>should be ok without any declaration. Or am I missing something?
This has been reported in Bug
More comments on test cases:
> lines are from Shane's original message.
>node17 - change to output attrs instead of elements, so out-of-order
>compares possible
This was changed from plain text to elements, but I can change
it again.
>select69 - if possible (don't know if it'll affect test) ou
67 matches
Mail list logo
