multiple natural language text fields share language/direction [I18N]

[aphillips]

Manifest
https://w3c.github.io/miniapp/specs/manifest/#manifest

The manifest provides a number of "attributes". These start with dir and lang (which is great). But the subsequent natural language attributes don't appear to have their own dir/lang associated with them. It may not be possible to produce a manifest that is localized into more than one language or which has different language or base direction strings in it. The attributes in question are:

• appName
• shortName
• description
• (maybe??) versionName

[zhangyongjing]

Manifest
https://w3c.github.io/miniapp/specs/manifest/#manifest

The manifest provides a number of "attributes". These start with dir and lang (which is great). But the subsequent natural language attributes don't appear to have their own dir/lang associated with them. It may not be possible to produce a manifest that is localized into more than one language or which has different language or base direction strings in it. The attributes in question are:

• appName
• shortName
• description
• (maybe??) versionName

The current design assumes all natural language related attributes share the same dir/lang configuration. We don't have yet the need of multiple localizations in the same manifest file. The manifest itself just use a default locale, while the whole MiniApp package would use multiple localizations (see https://w3c.github.io/miniapp/specs/packaging/#i18n)

[zhangyongjing]

See update in w3c/miniapp#107

[zhangyongjing]

Can close this issue now? since those attributes are inherited from WAM and marked as localizable.

[espinr]

For our reference: i18n WG work on localizable manifests

[xfq]

@espinr Just a reminder that the Developing Localizable Manifests document is mainly about localization. For language and direction metadata of strings, string-meta contains more useful information (as mentioned in the document) .

[MichaelWangzitao]

PWA Manifest provides a potential solution ( w3c/manifest#968 (comment)). It makes sense, and if it is officially accepted by the PWA, we can synchronize with it.

[xfq]

I would like to discuss this approach with the i18n WG first (hopefully today), so please wait a little bit more before adopting the web app manifest's approach.

[espinr]

Proposed PR in Web App Manifest: w3c/manifest#1101