search

chandlerbeck / googlevoice-to-sqlite

Automatically exported from code.google.com/p/googlevoice-to-sqlite
0 stars 0 forks source link

xml.etree.ElementTree.ParseError: not well-formed (invalid token) #13

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?
No errors...

What version of the product are you using? On what operating system?
googlevoice_to_sqlite_v3.2.2_win32.zip

Please provide any additional information below.
C:\G2Sql>googlevoice_to_sqlite.exe
Specify the Calls file location (ends with "\Voice\Calls"): 
C:\Users\jxxx.TRANSIT\GoogleTakeout\Voice\Calls
Andrea_Pxxe_-_2012-03-17T02-44-47Z.htmlTraceback (most recent call last):
  File "googlevoice_to_sqlite.py", line 429, in <module>
  File "googlevoice_to_sqlite.py", line 382, in getobjs
  File "xml\etree\ElementTree.pyc", line 1301, in XML
  File "xml\etree\ElementTree.pyc", line 1643, in feed
  File "xml\etree\ElementTree.pyc", line 1507, in _raiseerror
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 152, 
column 38

After trying several times, I ended up deleting the GoogleTakeout files for 
this particular person....hoping that perhaps there was something about those 
files that was wrong.

On the next run...a new error was present:

C:\G2Sql>googlevoice_to_sqlite.exe
Specify the Calls file location (ends with "\Voice\Calls"): 
C:\Users\jcolpean.TRANSIT\GoogleTakeout\Voice\Calls
Dan_xxx_-_2011-07-20T22-20-27Z.htmlTraceback (most recent call last):
  File "googlevoice_to_sqlite.py", line 437, in <module>
  File "googlevoice_to_sqlite.py", line 330, in import_Audio
TypeError: 'NoneType' object has no attribute '__getitem__'

Original issue reported on code.google.com by jamiecol...@gmail.com on 3 Jan 2013 at 8:16

GoogleCodeExporter commented 8 years ago 
I've been very hopeful about using this code.  However, the following error 
occurs.
***My apologies, I am in NOT a developer.

Original comment by jamiecol...@gmail.com on 3 Jan 2013 at 8:17

GoogleCodeExporter commented 8 years ago 
Issue 12 has been merged into this issue.

Original comment by handspri...@gmail.com on 6 Jan 2013 at 4:45

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I should have just patched the first of those issues. I believe the second is 
duplicated as a separate issue... let me check.

Original comment by handspri...@gmail.com on 6 Jan 2013 at 5:42

GoogleCodeExporter commented 8 years ago 
What type of record is Dan_xxx_-_2011-07-20T22-20-27Z.html? Could you possibly 
email me a (redacted) copy?

Original comment by handspri...@gmail.com on 6 Jan 2013 at 5:53

GoogleCodeExporter commented 8 years ago 
File as requested...

Original comment by jamiecol...@gmail.com on 7 Jan 2013 at 1:13

GoogleCodeExporter commented 8 years ago 
Fixed in the new version. (Turns out that the files aren't actually UTF-8 as 
claimed by the data, but ISO-8859-15...)

Original comment by handspri...@gmail.com on 5 Feb 2013 at 9:21