Page 1 of 1

.ct file version string

Posted: Sat Feb 22, 2014 2:04 pm
by JosDuchIt
What's wrong with this version string ?

## version $VER: AmigaWriter.catalog 03.00 (02.02.2014)

6.Stock:AmigaWriter/Catalogs/français> Flexcat Amigawriter2.2French.ct CATALOG Amigawriter2.2French.catalog
ERROR: '$VER: AmigaWriter.catalog 03.00 (02.02.2014)' is not a valid version value

Re: .ct file version string

Posted: Sat Feb 22, 2014 2:20 pm
by gazelle
JosDuchIt wrote:What's wrong with this version string ?
## version $VER: AmigaWriter.catalog 03.00 (02.02.2014)
Nothing. Maybe you are using an old version of flexcat?

I personally would remove leading/trailing zeros from versionnumbers "03.00" -> "3.0"

Re: .ct file version string

Posted: Sat Feb 22, 2014 6:02 pm
by nbache
gazelle wrote:
JosDuchIt wrote:What's wrong with this version string ?
## version $VER: AmigaWriter.catalog 03.00 (02.02.2014)
Nothing.
Actually, there is. Zero is not valid as a revision in AmigaOS, all revisions have to start at 1.
I personally would remove leading/trailing zeros from versionnumbers "03.00" -> "3.0"
Yep, so would I, and also the leading zeroes in the date and month, as they are not needed. (But both of those things are strictly speaking valid, AFAIK.)

So my choice for the example above would be:

## version $VER: AmigaWriter.catalog 3.1 (2.2.2014)

Edit: Are you sure the program does look for a catalog with version 3? The version (the number before the dot) cannot be chosen freely, it has to match what the program tries to open.

Best regards,

Niels

Re: .ct file version string

Posted: Sun Feb 23, 2014 5:38 pm
by JosDuchIt
@nbache & gazelle thanks
i copied the verion string from an existing catalog.file and this worked OK.
at least i got an output catalog.

The catalog description file
amigawriter.cd 47285 29/06/2000
(from Amigawriter 2.2.demo or from 2.0 to 2.2 patch)
seems to be corrupt however. When you generate a catalog eg from the 2.2demo
flexcomp/catcomp Amigawriter.cd Amigawriter_deutsch3.ct CATALOG Amigawriter.catalog
you get a catalog showing incorrect strings in most places when running Amigawriter
Asked for help to Alinea Computer.

Re: .ct file version string

Posted: Sat Mar 08, 2014 9:55 pm
by trixie
I have the very same problem with catcomp. My catalog translation file has

## version $VER: encoders.catalog 1.1 (8.3.2014)

and when I try to convert the .ct into a .catalog, I get:

ERROR: '$VER: encoders.catalog 1.1 (8.3.2014)' is not a valid version value

As you can see, there are neither trailing zeroes, nor a 0 revision number. I'm using catcomp from the latest SDK.

Re: .ct file version string

Posted: Sat Mar 08, 2014 10:21 pm
by joerg
trixie wrote:I have the very same problem with catcomp. My catalog translation file has

## version $VER: encoders.catalog 1.1 (8.3.2014)

and when I try to convert the .ct into a .catalog, I get:

ERROR: '$VER: encoders.catalog 1.1 (8.3.2014)' is not a valid version value

As you can see, there are neither trailing zeroes, nor a 0 revision number. I'm using catcomp from the latest SDK.
This error message seems to be for a bad version string in the .cd file, not in your .ct translation file. For a wrong one in .ct you should get "... is not a valid version number".

Re: .ct file version string

Posted: Sat Mar 08, 2014 10:38 pm
by trixie
@joerg
This error message seems to be for a bad version string in the .cd file
OK, but I'm not feeding the .cd file to catcomp at all, I'm doing

catcomp encoders.ct CATALOG encoders.catalog

so why would catcomp report an error in a file that it doesn't even receive as parameter?

Re: .ct file version string

Posted: Sat Mar 08, 2014 10:43 pm
by gazelle
@trixie

You can't build a catalog without an .cd file. The ids are only stored in the descriptor file not in the translation file.

[deleted]see jörgs description below[/deleted]

Re: .ct file version string

Posted: Sat Mar 08, 2014 10:46 pm
by joerg
trixie wrote:@joerg
This error message seems to be for a bad version string in the .cd file
OK, but I'm not feeding the .cd file to catcomp at all, I'm doing

catcomp encoders.ct CATALOG encoders.catalog

so why would catcomp report an error in a file that it doesn't even receive as parameter?
Catcomp can't work without a .cd file, and since the template is "DESCRIPTOR/A,TRANSLATION,CATALOG/K,CTFILE/K,..." it's using your .ct file as DESCRIPTOR (.cd) file instead of TRANSLATION (.ct) file.

Re: .ct file version string

Posted: Sat Mar 08, 2014 10:52 pm
by trixie
@gazelle, @joerg

OK, got it now. It was all my fault, then - don't know why I assumed the catalog is made from the translation file only. Thanks for help!