invalid image links for baseURL with subdirectory and relativeURLs=true

[McShelby]

As discussed in the forum, there is a regression when generating image links between 0.123 and previous versions in a multilang setup if a baseURL other than / and relativeURLs=true are given.

The markdown image link to the bundles's resource:

![kitten](a.jpg)

results in in broken link (one step up is missing)

<img alt="kitten" src="../../foo/en/s1/a.jpg">

while in previous versions it was

<img src="a.jpg" alt="kitten">

Thanks to @jmooring for the example repo

From the discussion, it's unclear if this is a bug or (because of the used option combination) is undefined behavior.

[jmooring]

To clarify, going as far back as v0.54.0¹, this combination has never worked with either monolingual or multilingual sites:

baseURL = 'https://example.org/foo/'   <-- includes subdirectory
relativeURLs = true

So then people got "clever" and started making URLs both relative and canonical at the same time (sigh):

baseURL = 'https://example.org/foo/'   <-- includes subdirectory
relativeURLs = true
canonifyURLs = true

And in some cases that helped, probably due to luck more than anything else.

Footnotes

1. I didn't bother testing anything earlier. ↩