Closed
Bug 838176
Opened 13 years ago
Closed 10 years ago
Decide on link/script types for l20n
Categories
(L20n :: HTML Bindings, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Next
People
(Reporter: zbraniecki, Unassigned)
References
()
Details
(Keywords: APIchange)
We need type and rel for the following four <head> elements:
- manifest link
- context data script
- resource link
- resource script
|
Reporter | |
Comment 1•13 years ago
|
||
manifest link:
- type: application/json
- rel: l10n-manifest
context data script:
- type: ?
resource link:
- type: application/l20n
- rel: l10n-resource
resource script:
- type: application/l20n
|
|
Reporter | |
Comment 2•13 years ago
|
||
1) <link rel="l10n-manifest" type="application/json" src="./locales/manifest.json" />
2)
<script type="">
{
"unreadEmails": 5,
"user": {
"name": "John",
"gender": "male"
}
}
</script>
3)
<link rel="l10n-resource" type="application/l20n" src="l10n:settings" />
4)
<script type="application/l20n">
<myButton "Button">
<warning "Warning!">
</script>
|
|
Reporter | |
Comment 3•13 years ago
|
||
1) <link rel="l10n-manifest" type="application/json" href="./locales/manifest.json" />
DONE
2)
<x-resource rel="l10n-data" type="application/json">
{
"unreadEmails": 5,
"user": {
"name": "John",
"gender": "male"
}
}
</x-resource>
3)
<x-resource rel="l10n" type="application/l20n" src="l10n:./locales/{{locale}}/settings.l20n">
4)
<x-resource rel="l10n" type="application/l20n">
<myButton "Button">
<warning "Warning!">
</x-resource>
|
||
Updated•13 years ago
|
|
|
||
Updated•13 years ago
|
|
|
||
Updated•13 years ago
|
Priority: P1 → --
Target Milestone: 1.0 beta → Next
|
|
||
Comment 4•13 years ago
|
||
I'll keep this bug open but keep in mind that 1) it's not targeting 1.0, 2) the 1.0 work is happening in bug 846179.
|
|
Reporter | |
Updated•13 years ago
|
Flags: blocking-parkcity+
|
|
||
Updated•11 years ago
|
Assignee: stas → nobody
|
|
Reporter | |
Comment 5•10 years ago
|
||
We settled on not using manifests, and use:
<meta name="defaultLanguage" content="en-US">
<meta name="availableLanguages" content="en-US, fr">
<link rel="localization" href="locales/example.{locale}.l20n">
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•