Package: freeguide
Version: 0.10.4-2
Severity: wishlist

Recent versions of 'freeguide' keep TV listings in '.ser' files:

    % file ~/.freeguide/day-2007-03-27-B.ser
    /home/alfie/.freeguide/day-2007-03-27-B.ser: Java serialization data, 
version 5

A search of the 'freeguide' man page, docs, help files and Wiki doesn't
seem turn up a mention of this format.  Online there were a few
messages on programmers mailing lists, but nothing for the novice.

I couldn't find '.ser' in the 'Wotsit' database, but there is an entry here:

    http://filext.com/detaillist.php?extdetail=.ser&Search=Search

It says it's a kind of Java data file, though nothing specific about
'freeguide'.  

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 older 'freeguide' xml files could be used to show TV
info in 'tvtime'.)

Hope this helps...


-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-3-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)

Versions of packages freeguide depends on:
ii  gij [java-virtual-machine]    4:4.1.1-15 The GNU Java bytecode interpreter
ii  gij-4.0 [java-virtual-machine 4.0.3-2    The GNU Java bytecode interpreter
ii  gij-4.1 [java2-runtime]       4.1.1-20   The GNU Java bytecode interpreter
ii  j2re1.4 [java2-runtime]       1.4.2.03-1 Blackdown Java(TM) 2 Runtime Envir
ii  xmltv-gui                     0.5.45-2   Graphical user interface related t

Versions of packages freeguide recommends:
ii  xmltv-util                    0.5.45-2   Utilities related to the XMLTV fil

-- no debconf information


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

Reply via email to