Test/id

This page is only for testing page translation feature.

Dokumentasi

Fitur penterjemahan halaman memungkinkan penterjemahan halaman wiki ke dalam bahasa lain dapat dikontrol. Dengan kata lain isi dari setiap terjemahan harus lebih kurang berjumlah sama dengan halaman sumbernya. Halaman sumber dibagi menjadi beberapa bagian atau paragraf yang masing-masing diterjemahkan secara terpisah. Perubahan akan dapat terlihat di tingkat paragraf. Paragraf tersebut akan diterjemahkan dengan menggunakan Special:Translate, yang menyediakan fitur yang sama dari terjemahan pesannya, yaitu: tampilan terjemahan dalam bahasa yang berbeda, dan informasi tentang dokumentasi pesannya. Halaman ini juga dapat diakses dari Special:PageTranslation atau Special:LanguageStats. Sebuah fitur baru yang saat ini hanya berlaku untuk penterjemahan halaman adalah perbedaan tampilan dari pesan yang berubah.

Halaman terjemahan secara otomatis akan muncul dari paragraf yang sudah diterjemahkan dengan menggunakan halaman asal sebagai modelnya. Setiap halaman terjemahan memiliki persentase penyelesaian yang dihitung dari paragraf yang sudah diterjemahkan di mana prosentase itu akan menurun jika terjemahannya sudah usang. Terjemahan yang sudah usang juga akan distabilo.

Hal lain

Ada hantu lewat.

Images in paragraphs

I want to investigate how images can be places in the middle of paragraphs without causing the imfamous shortening of the first line after the image:

Here we just have the image code between two lines of text with no blank lines in between. This should keep the whole paragraph in one translation unit but look exceedingly ugly! The code for this image was [[Image:Kde440-desktop.jpg|400px|center]].

It doesn't look ugly, though. Can anyone explain why? Perhaps it has to do with the options used.

This time I used the 'thumb' option. How does that look? Is the line shortened now? Yes it is, so it would appear, that the problem is caused by the 'thumb' option. The code for this image was [[Image:Kde440-desktop.jpg|thumb|400px]].

I'll just make one more paragraph to see what happens if no options at all are given (other than size): This doesn't look right, either. Even if the image is wide enough to fill the whole line (and so avoid text aligned with the bottom of the image) there is still the problem with to little vertical spacing between text and image. The code for this image was [[Image:Kde440-desktop.jpg|400px]].

Can we conclude, that future guidlines for writers should specify, that images appearing in between text sections should never have the 'thumb' option selected? It seems that this would be a good idea. It also seems, that if the image appears in the middle of a paragraph it should have the 'center' option selected.

Smileys

The standard smiley image is too large. It pushes lines apart, which doesn't look good. It should be made smaller. I'll try to find the proper size . This it how it looks when nothing is done. On my display it is far too big. If I specify a size of 11px, this is how it looks: . Much better, now the size of the smiley is about the same as a capital letter (it would look even better if it could be lowered 1 or 2px). It could be larger without pushing lines apart - here is a 15px sized smiley (actually I believe this line has been lowered just a bit, but maybe not too much?

Of course it would be better to use a template so that writers would not need to worry about these details . The template Template:Smiley is just a simple code snippet. Perhaps it can be expanded to allow for different browser settings of font size, if that information could be captured inside a template.

Splitting bulleted lists in two translation units

• first
• second
• third
• fourth

Apparently it is possible to split a bulleted list in two translation units. Special:myLanguage/Tasks_and_Tools

Nested lists: Numbered:

1. First main item
   1. First sub item
   2. Second sub item
2. Second main item
3. Third main item
   1. Third sub item

A Table

Jumping around in code
Ctrl+Alt+O	Quick open file: enter part of a filename and select among all the files in the current session's projects' directory trees that match the string; the file will then be opened
Ctrl+Alt+C	Quick open class: enter part of a class name and select among all class names that match; the cursor will then jump to the class declaration
Ctrl+Alt+M	Quick open function: enter part of a (member) function name and select among all names that match; note that the list shows both declarations and definitions and the cursor will then jump to the selected item
Other things
Ctrl+_	Collapse one level: remove this block from view, for example if you want to focus on the bigger picture within a function
Ctrl++	Expand one level: undo the collapsing

Foo

The translate extension page describes the use of variables. They could be be used for version numbers and the like. You write
< tvar|variable>value</> (without the space character after the opening <, off course) inside a translatable section. To translators it will appear as $variable.

The nice thing about this is, that when the values changes, the changed value propagates to all translations automatically. Translators don't have to do anything, and the translations ar not marked as fuzzy. To make this happen, the page still has to be marked for translation, and affected units must be ticked to not affect translations.

Example: Writing

The current version of eKsampleApp is < tvar|version>0.0.1</>.

displays this

The current version of eKsampleApp is 0.0.1.

Unfortunately, currently the $variable is only availlable in the translated pages. If extended, this feature might be really useful, fx when an application changes name.

Note: The tvar tag seems to be processed quite early in the parsing, so it is OK to use it in templates and even between nowiki tags.

Translating variables

This might go to Translate a Page, fx immediately after Info-boxes.

A variable is a of the form $name. It is defined in the original page as < tvar|name>value</> (without the space character after the opening <, off course). Whenever you write $name in your translation, the value given in the original page will be inserted. If the value in the original page changes at a later time, that change will automatically be applied to your translation as well without the need for you to do anything.

Using variables

This might go somewhere on Toolbox

If you have something in your page that doesn't need to be translated, you can use a variable; this can be useful for things like version numbers. Lets say you are writing the page for the application eKsampleApp and want to include information on the current version number. You can then write something like this in an ordinary paragraph (ie. inside a translation unit):

The current version of eKsampleApp is < tvar|version>0.0.1</>.

(without the space character after the <, off course). This will display

The current version of eKsampleApp is 0.0.1.

Instead of the current version number, translators will see the variable $version, which displays the version number. Then, when the version number is changed, the change automatically appears on the translated pages. The change still needs to be marked for translation, but if the affected section is ticked to not affect translations the translators won't need to do anything.

Linking with templates

Lets define a template {{UB}}, which produces http://userbase.kde.org . Now lets try {{UB}}/Quick Start, which gives http://userbase.kde.org /Quick_Start. Now lets try [{{UB}}]: [http://userbase.kde.org ] and [{{UB}}/Quick_Start Quick Start]: [http://userbase.kde.org /Quick_Start Quick Start]

Information

Link to http://userbase.kde.org

Testing Special:myLanguage links. [[{{Plasma}}|A nice page]] gives [[Special:myLanguage/Plasma |A nice page]] and [[{{Plasma}}/Panels|An other page]] gives [[Special:myLanguage/Plasma /Panels|An other page]].

Note on trailing slashes: For external links like http://userbase.kde.org

it is OK to have a trailing slash in the template, but for internal links it only works, if the template is only going to be used as a path prefix: Links of the form [[Plasma/]] do not work.

Template for Application Lists

A Headline

	This is a short line of description. It should normally not be more than one or two sentences.
	Same icon, different link. This is just for testing purposes.

Another Headline

	This is a short line of description. It should normally not be more than one or two sentences.
	Same icon, different link. This is just for testing purposes.

That's all, folks!