Translations of Markdown files not detected

[zamojski]

Hello, I need help with configuring translation components for Markdown files, configured like below:

File mask: app/src/main/res/raw-*/info_about_api_key_content.md
Language filter: ^[^.]+$
Monolingual base language file: app/src/main/res/raw/info_about_api_key_content.md

The problem is that translations are not detected - 0% for all non-base languages. Very similar configuration works for App UI component (however a different file format). The translations are present in the configured folder, see: https://github.com/zamojski/TowerCollector/tree/master/app/src/main/res/raw-DE for example.

Any suggestions are warmly welcomed. In the end I want to have 15 components of that kind, so it would be the best to have a working template for those.

Best regards
Adam

[nijel]

Most likely this is the issue described in #18023

[nijel]

translate/translate#6094 should make the situation better if the document structure is in sync. It will need a companion in Weblate, but I'd like to have it for the next bugfix release.

[zamojski]

The structure of documents is the same in all languages, I've checked that. Is there any way to trigger the update to see if the fix worked or not? When do you plan the next release?

[nijel]

For Markdown it didn't work even with the same structure because the library initially didn't expose string locations, so Weblate integration didn't match the existing translations at all.

I don't think there is any other way to test it out besides recreating the component.

[zamojski]

I've just created a new Markdown component but it doesn't seem to improve in any way.
https://hosted.weblate.org/projects/tower-collector/app-info-about-mls-project/

[nijel]

It can't be better until #18074 is merged (which in turn is waiting for translate-toolkit release).