On Nov 3, 10:03 am, "Edward K. Ream" <[email protected]> wrote:
> In any event, my initial enthusiasm for the scanner-based approach was > unfounded. I had forgotten to remove the code that completely ignores > whitespace. When I did so, the original whitespace failure reappeared! Rev 4767 of the trunk completes the present work on importers. **Important**: The new import code uses the token-based verification scheme. Note that the new scheme affects *all* of Leo's importers, not just html and xml. All the unit tests pass, but the possibilities for new kinds of failures remains. Please report any @auto or import problems immediately. Like the previous code, the html/xml importers "solve" the whitespace problem by completely ignoring whitespace and newlines. If the overly- lax nature of the html/xml importers ever becomes a real problem, it would be straightforward to do a more accurate comparison of html tokens in xmlScanner.filterTokens. I think the present html/xml importers are actually very good. Please let me know if they cause problems. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
