l10n-sample does not show/explain how to use translation keys/translate when vscode is set to english

[onfireprojects]

Extension sample

l10n-sample

VS Code version

1.98.2

What went wrong?

I was trying to show translations that deviate from the used translation message (e.g. "Hello") in the english translation.

In the l10n-sample, if a bundle.l10n.en.json and/or bundle.l10n.json are added in the "l10n" folder alongside the japanese version, the translations from those files are not used. Only the used translation message (e.g. "Hello") is displayed at all times.
Either this (and thus also working with keys like "info.message.hello" instead of "Hello") does not work at all, or the "documentation"/readme is lacking info, as it implies that >any< existing bundle.l10n..json is automatically used, if available, without making an exception for "en".

Expected behavior:
Either

• Sample including instructions how to add and use a "default translation file"/deviating translations for english
  or
• Readme explaining, that translating via keys/english is not supported (and the message property has thus always have to be readable english)

[TylerLeonhardt]

This is a duplicate of:
microsoft/vscode#168127

basically, whatever the text is in the call that will be used for the default language.

[onfireprojects]

This is a duplicate of: microsoft/vscode#168127

basically, whatever the text is in the call that will be used for the default language.

the fact that the original translation-"key" is supposed to be in the call should be at least part of the readme, independent of changes/enhancements talked about in the other post

[TylerLeonhardt]

It is called out in the API:
https://code.visualstudio.com/api/references/vscode-api#l10n