From: Jérôme <rom...@ya...> - 2010-09-09 09:28:52
|
> "/usr/share/gramps/plugins/import/ImportXml.py", line 2405, > in __init__ > self.__p.ParseFile(xml_file) > ExpatError: not well-formed (invalid token): line 1, column > 11 In fact, you are not the only one [1] But this type of error may also occur if your rename the extension (.gpkg)! I guess you keep the .gpkg extension ? Why a possible encoding or wrong command line issues ? Because : xml_file = open_file(filename, cl), gzip.open(filename, "rb") It might be related to "&", "? or "quote" characters [2][3]! Often into Note (internal), a replace function or a non-ASCII issue on filename. $ ls your_filename_directory could return an other name than your GUI! ie. some "?" characters instead of non-ASCII characters after encoding "corruption". So filename may be wrong and/or XML header broken (encoding set, "<", ">", "?" characters): <?xml version="1.0" encoding="UTF-8"?> Maybe try: $ gunzip < your_file.gpkg > data.xml $ xmllint data.xml or open data.xml with firefox (XML parser) :-/ It also returns line error on XML validation! [1] http://www.gramps-project.org/bugs/view.php?id=4111 [2] http://www.gramps-project.org/bugs/view.php?id=3187 [3] http://www.gramps-project.org/bugs/view.php?id=2808 Serge Noiraud a écrit : > jerome a écrit : >> Maybe it is related to the encoding with command line ? >> >> How do you move your file from hardy to lucid ? >> USB key, CD, network, device mounted ? >> > by mail and scp for my lucid in a virtual machine > > I made a diff between the xml file with error and the last one which is ok. > the diff IS the following : > > "http://gramps-project.org/xml/1.3.0/grampsxml.dtd"> > <database xmlns="http://gramps-project.org/xml/1.3.0/"> > <header> > - <created date="2010-09-08" version="3.2.3-1"/> > + <created date="2010-09-08" version="3.2.4-0.SVN15859M"/> > <==== this works. > <researcher> > > I hoped other kind of differences. >> >> >> --- En date de : Mer 8.9.10, Serge Noiraud <Ser...@fr...> a >> écrit : >> >> >>> De: Serge Noiraud <Ser...@fr...> >>> Objet: [Gramps-devel] I can't import a gramps file >>> À: "Gramps developers" <gra...@li...> >>> Date: Mercredi 8 septembre 2010, 21h19 >>> Does someone already get this kind of >>> problem ? >>> >>> I had gramps 3.2.0 on a ubuntu hardy. I export my database >>> with media : no problem. >>> I tried to import in trunk under lucid : big problem. >>> I tried to import in the same gramps in a new db under >>> hardy: I get the following problem >>> >>> 299902: ERROR: dbloader.py: line 247: Failed to import >>> database. >>> Traceback (most recent call last): >>> File "/usr/share/gramps/gui/dbloader.py", line 237, >>> in do_import >>> self._pulse_progress) >>> File >>> "/usr/share/gramps/plugins/import/ImportXml.py", line 111, >>> in importData >>> version_is_valid(xml_file, cl) is False: >>> File >>> "/usr/share/gramps/plugins/import/ImportXml.py", line 2479, >>> in version_is_valid >>> parser = VersionParser(filename) >>> File >>> "/usr/share/gramps/plugins/import/ImportXml.py", line 2405, >>> in __init__ >>> self.__p.ParseFile(xml_file) >>> ExpatError: not well-formed (invalid token): line 1, column >>> 11 >>> >>> I installed gramps 3.2.3 : I can work with my database. >>> I export the db. >>> I create a new db then import the gramps file : same >>> problem >>> I export it then try to reimport : same problem >>> >>> I have the same problem with 3.2.4 svn >>> >>> I tried to see in the xml file. Impossible, it's a 45600 >>> lines file. >>> >>> Is there a way to debug the parsing of the gramps file ? >>> can we add _LOG.debug() ? >>> >>> I'm on ubuntu hardy. >>> >>> I tried to export my database without media. It works. >>> very strange ! isn't it ? >>> >>> Serge >>> >>> > > |