chrome/common/extensions/docs/templates/intros/i18n.html - Issue 12996003: Dynamically generate a heading for Extension Docs API pages

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: chrome/common/extensions/docs/templates/intros/i18n.html

Issue 12996003: Dynamically generate a heading for Extension Docs API pages (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Addressing comments - Patch currently being broken up Created 7 years, 6 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

« no previous file with comments | « chrome/common/extensions/docs/templates/intros/history.html ('k') | chrome/common/extensions/docs/templates/intros/idle.html » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: chrome/common/extensions/docs/templates/intros/i18n.html

diff --git a/chrome/common/extensions/docs/templates/intros/i18n.html b/chrome/common/extensions/docs/templates/intros/i18n.html

index 6be494ca28796f23e450be712566e96bd7c963fe..92a90b07bfd15345f7b547e07630ed9ea5d4f051 100644

--- a/chrome/common/extensions/docs/templates/intros/i18n.html

+++ b/chrome/common/extensions/docs/templates/intros/i18n.html

@@ -3,15 +3,6 @@

* Try to be consistent about string vs. message (it's probably not yet).

-->

-

-An internationalized extension or app

-can be easily

-localized —

-adapted to languages and regions

-that it didn't originally support.

-

You need to put all of its user-visible strings into a file

named <a href="i18n-messages.html"><code>messages.json</code></a>.

@@ -567,4 +558,4 @@ function getAcceptLanguages() {

For details on calling <code>getAcceptLanguages()</code>, see the

$ref:[i18n.getAcceptLanguages API reference].

-

+