What are the limitations of WIF format (saving in DEMO versions)?

The WIF format is a simple plain ASCII file format intended for the exchange of weaving files among different programs.

Things that WIF lacks (and ArahWeave supports):

	•		fabric background color
	•		colorimetry with CIE Lab specified colors (only RGB colors are supported, and only one color - no distinction between screen and print colors)
	•		the concept of repeat
	•		denting
	•		regulator
	•		yarn composition
	•		multicolor yarns
	•		mouline / melange / chenille / printed / slub yarns
	•		data necessary for fabric calculation of fabric consumption (total number of ends in warp, selvedges, reed width, finished width, ...)
	•		yarn coun!!
	•		well structured form, which would facilitate efficient and fault tolerant reading, storage, browsing

So any of this advanced features, or any jacquard capabilities will not be saved in WIF files. ArahWeave demo will automatically add .WIF to your filenames.

What WIF has (in ArahWeave's implementation):

	•	weave up to 99 shafts
	•	warp and weft pattern
	•	warp and weft colors
	•	warp and weft density (in the form of yarn space)
	•	yarn diameter; each yarn can have its own diameter

What WIF has (but ArahWeave does not support):

	•		Variable density, in the form of yarn space; it is presented in a form which is completely different from a weaver's view of handling density (via regulator and denting).
	•		tredling - does not exist in industrial use

What WIF has (but nobody needs):

	•		the possibility to have the same thread in two different shafts
	•		the possibility to specify the range of colors in RGB specification (like from 0-65536)

If WIF is so bad, why do you support it? To be fair - WIF just reflects the needs its user base - hobbyist handweavers. As such, it fulfills its purpose. We are grateful to WIF's authors, since even a poor standard is much better than no standard at all.