- From: Addison Phillips <notifications@github.com>
- Date: Mon, 15 May 2023 00:04:19 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/manifest/issues/1080@github.com>
`dir` member https://w3c.github.io/manifest/#dir-member > The localizable members are: > > [name](https://w3c.github.io/manifest/#dfn-name) member. > [short_name](https://w3c.github.io/manifest/#dfn-short_name) member. > [Shortcut item's](https://w3c.github.io/manifest/#dfn-shortcut-item) [name](https://w3c.github.io/manifest/#dfn-name-0) member. > [Shortcut item's](https://w3c.github.io/manifest/#dfn-shortcut-item) [short_name](https://w3c.github.io/manifest/#dfn-short_name-0) member. > [Shortcut item's](https://w3c.github.io/manifest/#dfn-shortcut-item) [description](https://w3c.github.io/manifest/#dfn-description) member. This is more of an editorial comment than it is a technical objection. The section about the `dir` member defines the term "localizable member" and includes the above definition of which fields are localizable. It seems like "localizable" should be defined separately so that it can be referred to by various members and sub-members as appropriate and so that the list of items belonging to it doesn't inadvertently become stale. Note that "localization" encompasses more than just translation of strings. It can and often does include changing other items found in a manifest, such as icons, colors, and such. The textual items are important, of course, and are related to direction and language metadata more directly than (say) an icon, but this shouldn't be overlooked. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/1080 You are receiving this because you are subscribed to this thread. Message ID: <w3c/manifest/issues/1080@github.com>
Received on Monday, 15 May 2023 07:04:25 UTC