Re^2: Confusion ,XML::SIMPLE with DATA:DUMPER

[ultibuzz]

xml::twig sounds good, if vpn is working right i will test now some.
i just came home from a 12 hour working day
big thanks to joos and you for that hind with xml:twig

UPDATEi have tryed this snipet and this is the output

PHONENO:877465535
PHONENO:86719273704
PHONENO:8671881760
PHONENO:8671969876

not well-formed (invalid token) at line 17, column 14, byte 313 at C:/
+Perl/site/lib/XML/Parser.pm line 187

i added 'REASON/DATE_OCCURRED' => \&print_n_purge because i thought its related to that i don't take this element of REASON. but this didn't help

UPDATE2 well now i don't understand this, i jsut copy the informations ina a file called test2.xml and start over and i got this

PHONENO:867112593
PHONENO:86719273704
PHONENO:8671881760
PHONENO:8671969876
REASON:highspender limit exceeded

no element found at line 52, column 16, byte 1252 at C:/Perl/site/lib/
+XML/Parser.pm line 187

as you can see now the Reason is ther still an error but the reason is printed

[Joost]

Looks like your "XML" file isn't well-formed (note the line and column numbers in the error messages refer to the line and column in the XML file). In effect that means it's not valid XML and you should return it to whoever created it and let them figure out how to write well-formed XML first.

update: it appears the problem is the ü character. Adding an xml prolog that indicates the correct encoding should fix it. Add something like this at the very beginning of the file:

<?xml version="1.0" encoding="ISO-8859-1"?>

Your encoding is probably iso-8859-1 (latin-1), CP1252 (latin windows encoding) or utf-8 (one of the unicode encodings)

[ultibuzz]

i forgot to xopy the firstline of the main file
<?xml version="1.0" encoding="ISO-8859-1"?>
is what is standing there
with this in the testfile the error is gone

this file is in kinda good shape, sometimes we get files i can't even say what is waht but we need to live with that ;/

[Joost]

this file is in kinda good shape, sometimes we get files i can't even say what is waht but we need to live with that ;/

In my experience it's always better to not accept any XML file that isn't well-formed - that's the official recommendation for XML parsers anyway. Trying to retoactively fix a non wellformed file always leads to trouble. Getting whoever creates the files to fix their process to create real XML files (instead of files that only look like XML) is always a better choice.

update:

i forgot to xopy the firstline of the main file

<?xml version="1.0" encoding="ISO-8859-1"?>

is what is standing there with this in the testfile the error is gone

I'm not 100% sure, but if I read the source of your original post correctly, the original XML file isn't in iso-8859-1 but some form of unicode encoding. probably utf-8. That would also explain why copying the file in an editor works, since that can change the encoding.