Initial draft of 'developing localizable manifests' #302
Conversation
| <script class="remove"> | ||
| var respecConfig = { | ||
| specStatus: "ED", | ||
| edDraftURI: "https://w3c.github.io/i18n-drafts/techniques/developing-localizable-manifests.en.html", |
There was a problem hiding this comment.
Will this be an article or a document on /TR (like string-meta and specdev)?
There was a problem hiding this comment.
It's a good question. I used Respec with the idea that it would probably become a note, but I used the i18n-drafts repo instead of creating a new, separate, repo. The other "techniques" documents are actually indexes, so this doesn't really fit as well as I thought it might.
There was a problem hiding this comment.
This doesn't belong in the drafts/techniques directory, for sure. It should probably have its own repo, so that we can publish it as a Note in the future.
|
|
||
| <p>Some examples of specifications like this include Webapp [[APPMANIFEST]], Miniapp [[MINIAPP-MANIFEST]], and ePub [[EPUB-33]].</p> | ||
|
|
||
| <p>Manifest files generally contain a mix of <a href="https://w3c.github.io/i18n-glossary/#def_localizable_content">localizable content</a> and <a href="https://w3c.github.io/i18n-glossary/#def_syntactic_content">syntactic</a> or <a href="https://w3c.github.io/i18n-glossary/#def_user_supplied_value">user-supplied values</a> that are not localizable. A specification that defines such a format needs to provide a means for users to localize the manifest into different languages. This document covers the pros and cons of common designs, along with some best practices related to building and managing manifests.</p> |
There was a problem hiding this comment.
Would it be better to change "Manifest files generally" to something like "Some manifest files"?
For example, it seems that there is no human-readable text in Payment Method Manifest or the origin policy manifest.
There was a problem hiding this comment.
Good callout. See what you think of the updated text.
|
Do we want to add some examples of hybrid approaches? FYI - this proposal for MiniApps Manifest looks like one such example: https://pr-preview.s3.amazonaws.com/MichaelWangzitao/miniapp-manifest/pull/12.html#i18n-solution-i18n |
- Added a hybrid example - Changed wording about mixed localizable/non-localizable content - Added temporary reference to i18n-glossary - Fixed small typos (missing commas in examples, a few stray quotes from pasting from Word)
|
BTW, we can use |
- added class=json to examples - changed path location
to exclamation mark emoji.
[I18N-ACTION-1033]