ISSUE-414: No means of obtaining correctly localized manifest
No means of obtaining correctly localized manifest
- State:
- CLOSED
- Product:
- appmanifest
- Raised by:
- Addison Phillips
- Opened on:
- 2015-02-23
- Description:
- THREAD: https://github.com/w3c/manifest/issues/336
http://www.w3.org/TR/2015/WD-appmanifest-20150212/#obtaining
Section 6.1 discusses the steps in obtaining a manifest. There is no discussion of obtaining a correctly localized reference, particularly for use in cases where the source page itself has used language negotiation.
- Related Actions Items:
- No related actions
- Related emails:
- Weekly github digest (Review comments) (from sysbot+gh@w3.org on 2021-02-03)
- Weekly github digest (Tracker items) (from sysbot+gh@w3.org on 2021-02-03)
- Daily github digest (Review comments) (from sysbot+gh@w3.org on 2021-01-30)
- Daily github digest (WG INTERNAL review issues) (from sysbot+gh@w3.org on 2021-01-30)
- Re: [manifest] i18n: No means of obtaining correctly localized manifest; [I18N-ISSUE-414] (from sysbot+gh@w3.org on 2015-04-27)
- Closed: [manifest] i18n: No means of obtaining correctly localized manifest; [I18N-ISSUE-414] (from sysbot+gh@w3.org on 2015-04-27)
- Re: [manifest] i18n: No means of obtaining correctly localized manifest; [I18N-ISSUE-414] (from sysbot+gh@w3.org on 2015-03-25)
- [appmanifest] No means of obtaining correctly localized manifest [I18N-ISSUE-414] (from addison@lab126.com on 2015-03-19)
- I18N-ISSUE-414: No means of obtaining correctly localized manifest [appmanifest] (from sysbot+tracker@w3.org on 2015-02-23)
Related notes:
https://github.com/w3c/i18n-activity/issues/69
Richard Ishida, 17 Mar 2016, 12:53:22Display change log