# HG changeset patch # User Wuzzy # Date 1531450819 -3600 # Node ID b5bd32ab09ed33f2caa9bd704167d34450bd3041 # Parent d25ab95f2311768ab20dccdc12d2dd9d85c281e9 WikiSyntax: Rebranding, remove Google stuff diff -r d25ab95f2311 -r b5bd32ab09ed WikiSyntax.wiki --- a/WikiSyntax.wiki Wed Jul 11 13:39:34 2018 +0100 +++ b/WikiSyntax.wiki Fri Jul 13 04:00:19 2018 +0100 @@ -1,4 +1,4 @@ -#summary The reference to the wiki syntax for Google Code projects +#summary The reference to the wiki syntax for the Hedgewars Knowledge Base #labels Restrict-AddWikiComment-Commit = Wiki Syntax = @@ -20,7 +20,6 @@ || *Pragma* || *Value* || || #summary || One-line summary of the page || || #labels || Comma-separated list of labels (filled in automatically via the web UI) || -|| #sidebar || See [http://code.google.com/p/support/wiki/WikiSyntax#Side_navigation Side navigation] || = Wiki-style markup = @@ -102,7 +101,7 @@ == Lists == -Google Code wikis support both bulleted and numbered lists. A list +The HWKB wiki supports both bulleted and numbered lists. A list must be indented at least one space to be recognized as such. You can also nest lists one within the other by appropriate use of indenting: @@ -159,7 +158,7 @@ == Links == Links are central to the wiki principle, as they create the web of -content. Google Code wiki permits both internal (within the wiki) and +content. The HWKB wiki permits both internal (within the wiki) and external links, and in some cases automatically creates a link when it recognizes either a !WikiWord or an URL. @@ -239,38 +238,40 @@ using a syntax similar to that for internal links: {{{ -Plain URLs such as http://www.google.com/ or ftp://ftp.kernel.org/ are -automatically made into links. +Plain URLs such as https://www.example.org/ automatically made into links. You can also provide some descriptive text. For example, the following -link points to the [http://www.google.com Google home page]. +link points to the [https://www.example.org Example homepage]. If your link points to an image, it will get inserted as an image tag into the page: -http://code.google.com/images/code_sm.png +https://www.hedgewars.org/images/Static_Hat_Template.png You can also make the image into a link, by setting the image URL as the description of the URL you want to link: -[http://code.google.com/ http://code.google.com/images/code_sm.png] +[https://www.hedgewars.org/ https://www.hedgewars.org/images/Static_Hat_Template.png] }}} -Plain URLs such as http://www.google.com/ or ftp://ftp.kernel.org/ are -automatically made into links. +Plain URLs such as https://www.example.org/ automatically made into links. You can also provide some descriptive text. For example, the following -link points to the [http://www.google.com Google home page]. +link points to the [https://www.example.org Example homepage]. + +If your link points to an image, it will get inserted as an image tag +into the page: + +https://www.hedgewars.org/images/Static_Hat_Template.png You can also make the image into a link, by setting the image URL as the description of the URL you want to link: {{{ -[http://code.google.com/ http://code.google.com/images/code_sm.png] +[https://www.hedgewars.org/ https://www.hedgewars.org/images/Static_Hat_Template.png] }}} -[http://code.google.com/ http://code.google.com/images/code_sm.png] - +[https://www.hedgewars.org/ https://www.hedgewars.org/images/Static_Hat_Template.png] === Links to images === @@ -279,10 +280,10 @@ page: {{{ -http://code.google.com/images/code_sm.png +https://www.hedgewars.org/images/Static_Hat_Template.png }}} -http://code.google.com/images/code_sm.png +https://www.hedgewars.org/images/Static_Hat_Template.png 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. @@ -398,53 +399,6 @@ }}} -= +1 Button = - -Use `` to add a [http://www.google.com/+1/button/ +1 button] to the page. Example: - -{{{ - -}}} - - - -The count, size, and href parameters are supported; see http://code.google.com/apis/+1button/ for documentation. - -= Gadgets = - -You can embed [http://www.google.com/ig/directory?synd=open Gadgets] on your wiki pages with the following syntax: - -{{{ - -}}} - -Valid attributes are: - * `url`: the URL of the gadget - * `width`: the width of the gadget - * `height`: the height of the gadget - * `title`: a title to display above the gadget - * `border`: "0" or "1", whether to draw a border around the gadget - * `up_*`: Gadget user preference parameters - * `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. - -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. - -InterestingDeveloperGadgets shows some sample gadgets you may want to include on your project pages. - -= Videos = - -You can embed videos with the following syntax: - -{{{ - -}}} - -Valid attributes are: - * `url`: the URL of the video - * `width`: the width of the embedded video - * `height`: the height of the embedded video - -Right now we support videos from YouTube,. Other video sites may be embeddable via a gadget, as described above. = Navigation = == Table of Contents == @@ -460,7 +414,7 @@ == Side navigation == -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. +You can specify the sidebar for a wiki page by selecting another wiki page that defines your side navigation. 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. @@ -479,157 +433,6 @@ * [CSSReference CSS reference] }}} -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. - -= Localizing Wiki Content = - -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. - -New translations for a page cannot be added through the web interface and have to be added through the Subversion repository. - -To add a translation of a page, first checkout the wiki from Subversion:
-`svn checkout https://`yourproject`.googlecode.com/svn/wiki/` yourdirectory `-username` yourusername - -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. - -The following is an example of a valid wiki directory: -{{{ -wiki/ - ja/ - ProjectHistory.wiki - StyleGuide.wiki - zh-Hans/ - ProjectHistory.wiki - StyleGuide.wiki - zh-Hant/ - ProjectHistory.wiki - StyleGuide.wiki - ProjectHistory.wiki - StyleGuide.wiki -}}} - -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.`yourproject`.googlecode.com/hg/` or `https://wiki.`yourproject`.googlecode.com/git/`. - -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. +--- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Language (Locale) Directory Name -
Arabicar
Bulgarianbg
Chinese (China)zh-Hans
Chinese (Taiwan)zh-Hant
Croatianhr
Czechcs
Danishda
Dutchnl
English (United Kingdom)en-GB
English (United States)en-US
Finnishfi
Frenchfr
Germande
Greekel
Hebrewhe
Hungarianhu
Italianit
Japaneseja
Koreanko
Norwegianno
Polishpl
Portuguese (Brazil)pt-BR
Romanianro
Russianru
Slovaksk
Spanishes
Swedishsv
Turkishtr
- -_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._ \ No newline at end of file +_The content on this page is based on the old Google Code documentation for Google Code wikis and has been adapted and changed to fit the HWKB. The original document 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._ \ No newline at end of file