> Tablature automatic string and fret calculations should proceed from
> the lowest-pitched string to the highest-pitched string. A context
> property is available to tell whether string one is the
> highest-pitch string. Setting highStringOne to ##t should have the
> calculation start with the highest-numbered string and proceed to
> the lowest-numbered string (which would be the lowest pitch to the
> highest pitch). The calculation instead starts from string one,
> regardless of the setting of highStringOne. [...]
Thanks. Please open an issue!
Werner
