Re: t/DOMDocument.t fails

<[email protected]> writes:

> Hi, folks.  I finally managed to build a Xerces.so that doesn't bomb
> upon loading via use XML::Xerces.  (I'll give the gory details in the
> thread "Building Xerces.so on a Debian system", if anyone is
> interested).

Excellent! Sorry again that it took so much effort.

> So now the only test that fails is t/DOMDocument.t.  Out of 35,125
> subtests, 62 of them fail.  The error messages for these 62 failed
> subtests all have the same form; for example:
>
>   Error code: 5
>   not ok 662
>   #     Failed test (t/DOMDocument.t.skip at line 218)
>   char: <0x00C0>
>
> Does anyone have any idea of what could be going wrong?

The oddly named DOMDocument test is actually a test of your unicode
system - it iterates over all unicode characters defined in XML 1.0
that can be used to begin an element name and attempts to create an
XML document with a single element that begins with that character.

So when this fails it means that something is not configured correctly
for using unicode. 

It is included in the FAQ:

  C. Unicode Support
  ==================
  C.1 Why do a bunch of tests fail in t/DOMDocument.t?
  
    - If they are 662..723, try setting your LC_CTYPE environment
      variable to something besides the default value of "C", such as:
  
      export LC_CTYPE=en_US
  
    - Otherwise, are you using Perl-5.6.0 or greater?
  
Cheers,
jas.