These files will cause processing errors and should be renamed by hand, replacing the non-ASCII chars with dashes. (An example is 20050219 on an AdiumHTMLLog file.) Bad Log File NamesĮxamples have been found of Adium HTML-based log files with strange separator characters in the date written into the filename. The adium_xml.py input processor attempts to strip these characters if initial XML parsing fails. decode() tricks don't seem to strip them. The existence of ASCII control characters (such as hex 0x19, reportedly misused by Microsoft products for 'smart single quote' and seen in copied/pasted content) are especially problematic, as they terminate XML parsing when encountered, and the normal Python. Illegal XML Charactersĭespite writing files that claim to be well-formed XML 1.0, it appears that some versions of Adium did not sanitize their inputs very well. bkup added, so they won't be picked up by the processor on future runs. Original files are preserved with the extension. It is designed to be run against the failed_YYYY-MM-DD.log files produced by the bulk_convert.sh script. These files can be easily fixed using the Mac OS sed command:Ī small Bash script which runs this command against a list of files is included in the /extras directory as fix_xml_close.sh. Missing tags are particularly common in some periods (most are dated around early 2003, and the issue was apparently fixed by mid-2004). It appears that some versions of Adium produced malformed XML log files. Known Bugs / Limitations Incomplete Facebook Chat LogsĪdium logs of Facebook chat conversations (from the period when Facebook was using an open standards, XMPP-compatible chat service) seem to be frequently malformed.Īlthough the tool attempts to link Facebook user IDs to real names (stored as 'aliases' in the XML), this is only occasionally possible.Īlso, some logs appear to only contain one side (usually the remote) of the conversation, for reasons that are not clear.Ī possible cause is related to how Facebook handled multiple-device support: received messages were likely 'broadcast' to all signed-in devices, but transmitted messages from a device other than the computer running Adium were not re-sent out by Facebook's servers, and thus are not included in the Adium log. no-background Strips background color from message text clobber Overwrite identically-named output files h, -help show this help message and exit Outdirname Output directory (optional, defaults to cwd) Usage: adiumToEml.py infilename Ĭonvert Adium log files to RFC822 MIME text files (.eml) The most up-to-date usage options can be listed by running. py-dateutil - extensions to the python datetime module, including timezone-aware date parsing.Required Libraries / PackagesĪ few packages not included in Python's standard library are required for operation, and can be installed using pip. chatlog, although the tool will also process files ending in. (Usually ~/Documents/Adium/Logs or potentially also ~/Library/Application Support/Adium/Logs, but could be placed elsewhere.) with find and xargs in order to run it on the entire Adium Logs directory. In most cases, you probably want to call this from a wrapper script, e.g. If outputdir is not specified, the working directory will be used instead. Conversion tool to migrate Adium chat logs to RFC822.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |