gohugoio / hugo

The world’s fastest framework for building websites.
https://gohugo.io
Apache License 2.0
73.62k stars 7.39k forks source link

Incorrect diagram directory in multilingual project with asciidoctor #10473

Open anlar opened 1 year ago

anlar commented 1 year ago

What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.107.0-2221b5b30a285d01220a26a82305906ad3291880+extended linux/amd64 BuildDate=2022-11-24T13:59:45Z VendorInfo=gohugoio

Does this issue reproduce with the latest release?

Yes.

Details

When using Hugo to render asciidoc articles containing diagrams by default it puts diagram images to the folder without language prefix even for multilingual projects.

Scenario 1 (single language) - OK

E.g. I have a project with a single language and an article content/post/post-3.ru.adoc with a diagram which will be rendered to:

$ tree public/post/post-3/
public/post/post-3/
├── index.html
└── sequence-diagram-example.svg

It works just fine, post-3 will reference its diagram from public/post/post-3 directory.

Scenario 2 (project with language directories) - FAIL

Now I have a project with several languages - each of them in its own directory, config.toml:

defaultContentLanguage = 'ru'
defaultContentLanguageInSubdir = true

post-3 will be put to (and tries to reference diagram from here):

$ tree public/ru/post/post-3/
public/ru/post/post-3/
└── index.html

But diagram still located in non-language directory:

$ tree public/post/post-3/
public/post/post-3/
└── sequence-diagram-example.svg

Workaround

For now I'm able to bypass that issue by manually setting image location in each article. From above example:

:imagesoutdir: public/ru/post/post-3
github-actions[bot] commented 1 month ago

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help. If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open. If this is a feature request, and you feel that it is still relevant and valuable, please tell us why. This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.