- From: Fuqiao Xue <notifications@github.com>
- Date: Wed, 10 Nov 2021 00:41:31 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 10 November 2021 08:41:43 UTC
According to my understanding (please correct me if I'm wrong): * "string replacement" refers to something like the proposal in https://github.com/w3c/manifest/issues/211 , and * "maintaining separate translation files" refers to something like [Chrome extensions](https://developer.chrome.com/docs/extensions/reference/i18n/), which creates a separate file/directory for each supported language or locale. Both approaches intend to solve the problem of translation/localization, not the problem of the language and direction metadata of the strings itself. There is no way to override the language and direction for a specific natural language text field. See the "String metadata" part of https://github.com/w3c/miniapp-manifest/pull/12#issuecomment-811624265 . -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/968#issuecomment-964901794
Received on Wednesday, 10 November 2021 08:41:43 UTC