In setting up a VF, it is often the case that a spreadsheet is used to keep track of correspondences between a designer’s values (often measured in stem widths) and intended OpenType values, with arbitrary methods used to calculate or judge the correspondences.
Fencer would benefit from a textbox accepting input copied from a spreadsheet, accepting either 2-column (1-axis mappings) or 4-column (2-axis mappings). If 2 columns are received, then Fencer’s current X axis is used; if 4 columns are used, then Fencer’s current X and Y axes is used.
In this example, we have selected Weight on Fencer’s X axis, Width on Fencer’s Y axis, then wish to map various input values of Weight and Width to output values of Weight and Width.
Input X
Input Y
Output X
Output Y
200
75
210
71
300
75
340
71
400
75
400
71
500
75
550
72
600
75
640
75
700
75
730
80
800
75
810
84
900
75
900
86
Copying directly from a spreadsheet, and Fencer handling the tab delimited data, is more convenient than editing XML by hand.
In setting up a VF, it is often the case that a spreadsheet is used to keep track of correspondences between a designer’s values (often measured in stem widths) and intended OpenType values, with arbitrary methods used to calculate or judge the correspondences.
Fencer would benefit from a textbox accepting input copied from a spreadsheet, accepting either 2-column (1-axis mappings) or 4-column (2-axis mappings). If 2 columns are received, then Fencer’s current X axis is used; if 4 columns are used, then Fencer’s current X and Y axes is used.
In this example, we have selected Weight on Fencer’s X axis, Width on Fencer’s Y axis, then wish to map various input values of Weight and Width to output values of Weight and Width.
Copying directly from a spreadsheet, and Fencer handling the tab delimited data, is more convenient than editing XML by hand.