Translate
Appearance
Text
This page always uses small font size
Width
AllToolbox
Translate to norsk bokmål
Translation of the wiki page Toolbox from English (en) to norsk (bokmål) (nb)
This tool does not work without JavaScript. JavaScript is disabled, failed to work, or this browser is unsupported.
Translations:Toolbox/Page display title/nb
Toolbox
You need translation rights to translate messages.Get permission
Translations:Toolbox/1/nb
{{Info|1=This page offers examples of formatting code for common tasks}}
You need translation rights to translate messages.Get permission
Whenever possible we begin an application's top-level page with this. The code to achieve it is
{{Input|1=<nowiki>{|class="tablecenter vertical-centered"
|[[Image:YourScreenshot.png|250px|thumb]]
|Your descriptive text
|}</nowiki>}}
Each heading goes on its own line starting and ending with two or more '=' characters. Once there are more than a handful of headings on a page they automatically create a Table of Contents, so use them. The number of '=' characters determines their level in the Table of Contents, thus your headings should be '==Main section name==', '===Subsection name===', '====Sub-subheading name here====', and so on. Avoid using single '=', as that denotes a page heading and every wiki page already has one made from its name; for example, this page's title "{{PAGENAME}}" appears as its page heading.
Use <nowiki>'''bold text'''</nowiki> to specify '''bold text''' and
<nowiki>''italic text''</nowiki> to specify ''italic text''.
In order to ensure we get easy and accurate translations, please adhere to the ''[[Special:myLanguage/Typographical_Guidelines|typographical guidelines]].''
We have templates to assist in correctly displaying code snippets. Examples of use in various situations are available on [[Special:myLanguage/Typographical_Guidelines|the typographical guideline page]]
If you have problems displaying pipe characters in your code snippet, please see the explanation and markup detailed on [[Special:myLanguage/Typographical_Guidelines|Typographical Guidelines]]
:"''':'''" is used for an indent, and was used in multiples in some old pages. This is deprecated, and causes some problems, so the multiples will be removed as they are found. A single "''':'''" indents by four characters.
Dates in a purely numerical format cause confusion, due to differences in expectations of geographical zones. Please format dates as {{Input|1=<nowiki>18 Mar 2011</nowiki>}} with the month either spelled out completely or in abbreviated form, and the year in 4-digit format. The day may be single or double-digit.
{{Note|1=Enumerations should never have blank lines in them: it breaks the sequence and numbering starts at one again. Similarly, there should never be blank lines before a sublist item whether enumerated or bulleted: it creates two levels of item markings (bullets or numbers)}}
{{Note|1=Please remember, that long lists are a problem for translators. With single level bulleted lists, place each bullet in a section of its own, i.e. make a blank line between bullets. With two levels of bullets the subitems must be kept in the same section as their top level bullet; if you have to use subbullets, please keep the sublists short! With enumerations involved, you must keep everything in one unit. Please try to avoid enumerations, and if you find that you must use them try to keep them short.}}
{{Remember|2=Workaround|1=Though it is important to avoid blank lines in enumerations and nested lists it is still possible to split such lists in several translations units. This is highly recommended!}}
To get each bullet and each sub bullet in its own translation unit you can enter something like this:
{{Input|1=<nowiki>* First bullet </translate >
<translate >
** First sub bullet </translate >
<translate >
** Another sub bullet<br /><br />This one consists of two paragraphs </translate >
<translate >
* The next main bullet </translate >
<translate >
** And so on</nowiki>}}
If on the other hand you need to have more sections in the same item, you can do something like this to have each section in a translation unit of its own:
{{Input|1=<nowiki>* First bullet </translate >
<translate >
* Second bullet, first section. </translate><br /><br /> <translate > Second section of the
second bullet. This section has a translation unit of its own </translate >
<translate >
* And so on</nowiki>}}
Itemizations are produced using ''';''' and ''':''' alternatively. They are best for giving short descriptions for a group of related objects.
{{Note|1=As always, please keep each item in a section of its own; it helps translators a lot.}}
There are three kinds of links to learn, internal ones, to another userbase page, internal links to a section of a userbase page, and external URL links.
For an internal link the format <nowiki>[[PageLayout]]</nowiki>, where you want to display the name of the page, does work, but it is not ideal, particularly for translation to docbook and for localisation. It is better to use the form <nowiki>[[Special:myLanguage/PageLayout|Page Layout]]</nowiki>, because that allows translators to link correctly even though the page name is localised. The result is that it directs to the correctly translated page, if one exists. You often need to include the link in a sentence, so in that case you would use
{{Input|1=<nowiki>[[Special:myLanguage/PageLayout|this page]]</nowiki>}} which displays
[[Special:myLanguage/PageLayout|this page]]
Internal links to subsections of a page use character '#' (hash) and should look like this {{Input|1=<nowiki>[[Special:myLanguage/Tasks_and_Tools#Working_with_Languages|...]]</nowiki>}}With this kind of link it is very important, that the page you link to declares the reference anchor. If the anchor contains space characters, replace them by character '_' (underscore) when calling the reference. If the reference is found, the section will be automatically displayed by your browser (if it manages anchors). If it is not the case, you will have to go down through the page to find the referenced section.
External links are given as the URL and a text separated by a space and delimited by single square brackets as in {{Input|1=<nowiki>[https://en.wikipedia.org/wiki/KDE KDE's Wikipedia page]</nowiki>}} which gives [https://en.wikipedia.org/wiki/KDE KDE's Wikipedia page].
Anchor declaration must be done immediatly BEFORE the referenced section, and followed by a blank line separating the anchor and its headline. In the following example just copy in the ID value, the title of associated section. It should look like this:
{{Input|1=<nowiki></translate><span id="Working with Languages"></span> <translate></nowiki>}}
If the page containing the section that you link to is not yet marked up for translation, you should omit the <nowiki></translate > and <translate ></nowiki> tags.
{{Input|1=<nowiki>[http://techbase.kde.org/Schedules our road map]</nowiki>}} displays
[http://techbase.kde.org/Schedules our road map], which would take you straight to the techbase page.
One last thing to note - when you preview your page, all links are live. This gives you two benefits. You can check (by hovering) that your links are set up as you expected, and you can use a red link to create a new page.
If you want to make a list of applications like the ones in the subpages of [[Special:myLanguage/Applications|Applications]], you should use the <code>AppItem</code> template. Simply enter
{{Input|1=<nowiki>{|
{{AppItem|System Settings/Locale|Preferences-desktop-locale.png|
Settings for localized handling of numbers, dates, etc}}A short text.
A few more short lines about the app. This is optional.
|-
{{AppItem|System Settings/Shortcuts and Gestures|Preferences-desktop-keyboard.png|
Shortcuts and Gestures}}Another short text. If you do not type <keycap>Enter</keycap> between the texts
you get one section no matter how long the text is.
|}</nowiki>}}
{|
{{AppItem|System Settings/Locale|Preferences-desktop-locale.png|
Settings for localized handling of numbers, dates, etc}}A short text.
A few more short lines about the app. This is optional.
|-
{{AppItem|System Settings/Shortcuts and Gestures|Preferences-desktop-keyboard.png|
Shortcuts and Gestures}}Another short text. If you do not type <keycap>Enter</keycap> between the texts you get one section no matter how long the text is.
|}
Note, that you should not prepend "Special:myLanguage" to the page name - the template takes care of that. Also note, that you must give a title, even if the title is the same as the page name.
Footnotes are rarely used in our pages, but if you need them you can place a <code><nowiki><ref></nowiki>''text''<nowiki></ref></nowiki></code> in the source where the footnote mark should appear. There has to be one <code><nowiki><references /></nowiki></code> somewhere in the source as well, usually towards the end of the page. This is where the text added by the <nowiki><ref></nowiki> tags will appear. For more info see the [http://en.wikipedia.org/wiki/Help:Footnotes Wikipedia help page].
Note that you can change the position of the image, but the default is left. The size of the image depends on the circumstances, but for screenshots I recommend no less than 250px and no more than 500px.
Also note that <code>Image:</code> and <code>File:</code> are synonyms.
So that <code><nowiki>[[Image:KMail-kde4.png]]</nowiki></code> is the same as <code><nowiki>[[File:KMail-kde4.png]]</nowiki></code>. However <code>Image:</code> is deprecated, so prefer <code>File:</code> in new content.
Where you need to show more detail, create a moderately sized image, clickable, so that the full-size can be seen. Simply add the parameter '|thumb' within the image parentheses.
66 more messages
0% translated, 0% reviewed
Retrieved from "https://wikisandbox.kde.org/Special:Translate"