split string based on Character count

ptn77 · August 21st, 2010, 10:04 PM

Quote:

Originally Posted by samjudson

If there is I shouldn't think it would be one that would affect you - i.e. it would be something like Maximum Integer (2,147,483,647 in 32 bit architecture).

When people ask questions like this however I always worry. Are you saying you have found a value that doesn't work? Are you saying you have written the whole XSLT template but don't have 2 minutes to try it out yourself? Or are you just being curious for the sake of it?

Well I have a string that can contain over 50,000 characters. I did create the xslt template and tried it out. Using smaller integers work great but I think I tried to use 100 or something and that's when it no longer worked. :(

It didn't error or anything just left the string as is without splitting it.

samjudson · August 22nd, 2010, 01:06 PM

You're right, I've tried it myself and it doesn't appear to match for large values of n.

I can't find any reference to a limit in the spec, so it will likely depend on the some functionality within the processor implementation perhaps, which will likely be different for each implementation.

ptn77 · September 1st, 2010, 11:09 AM

When I got rid of new line characters in my string within the CDATA section, I noticed that the analyze string finds matches for values that are larger than 100.
Is it because the analyze string finds matches on consecutive characters not including new line? So, if you use a value larger than the largest line length in your file you'll see no change?
Is it possible to parse the entire contents of a CDATA as a single string even with new line characters?
Any help is appreciated.
thanks,

Martin Honnen · September 1st, 2010, 11:17 AM

Put
flags="s"
on your xsl: analyze-string element to ensure that "." matches any character, including a linefeed.

ptn77 · September 1st, 2010, 12:03 PM

That worked! thanks so much!