On Tue, 12 Feb 2008 5:01:44 pm Graeme Gill wrote: > You've misunderstood the purpose of the "EXPECTED" block in the .cht > file. [...] > The description in the .cht description document makes this reasonable > clear, as the EXPECTED fields are optional and approximate: Ah, OK. Thanks a lot. So it's a hinting towards the orientation algorithm to align the patches with for reading with the template. Still, one question remains: Is it possible to leave meta data, even in the form of comments, inside a .cht file? Or for the same reasons in the other file formats as used by ArgyllCMS. This way it would be possible to e. g. leave version information inside the file, that could be used by a (human) user to be more descriptive. Then one would not have to refer to "the file xyz.foo with size 13421 bytes from ABC", but it could be identified or described internally. I recall you just referred to an ICC profile recently in a similar way ... Especially when developing something (as in this case a .cht file), it is often a good idea to leave e. g. a software version management identification string inside to disambiguate versions without the need of another software tool for comparison. Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Putaiao o Mohiohio me Pangarau Room 2.63, Quad Block A Building Massey University, Auckland, Albany Private Bag 102 904, North Shore Mail Centre voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 eMail: G.Kloss@xxxxxxxxxxxx http://www.massey.ac.nz/~gkloss/