feature: Specify absolute path for known_words #29
Description
Is your feature request related to a problem? Please describe.
I'm currently using configuration inheritance for my config files. (I'm working on sorting out an MkDocs translation solution.) It appears that known_words is looked at by referencing the specified docs_dir. I'm in a situation where I will have multiple config files inheriting the same base file, which will contain the known_words: words.txt. The base file lives in /. The language config files live in docs/locales/language, and therefore the docs_dir is . for each of them. So, it isn't finding the known_words file unless I hardcode a relative path, which then doesn't work for the primary language.
Describe the solution you'd like
Unless I'm missing something, providing an absolute path (e.g. known_words: /docs/words.txt) is not possible. The solution I'd like to see is the ability to provide an absolute path so the location of the config file and the provided docs directory are not relevant to the location of the known words list.
Describe alternatives you've considered
It is possible to override the known_words keyword to supply a relative path in the config file inheriting the base file, however, I am doing my best to keep each language config file as small as possible, and override as little as possible, to avoid duplicating anything that will need to be updated across the board later.
Additional context
If I'm missing some kind of potential change in the directory structure or other solution that would resolve this, please let me know. I've been trying things for a bit here, but I absolutely could have missed something obvious.