Skip Menu |

This queue is for tickets about the Config-Any CPAN distribution.

Report information
The Basics
Id: 43834
Status: rejected
Priority: 0/
Queue: Config-Any
People
Owner: Nobody in particular
Requestors: ddascalescu+perl [...] gmail.com
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in: 0.17
Fixed in: (no value)

History Show all quoted text
  Wed Mar 04 07:49:42 2009 ddascalescu+perl [...] gmail.com - Ticket created
Subject: Error loading UTF-8 JSON with BOM?
I'm using Config::Any::JSON in conjunction with FormFu. In a :FormConfig action, if the JSON that it loads is UTF-8 encoded and has the BOM, I get this error: Error parsing ...\root\forms\index.json: malformed JSON string, neither array, object, number, string or atom, at character offset 0 ["\x{feff}{n "id": "c..."] at C:/strawberry/Perl/site/lib/Config/Any/JSON.pm line 54.
  Wed Dec 09 14:08:38 2009 bricas [...] cpan.org - Status changed from 'new' to 'open'
  Wed Dec 09 15:09:09 2009 bricas [...] cpan.org - Correspondence added
I'm marking this as stalled since I really have no clue how to handle this. Is the BOM truly required?
  Wed Dec 09 15:09:13 2009 bricas [...] cpan.org - Status changed from 'open' to 'stalled'
  Fri Jun 04 08:50:34 2010 bricas [...] cpan.org - Correspondence added
After much thought, I've decided to reject this ticket. Config::Any simply delegates config parsing to another module. You should report the inability to handle "Byte Order Marks" to the author of the "upstream" JSON parser.
  Fri Jun 04 08:50:35 2010 The RT System itself - Status changed from 'stalled' to 'open'
  Fri Jun 04 08:50:36 2010 bricas [...] cpan.org - Status changed from 'open' to 'rejected'