Hello trid users,
some days ago i handled some Device Metadata Packages, which are Microsoft
Cabinet archive. So i look for other CAB archives. So i look for Microsoft
InfoPath Form template with file name extension xsn.
When running trid on such samples, some like APPRATE.XSN and INVOICED.XSN
are not recognized as "InfoPath Dynamic Form - Template" by xsn.trid.xml
(See appended output/trid-old.txt).
For comparison reason i run other utilities. The newest file utility
{https://en.wikipedia.org/wiki/File_(command)} describes such samples in
general as "Microsoft Cabinet archive"( See appended output/file-5.38.txt).
So i update xsn.trid.xml by running tridscan on undetected samples and then
manually refine definition.
The current used URL for infopath on Microsoft now points to a site
concerning Microsoft Office product in especially Office 365. So i
replaced reference URL by InfoPath page on Wikipedia. This is expressed by
comment line with reference URL like:
<RefURL>
https://en.wikipedia.org/wiki/Microsoft_InfoPath</RefURL>
Also display now standard CAB mime type by line:
<Mime>application/vnd.ms-cab-compressed</Mime>
Because XSN file are CAB archives content can be listed by 7z with list
option ( See appended output/7z-l.txt).
So in most examples there exist a file with name like view*.xsl. This was
expressed in side global strings section by line:
<String>VIEW</String>
In non described examples the XSL file have a name like default.xsl. So now the
above string line vanish.
From 7z and file command output is visible that first cabinet member is a
file with name "manifest.xsf". This is not clearly mentioned on
documentation sites. So i mention this fact by a remark line like
<Rem>1st archive member is manifest.xsf</Rem>
With the updated trid definition all my inspected XSN samples are now
described correctly ( see appended output/trid-new-v.txt). TrID
definition and output are stored in archive xsn.zip. I hope that
my updated XML file can be used in future version of triddefs.
With best wishes
Jörg Jenderek
