defaultContentLanguageInSubdir and links in languages.toml

[strauhmanis]

Is your feature request related to a problem? Please describe
The problem is that the functioning of the option defaultContentLanguageInSubdir depends on the hardcoded into languages.toml links (i.e. "/en/about").

Describe the solution you'd like
Although, I do not know whether there is or is no limitation with the Hugo to arrive at this specific solution, my description of it is as follows:

Perhaps, and in the example of the "/en/about" link, it could be possible for the "en" part to be generated dynamically depending on the high-level definition in the languages.toml (i.e. "[en]" and "[nl]" and "[mylang]"), and depending on whether the defaultContentLanguageInSubdir option is true or false, as well as depending on the weight.

Describe alternatives you've considered
As is now, the alternative to the proposed solution, is to change the hardcoded links by hand whenever the defaultContentLanguageInSubdir is set to true or false and whenever language's weight is altered.

Additional context
Please see the attached screenshot in respect to the proposed solution.

[markdumay]

Thanks for pointing this out, I agree the current configuration is kind of messy. I submitted a new release to fix this, see this PR for the changes. All URLs should now be decoupled from the language configuration. Let me know if this behaves as expected.

Regarding the contentDir, this depends on your specific Hugo configuration. You can organize content translations by either content directory or by filename. Hinode uses organization by content directory as an example, but you should be able to adjust this in your own project as desired.

[strauhmanis]

Thank you very much, Mark!
The change you introduced is excellent and behaves as excepted!