From: Gregory Machin
> Thanks Terry for responding.
>
> The files are very big and contain data I'd prefer not to be out in the
> wild. what parts of the file would be helpful , I can provide the lines
> with the text and say heard part of the xml ??
>
> Thanks
> G
Yep, that should be enough.
On Wed, Jun 26, 2013 at 7:45 AM, Peter Gordon wrote:
> On Wed, 26 Jun 2013 12:36:01 +1200, Gregory Machin wrote:
> >
> >Looks like the data already is utf8, but the header of the XML
> >specifies otherwise.
> >How do you parse the data? Can you give us a short example file?
> >
> >Jenda
>
> This
On Wed, 26 Jun 2013 12:36:01 +1200, Gregory Machin wrote:
>
>Looks like the data already is utf8, but the header of the XML
>specifies otherwise.
>How do you parse the data? Can you give us a short example file?
>
>Jenda
This is a bit of code I adapt to whichever encoding I require.
use open ":enc
Thanks Terry for responding.
The files are very big and contain data I'd prefer not to be out in the
wild. what parts of the file would be helpful , I can provide the lines
with the text and say heard part of the xml ??
Thanks
G
On Thu, Jun 20, 2013 at 7:42 PM, Jenda Krynicky wrote:
> From:
From: Gregory Machin
> I'm debugging an application written in Perl that converse data exported
> from the Nessus security scanner in xml format. I have narrowed down the
> bug to an issue with special characters in names that are in the file such
> as Fr~A©d~A©ric and Gr~A©goire , thus ~A© are
Hi.
I'm debugging an application written in Perl that converse data exported
from the Nessus security scanner in xml format. I have narrowed down the
bug to an issue with special characters in names that are in the file such
as Frédéric and Grégoire , thus é are most likely the guilty parties.
