Case 1

Steps to reproduce

1. Upload any .png or .jpg Image in Assets-App creating a new Asset
2. Change language and upload other images for different languages (using example multisite configuration: config.modules.multisite.config.sites.xml and i18n: config.server.i18n.xml )
3. Generate Link in Freemarker Template with damfn.getAssetLink (Variation Aware with default Variation) for said asset (using its itemkey) adding a non default or fallback language for the current site at the start (example result: /en/.imaging/mte/<name of theme>/default/dam/<path to image>/jcr:content/<name of image>.png)
4. open link in website

Expected results

The Image that was uploaded in the corresponding language determined by path (in this case english)

Actual results

The Image with which the asset was created at first, completely ignoring i18n

Case 2

Steps to reproduce

1. Upload any .png or .jpg Image in Assets-App creating a new Asset
2. Change language and upload other images for different languages
3. Generate a direct link (using either damfn.getAssetLink or cmsfn.link) adding desired language at the start (example link: /en/dam/jcr:8deeb22d-d9d7-403f-9a0c-3d8046253154/<name of image>.png)
4. Use a Hostname that is configured in Multisite (example configuration below):
5. Open the following url (example): https://dev-bg.neusta-ws.de/en/dam/jcr:8deeb22d-d9d7-403f-9a0c-3d8046253154/<name of image>.png 

Expected results

The Image that was uploaded in the corresponding language determined by path (in this case english)

Actual results

The Image that was uploaded in the language determined by fallbackLocale (in this case bulgarian)

Workaround

Development notes