It might be good to adjust the wording of Section 3 of the feature file syntax. Currently, it could be interpreted as if include statements in feature files worked like in other programming languages, such as the C preprocessor:
If the file name were relative, then it would be appended to the directory of the including feature file.
However, according to @miguelsousa in fonttools/fonttools#838, this is actually not the case. Instead, include paths are getting resolved relative to the first file being compiled; see Miguel’s example. It would be good if the feature file spec could make the (somewhat unusual) behavior of include statements more explicit.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3