LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  LAE Error Code: ls.brain.node.structuredData.xmlData.locationBased-Error

    Employee
    Posted 09-18-2014 19:50

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: lae_errors

    This post has been created for discussion of error code ls.brain.node.structuredData.xmlData.locationBased-Error.

    Please reply to this thread with any description of error conditions, diagnostic information, and recommended resolutions.


  • 2.  RE: LAE Error Code: ls.brain.node.structuredData.xmlData.locationBased-Error

    Employee
    Posted 09-18-2014 19:52

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: ryeh

    Invalid byte 2 of 3-byte UTF-8 sequence.

    File was written in Portuguese - aprova��o.


  • 3.  RE: LAE Error Code: ls.brain.node.structuredData.xmlData.locationBased-Error

    Employee
    Posted 10-02-2014 05:16

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Tim Meagher

    Hi,

    Sorry for the delay in the response.
    What character set is the file in?
    Is this a UTF-8 file, or using windows-1252 character set?
    If it's not a UTF-8 file you may need to set the Charset parameter on the Optional tab of the node in order to specify the character set of the file that you are reading.

    Regards,
    Tim.


  • 4.  RE: LAE Error Code: ls.brain.node.structuredData.xmlData.locationBased-Error

    Employee
    Posted 10-22-2014 18:49

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: ryeh

    Haha, and I'm only seeing this response now, 3 weeks later.

    I had an XML file that I wanted to parse. It was a large file, so I thought I would be doing myself a favor by stripping out a few records to test. But in doing so, I had removed the header, which specified the encoding. Therefore, I ended up having to specify UTF-8 in the Optional/Charset field. When I plugged the original XML file, UTF-8 no longer needs to be specified as the node pulls it from the header.

    So all this to say what the documentation already says - Lavastorm will read the encoding from the XML header, and if it's not there, as Tim suggested, you may need to manually specify the character set.