|
1 #summary The reference to the wiki syntax for Google Code projects |
|
2 #labels Restrict-AddWikiComment-Commit |
|
3 = Wiki Syntax = |
|
4 <wiki:toc max_depth="2" /> |
|
5 |
|
6 = Introduction = |
|
7 |
|
8 Each wiki page is stored in a .wiki file under the /wiki directory in |
|
9 a project's repository. Each file's name is the same as the wiki page |
|
10 name. And, each wiki file consists of optional pragma lines followed |
|
11 by the content of the page. |
|
12 |
|
13 = Pragmas = |
|
14 |
|
15 Optional pragma lines provide metadata about the page and how it should be |
|
16 displayed. These lines are only processed if they appear at the top of |
|
17 the file. Each pragma line begins with a pound-sign (#) and the |
|
18 pragma name, followed by a value. |
|
19 |
|
20 || *Pragma* || *Value* || |
|
21 || #summary || One-line summary of the page || |
|
22 || #labels || Comma-separated list of labels (filled in automatically via the web UI) || |
|
23 || #sidebar || See [http://code.google.com/p/support/wiki/WikiSyntax#Side_navigation Side navigation] || |
|
24 |
|
25 = Wiki-style markup = |
|
26 |
|
27 == Paragraphs == |
|
28 |
|
29 Use one or more blank lines to separate paragraphs. |
|
30 |
|
31 == Typeface == |
|
32 |
|
33 ||* Name/Sample* || * Markup * || |
|
34 || _italic_ || `_italic_` || |
|
35 || *bold* || `*bold*` || |
|
36 || `code` || {{{`code`}}} || |
|
37 || {{{code}}} || `{{{code}}}` || |
|
38 || ^super^script || `^super^script` || |
|
39 || ,,sub,,script || `,,sub,,script` || |
|
40 || ~~strikeout~~ || `~~strikeout~~` || |
|
41 |
|
42 You can mix these typefaces in some ways: |
|
43 |
|
44 || *Markup* || *Result* || |
|
45 || `_*bold* in italics_` || _*bold* in italics_ || |
|
46 || `*_italics_ in bold*` || *_italics_ in bold* || |
|
47 || `*~~strike~~ works too*` || *~~strike~~ works too* || |
|
48 || `~~as well as _this_ way round~~` || ~~as well as _this_ way round~~ || |
|
49 |
|
50 == Code == |
|
51 |
|
52 If you have a multiline code block that you want to display verbatim, |
|
53 use the multiline code delimiter: |
|
54 |
|
55 {{{ |
|
56 {{{ |
|
57 def fib(n): |
|
58 if n == 0 or n == 1: |
|
59 return n |
|
60 else: |
|
61 # This recursion is not good for large numbers. |
|
62 return fib(n-1) + fib(n-2) |
|
63 }}} |
|
64 }}} |
|
65 |
|
66 Which results in: |
|
67 |
|
68 {{{ |
|
69 def fib(n): |
|
70 if n == 0 or n == 1: |
|
71 return n |
|
72 else: |
|
73 # This recursion is not good for large numbers. |
|
74 return fib(n-1) + fib(n-2) |
|
75 }}} |
|
76 |
|
77 For more control over the syntax higlighting, the `<code>` tag allows you to specify a file extension: |
|
78 |
|
79 {{{ |
|
80 <code language="xml"> |
|
81 <hello target="world"/> |
|
82 </code> |
|
83 }}} |
|
84 |
|
85 To disable highlighting entirely, use the `<pre>` tag. |
|
86 |
|
87 == Headings == |
|
88 |
|
89 {{{ |
|
90 = Heading = |
|
91 == Subheading == |
|
92 === Level 3 === |
|
93 ==== Level 4 ==== |
|
94 ===== Level 5 ===== |
|
95 ====== Level 6 ====== |
|
96 }}} |
|
97 |
|
98 == Dividers == |
|
99 |
|
100 Four or more dashes on a line by themselves results in a horizontal rule. |
|
101 |
|
102 |
|
103 == Lists == |
|
104 |
|
105 Google Code wikis support both bulleted and numbered lists. A list |
|
106 must be indented at least one space to be recognized as such. You can |
|
107 also nest lists one within the other by appropriate use of indenting: |
|
108 |
|
109 {{{ |
|
110 The following is: |
|
111 * A list |
|
112 * Of bulleted items |
|
113 # This is a numbered sublist |
|
114 # Which is done by indenting further |
|
115 * And back to the main bulleted list |
|
116 |
|
117 * This is also a list |
|
118 * With a single leading space |
|
119 * Notice that it is rendered |
|
120 # At the same levels |
|
121 # As the above lists. |
|
122 * Despite the different indentation levels. |
|
123 }}} |
|
124 |
|
125 The following is: |
|
126 * A list |
|
127 * Of bulleted items |
|
128 # This is a numbered sublist |
|
129 # Which is done by indenting further |
|
130 * And back to the main bulleted list |
|
131 |
|
132 * This is also a list |
|
133 * With a single leading space |
|
134 * Notice that it is rendered |
|
135 # At the same levels |
|
136 # As the above lists. |
|
137 * Despite the different indentation levels. |
|
138 |
|
139 == Quoting == |
|
140 |
|
141 Block quotes place emphasis on a particular extract of text in your |
|
142 page. Block quotes are created by indenting a paragraph by at least |
|
143 one space: |
|
144 |
|
145 {{{ |
|
146 Someone once said: |
|
147 |
|
148 This sentence will be quoted in the future as the canonical example |
|
149 of a quote that is so important that it should be visually separate |
|
150 from the rest of the text in which it appears. |
|
151 }}} |
|
152 |
|
153 Someone once said: |
|
154 |
|
155 This sentence will be quoted in the future as the canonical example |
|
156 of a quote that is so important that it should be visually separate |
|
157 from the rest of the text in which it appears. |
|
158 |
|
159 == Links == |
|
160 |
|
161 Links are central to the wiki principle, as they create the web of |
|
162 content. Google Code wiki permits both internal (within the wiki) and |
|
163 external links, and in some cases automatically creates a link when it |
|
164 recognizes either a !WikiWord or an URL. |
|
165 |
|
166 === Internal wiki links === |
|
167 |
|
168 Internal links within a wiki are created using the syntax below. If |
|
169 you add a wiki link to a page that does not exist, the link will |
|
170 appear with a !LittleLink[WikiSyntax ?] to project committers and |
|
171 owners. Clicking that link will take you to the page creation form |
|
172 where you can enter content for that page. |
|
173 |
|
174 If you are not logged in, wiki links that point to non-existent pages |
|
175 will appear as plain text, without the link to the page creation |
|
176 form. When you create the target page, |
|
177 the link will become a normal hyperlink for all viewers of |
|
178 the page. |
|
179 |
|
180 {{{ |
|
181 WikiSyntax is identified and linked automatically |
|
182 |
|
183 Wikipage is not identified, so if you have a page named [Wikipage] you |
|
184 need to link it explicitly. |
|
185 |
|
186 If the WikiSyntax page is actually about reindeers, you can provide a |
|
187 description, so that people know you are actually linking to a page on |
|
188 [WikiSyntax reindeer flotillas]. |
|
189 |
|
190 If you want to mention !WikiSyntax without it being autolinked, use an |
|
191 exclamation mark to prevent linking. |
|
192 }}} |
|
193 |
|
194 WikiSyntax is identified and linked automatically |
|
195 |
|
196 Wikipage is not identified, so if you have a page named [Wikipage] you |
|
197 need to link it explicitly. |
|
198 |
|
199 If the WikiSyntax page is actually about reindeers, you can provide a |
|
200 description, so that people know you are actually linking to a page on |
|
201 [WikiSyntax reindeer flotillas]. |
|
202 |
|
203 If you want to mention !WikiSyntax without it being autolinked, use an |
|
204 exclamation mark to prevent linking. |
|
205 |
|
206 === Links to anchors within a page === |
|
207 |
|
208 Each heading defines a HTML anchor with the same name as the heading, but with spaces replaced by underscores. You can |
|
209 create a link to a specific heading on a page like this: |
|
210 |
|
211 {{{ |
|
212 [WikiSyntax#Wiki-style_markup] |
|
213 }}} |
|
214 |
|
215 And it will render as: [WikiSyntax#Wiki-style_markup]. |
|
216 |
|
217 === Links to issues and revisions === |
|
218 |
|
219 You can easily link to issues and revisions using the following syntax. |
|
220 |
|
221 * `issue 123` will be autolinked to issue number 123 in the current project. You can include a `#` or not. If the issue has been closed, the link will appear as a cross-out rather than an underline. Hovering your mouse over such a link shows the issue summary. |
|
222 |
|
223 * `issue PROJECTNAME:122` will be autolinked to that issue number in the specified project. This is useful when your project depends on work being done in related projects. |
|
224 |
|
225 * `r123` will be autolinked to the revision detail page for that revision in the current project. |
|
226 |
|
227 There is currently no way to disable this type of autolinking. See issue 996. |
|
228 |
|
229 {{{ |
|
230 For example: Please add a comment on issue 123 rather than adding more review comments to r456. |
|
231 }}} |
|
232 |
|
233 Renders as: Please add a comment on issue 123 rather than adding more review comments to r456. |
|
234 |
|
235 |
|
236 === Links to external pages === |
|
237 |
|
238 You can of course link to external pages from your own wiki pages, |
|
239 using a syntax similar to that for internal links: |
|
240 |
|
241 {{{ |
|
242 Plain URLs such as http://www.google.com/ or ftp://ftp.kernel.org/ are |
|
243 automatically made into links. |
|
244 |
|
245 You can also provide some descriptive text. For example, the following |
|
246 link points to the [http://www.google.com Google home page]. |
|
247 |
|
248 If your link points to an image, it will get inserted as an image tag |
|
249 into the page: |
|
250 |
|
251 http://code.google.com/images/code_sm.png |
|
252 |
|
253 You can also make the image into a link, by setting the image URL as |
|
254 the description of the URL you want to link: |
|
255 |
|
256 [http://code.google.com/ http://code.google.com/images/code_sm.png] |
|
257 }}} |
|
258 |
|
259 Plain URLs such as http://www.google.com/ or ftp://ftp.kernel.org/ are |
|
260 automatically made into links. |
|
261 |
|
262 You can also provide some descriptive text. For example, the following |
|
263 link points to the [http://www.google.com Google home page]. |
|
264 |
|
265 You can also make the image into a link, by setting the image URL as |
|
266 the description of the URL you want to link: |
|
267 |
|
268 {{{ |
|
269 [http://code.google.com/ http://code.google.com/images/code_sm.png] |
|
270 }}} |
|
271 |
|
272 [http://code.google.com/ http://code.google.com/images/code_sm.png] |
|
273 |
|
274 |
|
275 === Links to images === |
|
276 |
|
277 If your link points to an image (that is, if it ends in `.png`, |
|
278 `.gif`, `.jpg` or `.jpeg`), it will get inserted as an image into the |
|
279 page: |
|
280 |
|
281 {{{ |
|
282 http://code.google.com/images/code_sm.png |
|
283 }}} |
|
284 |
|
285 http://code.google.com/images/code_sm.png |
|
286 |
|
287 If the image is produced by a server-side script, you may need to add a nonsense query string parameter to the end so that the URL ends with a supported image filename extension. |
|
288 |
|
289 {{{ |
|
290 http://chart.apis.google.com/chart?chs=200x125&chd=t:48.14,33.79,19.77|83.18,18.73,12.04&cht=bvg&nonsense=something_that_ends_with.png |
|
291 }}} |
|
292 |
|
293 http://chart.apis.google.com/chart?chs=200x125&chd=t:48.14,33.79,19.77|83.18,18.73,12.04&cht=bvg&nonsense=something_that_ends_with.png |
|
294 |
|
295 == Tables == |
|
296 |
|
297 Tables are created by entering the content of each cell separated by |
|
298 {{{||}}} delimiters. You can insert other inline wiki syntax in table |
|
299 cells, including typeface formatting and links. |
|
300 |
|
301 {{{ |
|
302 || *Year* || *Temperature (low)* || *Temperature (high)* || |
|
303 || 1900 || -10 || 25 || |
|
304 || 1910 || -15 || 30 || |
|
305 || 1920 || -10 || 32 || |
|
306 || 1930 || _N/A_ || _N/A_ || |
|
307 || 1940 || -2 || 40 || |
|
308 }}} |
|
309 |
|
310 || *Year* || *Temperature (low)* || *Temperature (high)* || |
|
311 || 1900 || -10 || 25 || |
|
312 || 1910 || -15 || 30 || |
|
313 || 1920 || -10 || 32 || |
|
314 || 1930 || _N/A_ || _N/A_ || |
|
315 || 1940 || -2 || 40 || |
|
316 |
|
317 |
|
318 |
|
319 |
|
320 |
|
321 |
|
322 |
|
323 |
|
324 = HTML support = |
|
325 To aid in the presentation of a wiki page there is some support for HTML. HTML tags are only supported in wiki pages, not in page comments. |
|
326 |
|
327 HTML syntax can be used in conjunction with wiki syntax, but it is recommended against doing so where possible.<wiki:comment>Also, avoid blank lines between list items.</wiki:comment> |
|
328 |
|
329 The following HTML tags and attributes are currently supported: |
|
330 |
|
331 <table border=1> |
|
332 <thead><th>HTML Tag</th><th>Supported Attributes</th></thead> |
|
333 <tbody> |
|
334 <tr><td>a</td><td>title dir lang href</td></tr> |
|
335 <tr><td>b</td><td>title dir lang</td></tr> |
|
336 <tr><td>br</td><td>title dir lang</td></tr> |
|
337 <tr><td>blockquote</td><td>title dir lang</td></tr> |
|
338 <tr><td>code</td><td>title dir lang language `[1]`</td></tr> |
|
339 <tr><td>dd</td><td>title dir lang</td></tr> |
|
340 <tr><td>div</td><td>title dir lang</td></tr> |
|
341 <tr><td>dl</td><td>title dir lang</td></tr> |
|
342 <tr><td>dt</td><td>title dir lang</td></tr> |
|
343 <tr><td>em</td><td>title dir lang</td></tr> |
|
344 <tr><td>font</td><td>title dir lang face size color</td></tr> |
|
345 <tr><td>h1</td><td>title dir lang</td></tr> |
|
346 <tr><td>h2</td><td>title dir lang</td></tr> |
|
347 <tr><td>h3</td><td>title dir lang</td></tr> |
|
348 <tr><td>h4</td><td>title dir lang</td></tr> |
|
349 <tr><td>h5</td><td>title dir lang</td></tr> |
|
350 <tr><td>i</td><td>title dir lang</td></tr> |
|
351 <tr><td>img</td><td>title dir lang src alt border height width align</td></tr> |
|
352 <tr><td>li</td><td>title dir lang</td></tr> |
|
353 <tr><td>ol</td><td>title dir lang type start</td></tr> |
|
354 <tr><td>p</td><td>title dir lang align</td></tr> |
|
355 <tr><td>pre</td><td>title dir lang</td></tr> |
|
356 <tr><td>q</td><td>title dir lang</td></tr> |
|
357 <tr><td>s</td><td>title dir lang</td></tr> |
|
358 <tr><td>span</td><td>title dir lang</td></tr> <tr><td>strike</td><td>title dir lang</td></tr> <tr><td>strong</td><td>title dir lang</td></tr> |
|
359 <tr><td>sub</td><td>title dir lang</td></tr> |
|
360 <tr><td>sup</td><td>title dir lang</td></tr> |
|
361 <tr><td>table</td><td>title dir lang align valign cellspacing cellpadding border width height</td></tr> |
|
362 <tr><td>tbody</td><td>title dir lang align valign cellspacing cellpadding border width height</td></tr> |
|
363 <tr><td>td</td><td>title dir lang align valign cellspacing cellpadding border width height</td></tr> |
|
364 <tr><td>tfoot</td><td>title dir lang align valign cellspacing cellpadding border width height</td></tr> |
|
365 <tr><td>th</td><td>title dir lang align valign cellspacing cellpadding border width height</td></tr> |
|
366 <tr><td>thead</td><td>title dir lang align valign cellspacing cellpadding border width height colspan rowspan</td></tr> |
|
367 <tr><td>tr</td><td>title dir lang align valign cellspacing cellpadding border width height colspan rowspan</td></tr> |
|
368 <tr><td>tt</td><td>title dir lang</td></tr> |
|
369 <tr><td>u</td><td>title dir lang</td></tr> |
|
370 <tr><td>ul</td><td>title dir lang type</td></tr> |
|
371 <tr><td>var</td><td>title dir lang</td></tr> </tbody> |
|
372 </table> |
|
373 |
|
374 `[1]` The language attribute of the code tag is the file extension of the language used in the code block. It is used as a hint for the syntax highlighter. |
|
375 |
|
376 == Escaping HTML Tags == |
|
377 |
|
378 When you want to display html tags directly on your wiki page (as opposed to rendered), you will need to escape each HTML tag. |
|
379 |
|
380 HTML tags can be escaped as shown in the table below: |
|
381 <table border="1"> |
|
382 <thead><th>Markup</th><th>Result</th></thead> |
|
383 <tbody> |
|
384 <tr><td> {{{`<hr>`}}}</td><td>`<hr>`</td></tr> |
|
385 <tr><td> `{{{<hr>}}}`</td><td>{{{<hr>}}}</td></tr> |
|
386 </tbody> |
|
387 </table> |
|
388 |
|
389 <br/> |
|
390 |
|
391 = Comments = |
|
392 |
|
393 The wiki supports embedded comments to help explain the contents of a wiki page. Anything inside the comment block is removed from the rendered page, but is visible when editing or viewing the source for that page. |
|
394 |
|
395 {{{ |
|
396 <wiki:comment> |
|
397 This text will be removed from the rendered page. |
|
398 </wiki:comment> |
|
399 }}} |
|
400 |
|
401 = +1 Button = |
|
402 |
|
403 Use `<g:plusone></g:plusone>` to add a [http://www.google.com/+1/button/ +1 button] to the page. Example: |
|
404 |
|
405 {{{ |
|
406 <g:plusone size="medium"></g:plusone> |
|
407 }}} |
|
408 |
|
409 <g:plusone size="medium"></g:plusone> |
|
410 |
|
411 The count, size, and href parameters are supported; see http://code.google.com/apis/+1button/ for documentation. |
|
412 |
|
413 = Gadgets = |
|
414 |
|
415 You can embed [http://www.google.com/ig/directory?synd=open Gadgets] on your wiki pages with the following syntax: |
|
416 |
|
417 {{{ |
|
418 <wiki:gadget url="http://example.com/gadget.xml" height="200" border="0" /> |
|
419 }}} |
|
420 |
|
421 Valid attributes are: |
|
422 * `url`: the URL of the gadget |
|
423 * `width`: the width of the gadget |
|
424 * `height`: the height of the gadget |
|
425 * `title`: a title to display above the gadget |
|
426 * `border`: "0" or "1", whether to draw a border around the gadget |
|
427 * `up_*`: Gadget user preference parameters |
|
428 * `caja`: "0" or "1", whether to use Caja to render the gadget. [http://code.google.com/p/google-caja Caja] helps protect users from malicious or accidental errors in third party gadgets. |
|
429 |
|
430 WorkingWithGoogleGadgets describes how to create gadgets for Google Code. It also provides a few helpful suggestions that can make it easier to publish gadgets and to integrate with other Google products such as iGoogle. |
|
431 |
|
432 InterestingDeveloperGadgets shows some sample gadgets you may want to include on your project pages. |
|
433 |
|
434 = Videos = |
|
435 |
|
436 You can embed videos with the following syntax: |
|
437 |
|
438 {{{ |
|
439 <wiki:video url="http://www.youtube.com/watch?v=3LkNlTNHZzE"/> |
|
440 }}} |
|
441 |
|
442 Valid attributes are: |
|
443 * `url`: the URL of the video |
|
444 * `width`: the width of the embedded video |
|
445 * `height`: the height of the embedded video |
|
446 |
|
447 Right now we support videos from YouTube,. Other video sites may be embeddable via a gadget, as described above. |
|
448 |
|
449 = Navigation = |
|
450 == Table of Contents == |
|
451 |
|
452 An inline table of contents can be generated from page headers on a wiki page. Add the following syntax to a page in the location the table of contents should be displayed: |
|
453 |
|
454 {{{ |
|
455 <wiki:toc max_depth="1" /> |
|
456 }}} |
|
457 |
|
458 Valid attributes are: |
|
459 * `max_depth`: the maximum header depth to display in the table of contents |
|
460 |
|
461 == Side navigation == |
|
462 |
|
463 You can specify the sidebar for a wiki page by selecting another wiki page that defines your side navigation. The [http://code.google.com/p/guava-libraries/wiki/GuavaExplained?tm=6 Guava project] uses the sidebar extensively across its wiki. |
|
464 |
|
465 One way of adding a sidebar is by setting the #sidebar pragma, as shown below. Alternatively, the sidebar pragma can be left blank if no side navigation is desired. |
|
466 |
|
467 || #sidebar !TableOfContents || |
|
468 |
|
469 The side navigation that is defined should be in the format of a simple list, as shown below. |
|
470 |
|
471 {{{ |
|
472 * [Articles HOWTO articles] |
|
473 * [ArticlesXSS Web security] |
|
474 * [ArticlesDom DOM manipulation] |
|
475 * [ArticlesStyle CSS and style] |
|
476 * [ArticlesTips Tips and tricks] |
|
477 * [DOMReference DOM reference] |
|
478 * [HTMLElements HTML reference] |
|
479 * [CSSReference CSS reference] |
|
480 }}} |
|
481 |
|
482 A default sidebar page can also be specified for all wiki pages by project owners through the Wiki settings in the Administer tab. If a #sidebar pragma is also specified, it will take precedence on the page. |
|
483 |
|
484 = Localizing Wiki Content = |
|
485 |
|
486 Along with the default language for the wiki, which can be set through the Wiki settings in the Administer tab, additional languages are also supported. If more than one language is available, based on a user's language preference (e.g. browser language), the wiki will try to serve the page for the appropriate language. If no wiki page exists for that language, it will fall back to the default language. Comments, however, are shared amongst all translations of a wiki page. |
|
487 |
|
488 New translations for a page cannot be added through the web interface and have to be added through the Subversion repository. |
|
489 |
|
490 To add a translation of a page, first checkout the wiki from Subversion: <br/> |
|
491 `svn checkout https://`<b>yourproject</b>`.googlecode.com/svn/wiki/` <b>yourdirectory</b> `-username` <b>yourusername</b> |
|
492 |
|
493 Then create a new directory under /wiki/ using the two letter ISO-639 code as the name of that directory. Place all translated files in the new directory and submit those changes to the Subversion repository. |
|
494 |
|
495 The following is an example of a valid wiki directory: |
|
496 {{{ |
|
497 wiki/ |
|
498 ja/ |
|
499 ProjectHistory.wiki |
|
500 StyleGuide.wiki |
|
501 zh-Hans/ |
|
502 ProjectHistory.wiki |
|
503 StyleGuide.wiki |
|
504 zh-Hant/ |
|
505 ProjectHistory.wiki |
|
506 StyleGuide.wiki |
|
507 ProjectHistory.wiki |
|
508 StyleGuide.wiki |
|
509 }}} |
|
510 |
|
511 Once the files have been submitted to the project's subversion repository, they can now be edited through the wiki's web editor. The process is the same for Mercurial or Git projects, except that the wiki lives in the root directory (not wiki/) of `https://wiki.`<b>yourproject</b>`.googlecode.com/hg/` or `https://wiki.`<b>yourproject</b>`.googlecode.com/git/`. |
|
512 |
|
513 Note: The wiki accepts a subset of ISO-639 two letter language codes, where a few of the codes (such as zh_Hans) contain locale-specific codes. Such locale-specific codes should use a hyphen (zh-Hans) separator. A few example language codes have been specified in the table below. |
|
514 |
|
515 <table border=1> |
|
516 <tbody><tr> |
|
517 <th style="padding: 4px 4px 4px 8px;" scope="col"> Language (Locale)</th> |
|
518 <th style="padding: 4px 4px 4px 8px;" scope="col"> Directory Name |
|
519 </th> |
|
520 </tr> |
|
521 <tr> |
|
522 <td>Arabic</td> |
|
523 <td>ar</td> |
|
524 </tr> |
|
525 <tr> |
|
526 <td>Bulgarian</td> |
|
527 <td>bg</td> |
|
528 </tr> |
|
529 <tr> |
|
530 <td>Chinese (China)</td> |
|
531 <td>zh-Hans</td> |
|
532 </tr> |
|
533 <tr> |
|
534 <td>Chinese (Taiwan)</td> |
|
535 <td>zh-Hant</td> |
|
536 </tr> |
|
537 <tr> |
|
538 <td>Croatian</td> |
|
539 <td>hr</td> |
|
540 </tr> |
|
541 <tr> |
|
542 <td>Czech</td> |
|
543 <td>cs</td> |
|
544 </tr> |
|
545 <tr> |
|
546 <td>Danish</td> |
|
547 <td>da</td> |
|
548 </tr> |
|
549 <tr> |
|
550 <td>Dutch</td> |
|
551 <td>nl</td> |
|
552 </tr> |
|
553 <tr> |
|
554 <td>English (United Kingdom)</td> |
|
555 <td>en-GB</td> |
|
556 </tr> |
|
557 <tr> |
|
558 <td>English (United States)</td> |
|
559 <td>en-US</td> |
|
560 </tr> |
|
561 <tr> |
|
562 <td>Finnish</td> |
|
563 <td>fi</td> |
|
564 </tr> |
|
565 <tr> |
|
566 <td>French</td> |
|
567 <td>fr</td> |
|
568 </tr> |
|
569 <tr> |
|
570 <td>German</td> |
|
571 <td>de</td> |
|
572 </tr> |
|
573 <tr> |
|
574 <td>Greek</td> |
|
575 <td>el</td> |
|
576 </tr> |
|
577 <tr> |
|
578 <td>Hebrew</td> |
|
579 <td>he</td> |
|
580 </tr> |
|
581 <tr> |
|
582 <td>Hungarian</td> |
|
583 <td>hu</td> |
|
584 </tr> |
|
585 <tr> |
|
586 <td>Italian</td> |
|
587 <td>it</td> |
|
588 </tr> |
|
589 <tr> |
|
590 <td>Japanese</td> |
|
591 <td>ja</td> |
|
592 </tr> |
|
593 <tr> |
|
594 <td>Korean</td> |
|
595 <td>ko</td> |
|
596 </tr> |
|
597 <tr> |
|
598 <td>Norwegian</td> |
|
599 <td>no</td> |
|
600 </tr> |
|
601 <tr> |
|
602 <td>Polish</td> |
|
603 <td>pl</td> |
|
604 </tr> |
|
605 <tr> |
|
606 <td>Portuguese (Brazil)</td> |
|
607 <td>pt-BR</td> |
|
608 </tr> |
|
609 <tr> |
|
610 <td>Romanian</td> |
|
611 <td>ro</td> |
|
612 </tr> |
|
613 <tr> |
|
614 <td>Russian</td> |
|
615 <td>ru</td> |
|
616 </tr> |
|
617 <tr> |
|
618 <td>Slovak</td> |
|
619 <td>sk</td> |
|
620 </tr> |
|
621 <tr> |
|
622 <td>Spanish</td> |
|
623 <td>es</td> |
|
624 </tr> |
|
625 <tr> |
|
626 <td>Swedish</td> |
|
627 <td>sv</td> |
|
628 </tr> |
|
629 <tr> |
|
630 <td>Turkish</td> |
|
631 <td>tr</td> |
|
632 </tr> |
|
633 </tbody></table> |
|
634 |
|
635 _The content on this page created by Google is licensed under the [http://creativecommons.org/licenses/by/3.0/ Creative Commons Attribution 3.0 License]. User-generated content is not included in this license._ |