This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: xsl string comparison fails why?
- From: Jeni Tennison <jeni at jenitennison dot com>
- To: "Passin, Tom" <tpassin at mitretek dot org>
- Cc: xsl-list at lists dot mulberrytech dot com
- Date: Wed, 25 Sep 2002 18:20:41 +0100
- Subject: Re: [xsl] xsl string comparison fails why?
- Organization: Jeni Tennison Consulting Ltd
- References: <5D3C2276FD64424297729EB733ED1F76B3C517@email1.mitretek.org>
- Reply-to: xsl-list at lists dot mulberrytech dot com
Hi Tom,
> [ Yates, Danny]
>> For the first state (Alabama), "admissions/state/text()"
>> evaluates to something like:
>>
>> Alabama<cr><space><space><cr><space><space>
>>
>> Which is NOT the same as:
>>
>> Alabama
>>
>> You can solve this either by using normalize-space() or by
>> changing your <state> elements so that they don't use a mixed
>> content model (i.e. containing both text and other elements). e.g.:
>
> Actually, even nomalize-space() does not quite do it because it
> collapses all the whitespace down to one space, resulting in
>
> Alabama<space>
normalize-space() strips leading and trailing space, so if the string
was:
"Alabama<cr><space><space><cr><space><space>"
then all that trailing space would be stripped and you'd get:
"Alabama"
It's only spaces in the *middle* of the string that get collapsed down
to a single string. So for example:
"New<cr><space><space><cr><space><space>York"
would become:
"New York"
Cheers,
Jeni
---
Jeni Tennison
http://www.jenitennison.com/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list