On 03 Jan 2014, at 21:07, Sebastian Sastre <sebast...@flowingconcept.com> wrote:
> It's probable unrelated to size as expected. > > For the record: > > I've changed the XMLParser how? I do not know if SIxx fixes the version of the XML parser it uses. > and the new one complained about a problem on a specific line that has this > content > > <sixx.object sixx.id="1106" sixx.name="key" sixx.type="String" > >name</sixx.object> > > <sixx.object sixx.id="1107" sixx.name="value" sixx.type="String" > >���L���i���k���e��� > ���M���a���r���k��� > ���T���w���a���i���n���:��� > �� > ���I���'���v���e��� > ���n���e���v���e���r��� > ���l���e���t��� > ���m���y��� > ���s���c���h���o���o���l��� > > ���i���n���t���e���r���f���e���r���e��� > ���w���i���t���h��� > ���m���y��� > ���e���d���u���c���a���t���i���o���n���.�� > </sixx.object> > > </sixx.object> > > looks like an encoding problem > > > > On Jan 3, 2014, at 5:59 PM, Sebastian Sastre <sebast...@flowingconcept.com> > wrote: > >> Hi guys, >> >> anyone here using SIXX? >> >> I'm having a consistent problem in opening a SixxReadStream on a file that >> has ~10MB of serialized objects. >> >> Smaller than that is all good >> >> Bigger, raises SixxXmlParseError >> >> ideas? >> >> Maybe I'm using the wrong version of XMLDOMParser? >> >> patches? workarounds? >> >> sebastian >> >> o/ >> >> PD: sixx was loaded with: >> >> Gofer it >> squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfSIXX'; >> load. >> >> (Smalltalk at: #ConfigurationOfSIXX) project latestVersion load. >> >> >> >