Hi Daniel,

[Really glad to hear you are taking over Debian maintainership!  I hope
to add an ant task to generate a Debian package automatically, so would
appreciate any advice from you about this (or even better you could do
it... :) ]

> I'm unsure of how to respond to the bug report below, and thought
> that you collectively would be in a much better position to answer.  I
> would ask that you CC [EMAIL PROTECTED] in your
> responses to it, so that the Debian bug is kept up-to-date with your
> discussion.

>> Recent versions of 'freeguide' keep TV listings in '.ser' files:
<snip>
>> A search of the 'freeguide' man page, docs, help files and Wiki
>> doesn't seem turn up a mention of this format.

The .ser files are serialised Java objects.  They are essentially part
of the internals of FreeGuide and are not designed to be understood or
used by other programs.

Programmers wanting to use them for other purposes, can of course
examine (and re-use under the GPL) the FreeGuide source code to do
whatever they like with them by deserialising them back into Java
objects and manipulating them using Java code.

> Yet the file format seems important to 'freeguide'; it would be
>> better if the docs had an explanation of what '.ser' files were to
>> 'freeguide', why '.ser' is better than 'xml', and whether '.ser' is
>> convertible to 'xml' with some standard util**, or is it a dead-end
>> file format.  

The files are an implementation detail, and I don't see any value in
mentioning them in the documentation.  Perhaps an FAQ entry might be
useful.  If anyone wanted to write it I'd happily add it to the web site.

The ,ser files are much faster to read than the unprocessed XMLTV files
which is what we used to store.  They also use less memory to read.

>> (**the older 'freeguide' xml files could be used to show TV
>> info in 'tvtime'.)

FreeGuide has an Export function under the file menu.  Choosing to
export as "XMLTV" will produce the XML files that were previously stored
in the .freeguide directory.

Would an FAQ entry be good enough to mark this bug as fixed?

Andy



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to