That solved the timing issue.
The last few sentences seem to all get bunched up into one character. If you resize the text to a smaller size it clears it all up but then the text is too small.
The problem is that some text functions supported by the FxScript programming architecture (and those used by Boris too it would seem) are simply exposing calls to functions within the Carbon API (Application Programming Interface) which is limited to 32K processing ... and what that boils down to as far as we're concerned with Text Crawls is that the maximum width for any text string is 32K pixels. How many characters you can display therefore depends on the resolution of your sequence and the point size of the text. Bummer, but there you are. Its a hard limitation I'm afraid.
If it helps I have a free FxScript plug that you're welcome to use that offers fixed rate Text Crawls ie you set the speed you want it to crawl and away it goes ie its not dependent on the duration of the text generator in the timeline. If you're stringing a few crawls together to give the appearance of a single longer crawl then it would help to maintain a fixed crawl rate else the illusion of a single crawl will be broken.