file format specification for TrID definitions packages (TRD and TRS)?

[jenderek]

Hello,
when i run file command on TrID definitions packages i get output like
     TrIDDefList.TRS: TrueType font data
     triddefs.trd:    RIFF (little-endian) data

To avoid this misidentification the magics of file command must be modified. So
i need some information about structure of TrID definitions packages. Of course
i can use the information grabbed from trs.trid.xml and trd.trid.xml. But i do
not like this procedure. It is a kind of reverse engineering. You make some
assumptions on some variables and later you detect your thoughts are only true
for some versions for example.

So does exist an "official" file format specification (at least some basic file
structure, header information and mime types not being "application/octet-stream")
for TrID definitions packages?

Thanks for answerers
jenderek

[Mark0]

Hi!

Both format aren't documented at the moment (for no particular reason, so they may be in the future).
Anyway TRS is just a standard serialization of a .NET structure.
I just updated it's definition refining it scanning a minimal TRS obtained packaging just 1 trid.xml def with the minimum amount of info possible. We'll see if it's possible to have a def for the standard .NET serialized files too.

Thanks for pointing out the issue!
Bye!