lmc-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmc-dev] Unability to open amc-Files


From: lmc-dev
Subject: Re: [lmc-dev] Unability to open amc-Files
Date: Mon, 1 Aug 2005 16:00:12 +0200
User-agent: KMail/1.7.2

Hi,

On Monday 01 August 2005 12:30 pm, address@hidden wrote:
> my FreeBSD installation of Moviefly (see "MovieFly on FreeBSD (long)")
> is unable to open amc files, even those create with Moviefly.

Thank you for your description on the FreeBSD installation. I will update the 
documentation and install-scripts so that others will have it more easy.

> I am able to create new files and save them using Moviefly. AMC is even
> able to open the Moviefly files flawlessly.
>
> The messages on the console read:
> [LMCMain] DEBUG: Autoprobing file format
> [LMCMain] ERROR: Cannot read file format: /usr/home/martin/test.amc
>
>
> Any idea how I could trace this down?

It seems you have saved the file with AMC afterwards? Otherwise maybe AMC 
transparently upgrades to a newer file version.
Try a head on the file:
$ head /usr/home/martin/test.amc

The first line should be:

 AMC_3.3 Ant Movie Catalog 3.3.x   www.buypin.com  www.ant.be.tf 

This is the ID for v3.3 format.

Moviefly is currently still working with AMCs file format v3.3, but IIRC AMC 
has a newer version 3.4 and upgraded to an XML file format.
Moviefly does not read newer versions above 3.3.

Also LMC saves strings in utf-8, while AMC uses the current Windows CP - which 
might yield some encoding problems with AMC on non-english texts.

Does AMC allow explicit saveing in v3.3 format?

Otherwise I'll guess I'll have to go program something to include v3.4 file 
format. ;)

Ciao
Uwe
-- 
#else /* !STDSTDIO */     /* The big, slow, and stupid way */
             -- Larry Wall in str.c from the perl source code

Attachment: pgp33U4JvoPvB.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]