https://techbase.kde.org/api.php?action=feedcontributions&user=PingusPepan&feedformat=atomKDE TechBase - User contributions [en]2024-03-29T06:20:30ZUser contributionsMediaWiki 1.40.2https://techbase.kde.org/index.php?title=Translation_Workflow/cs&diff=63582Translation Workflow/cs2011-08-11T21:30:59Z<p>PingusPepan: Created page with "== Držení kroku s vývojem =="</p>
<hr />
<div><languages /><br />
<br />
Some of the information that was on this page is now outdated. How-Tos exist for all the common contributor tasks, including translation, both on- and off-line, and can be found linked from [[Tasks_and_Tools|Tasks and Tools]]. <br />
<br />
{{Warning|1=When editing pages that are already marked for translation, you will see section markers similar to <nowiki><!--T:1--></nowiki>. Usually each paragraph is one section. You should not change the markers, unless you fully delete a section, in which case you should simply remove the old marker. When adding new sections, you don't need to add marker to it – the marker will be added automatically when your changes are approved for translation. If you want to move a section, move also the section marker with it. That is the only time when you touch the markers - the system will do the rest.}}<br />
<br />
=== Obecné pokyny ===<br />
<br />
;Expressions, jargon, and humor<br />
: As you translate, you may encounter expressions, puns, or jargon that are specific to the original language and may be difficult to translate effectively. <br />
: In such cases, translate the concept or point the article is trying to convey and not the exact words. : Take care to ensure you capture the overall message, and don't worry about losing the humor or the colloquialism.<br />
<br />
;Proper names<br />
: Company names and product names should never be translated. Proper company names and product names should always remain in English, no matter what language you are translating for. <br />
: People's names should remain in English for Latin-based languages, but you may transliterate them for non-Latinbased alphabets.<br />
<br />
;Terminology<br />
: For help with translating tricky constructions or technical terms, consult the translation-sharing site to: [http://www.tausdata.org/index.php/taus-search TAUS]. <br />
: Simply enter your desired text and then choose which language to translate it from and to. Not all terms are included for all languages, but this can be a helpful tool for completing accurate translations. <br />
<br />
;Titles of works<br />
: When you run across the title of a book, program, feature, distro, or other public work, check to see if that title has already been officially translated for your language (by the publisher or distributor), and if so, use that translation. <br />
: If you cannot find a translation for that particular title in your language, do your best to translate it as accurately as possible. <br />
<br />
;Units of measure<br />
: Convert units of measure to make them relevant for the intended language or region.<br />
<br />
;User interface terms<br />
: Translate user interface terms as appropriate for your language.<br />
<br />
<br />
See here for more information:<br />
<br />
1. http://translate.sourceforge.net/wiki/guide/start<br />
<br />
2. Slovník: http://translate.sourceforge.net/wiki/guide/glossary<br />
<br />
3. Další slovník: http://www.glossary.com/category.php?q=Computer<br />
<br />
== Pokyny specifické pro jazyk ==<br />
<br />
UserBase proposes to have Team Leaders for each language. Techbase may, at a later date, do the same. As we get leaders appointed, they will take charge of a page of guidelines for their specific language, where they will be named. They will have final say on any question relating to their language. The guidelines will be linked from [[Translation_Workflow#Language-specific_guideline_pages|Language-specific guideline pages]].<br />
<br />
== Držení kroku s vývojem ==<br />
<br />
I propose that the Discussion page attached to this page should be used for orderly debate about general issues noted, particularly issues where existing markup is causing problems. I would ask you to put a Watch on [[Talk:Translation_Workflow]].<br />
<br />
== Getting a Better Understanding of the Process ==<br />
<br />
For a fuller description of the Translate extension, read the description on [http://translatewiki.net/wiki/Translating:Page_translation_feature the developers' website]<br />
<br />
{{Tip|1=Monitor the status of your language statistics by monitoring the page http://techbase.kde.org//your-language-code or simply [[Special:LanguageStats]] if you have your own language set as the interface language of TechBase.}}<br />
<br />
==Language-specific guideline pages ==<br />
<br />
Volunteer Team Leaders, please link your page from here (or ask for help)<br />
<br />
[[Translation_Workflow/Italian|Italian]]<br />
<br />
<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Translation_Workflow/17/cs&diff=63581Translations:Translation Workflow/17/cs2011-08-11T21:30:59Z<p>PingusPepan: Created page with "== Držení kroku s vývojem =="</p>
<hr />
<div>== Držení kroku s vývojem ==</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translation_Workflow/cs&diff=63580Translation Workflow/cs2011-08-11T21:30:34Z<p>PingusPepan: Created page with "== Pokyny specifické pro jazyk =="</p>
<hr />
<div><languages /><br />
<br />
Some of the information that was on this page is now outdated. How-Tos exist for all the common contributor tasks, including translation, both on- and off-line, and can be found linked from [[Tasks_and_Tools|Tasks and Tools]]. <br />
<br />
{{Warning|1=When editing pages that are already marked for translation, you will see section markers similar to <nowiki><!--T:1--></nowiki>. Usually each paragraph is one section. You should not change the markers, unless you fully delete a section, in which case you should simply remove the old marker. When adding new sections, you don't need to add marker to it – the marker will be added automatically when your changes are approved for translation. If you want to move a section, move also the section marker with it. That is the only time when you touch the markers - the system will do the rest.}}<br />
<br />
=== Obecné pokyny ===<br />
<br />
;Expressions, jargon, and humor<br />
: As you translate, you may encounter expressions, puns, or jargon that are specific to the original language and may be difficult to translate effectively. <br />
: In such cases, translate the concept or point the article is trying to convey and not the exact words. : Take care to ensure you capture the overall message, and don't worry about losing the humor or the colloquialism.<br />
<br />
;Proper names<br />
: Company names and product names should never be translated. Proper company names and product names should always remain in English, no matter what language you are translating for. <br />
: People's names should remain in English for Latin-based languages, but you may transliterate them for non-Latinbased alphabets.<br />
<br />
;Terminology<br />
: For help with translating tricky constructions or technical terms, consult the translation-sharing site to: [http://www.tausdata.org/index.php/taus-search TAUS]. <br />
: Simply enter your desired text and then choose which language to translate it from and to. Not all terms are included for all languages, but this can be a helpful tool for completing accurate translations. <br />
<br />
;Titles of works<br />
: When you run across the title of a book, program, feature, distro, or other public work, check to see if that title has already been officially translated for your language (by the publisher or distributor), and if so, use that translation. <br />
: If you cannot find a translation for that particular title in your language, do your best to translate it as accurately as possible. <br />
<br />
;Units of measure<br />
: Convert units of measure to make them relevant for the intended language or region.<br />
<br />
;User interface terms<br />
: Translate user interface terms as appropriate for your language.<br />
<br />
<br />
See here for more information:<br />
<br />
1. http://translate.sourceforge.net/wiki/guide/start<br />
<br />
2. Slovník: http://translate.sourceforge.net/wiki/guide/glossary<br />
<br />
3. Další slovník: http://www.glossary.com/category.php?q=Computer<br />
<br />
== Pokyny specifické pro jazyk ==<br />
<br />
UserBase proposes to have Team Leaders for each language. Techbase may, at a later date, do the same. As we get leaders appointed, they will take charge of a page of guidelines for their specific language, where they will be named. They will have final say on any question relating to their language. The guidelines will be linked from [[Translation_Workflow#Language-specific_guideline_pages|Language-specific guideline pages]].<br />
<br />
== Keeping up to date with development ==<br />
<br />
I propose that the Discussion page attached to this page should be used for orderly debate about general issues noted, particularly issues where existing markup is causing problems. I would ask you to put a Watch on [[Talk:Translation_Workflow]].<br />
<br />
== Getting a Better Understanding of the Process ==<br />
<br />
For a fuller description of the Translate extension, read the description on [http://translatewiki.net/wiki/Translating:Page_translation_feature the developers' website]<br />
<br />
{{Tip|1=Monitor the status of your language statistics by monitoring the page http://techbase.kde.org//your-language-code or simply [[Special:LanguageStats]] if you have your own language set as the interface language of TechBase.}}<br />
<br />
==Language-specific guideline pages ==<br />
<br />
Volunteer Team Leaders, please link your page from here (or ask for help)<br />
<br />
[[Translation_Workflow/Italian|Italian]]<br />
<br />
<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Translation_Workflow/15/cs&diff=63579Translations:Translation Workflow/15/cs2011-08-11T21:30:34Z<p>PingusPepan: Created page with "== Pokyny specifické pro jazyk =="</p>
<hr />
<div>== Pokyny specifické pro jazyk ==</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translation_Workflow/cs&diff=63578Translation Workflow/cs2011-08-11T21:30:22Z<p>PingusPepan: Created page with "3. Další slovník: http://www.glossary.com/category.php?q=Computer"</p>
<hr />
<div><languages /><br />
<br />
Some of the information that was on this page is now outdated. How-Tos exist for all the common contributor tasks, including translation, both on- and off-line, and can be found linked from [[Tasks_and_Tools|Tasks and Tools]]. <br />
<br />
{{Warning|1=When editing pages that are already marked for translation, you will see section markers similar to <nowiki><!--T:1--></nowiki>. Usually each paragraph is one section. You should not change the markers, unless you fully delete a section, in which case you should simply remove the old marker. When adding new sections, you don't need to add marker to it – the marker will be added automatically when your changes are approved for translation. If you want to move a section, move also the section marker with it. That is the only time when you touch the markers - the system will do the rest.}}<br />
<br />
=== Obecné pokyny ===<br />
<br />
;Expressions, jargon, and humor<br />
: As you translate, you may encounter expressions, puns, or jargon that are specific to the original language and may be difficult to translate effectively. <br />
: In such cases, translate the concept or point the article is trying to convey and not the exact words. : Take care to ensure you capture the overall message, and don't worry about losing the humor or the colloquialism.<br />
<br />
;Proper names<br />
: Company names and product names should never be translated. Proper company names and product names should always remain in English, no matter what language you are translating for. <br />
: People's names should remain in English for Latin-based languages, but you may transliterate them for non-Latinbased alphabets.<br />
<br />
;Terminology<br />
: For help with translating tricky constructions or technical terms, consult the translation-sharing site to: [http://www.tausdata.org/index.php/taus-search TAUS]. <br />
: Simply enter your desired text and then choose which language to translate it from and to. Not all terms are included for all languages, but this can be a helpful tool for completing accurate translations. <br />
<br />
;Titles of works<br />
: When you run across the title of a book, program, feature, distro, or other public work, check to see if that title has already been officially translated for your language (by the publisher or distributor), and if so, use that translation. <br />
: If you cannot find a translation for that particular title in your language, do your best to translate it as accurately as possible. <br />
<br />
;Units of measure<br />
: Convert units of measure to make them relevant for the intended language or region.<br />
<br />
;User interface terms<br />
: Translate user interface terms as appropriate for your language.<br />
<br />
<br />
See here for more information:<br />
<br />
1. http://translate.sourceforge.net/wiki/guide/start<br />
<br />
2. Slovník: http://translate.sourceforge.net/wiki/guide/glossary<br />
<br />
3. Další slovník: http://www.glossary.com/category.php?q=Computer<br />
<br />
== Guidelines specific to a Language ==<br />
<br />
UserBase proposes to have Team Leaders for each language. Techbase may, at a later date, do the same. As we get leaders appointed, they will take charge of a page of guidelines for their specific language, where they will be named. They will have final say on any question relating to their language. The guidelines will be linked from [[Translation_Workflow#Language-specific_guideline_pages|Language-specific guideline pages]].<br />
<br />
== Keeping up to date with development ==<br />
<br />
I propose that the Discussion page attached to this page should be used for orderly debate about general issues noted, particularly issues where existing markup is causing problems. I would ask you to put a Watch on [[Talk:Translation_Workflow]].<br />
<br />
== Getting a Better Understanding of the Process ==<br />
<br />
For a fuller description of the Translate extension, read the description on [http://translatewiki.net/wiki/Translating:Page_translation_feature the developers' website]<br />
<br />
{{Tip|1=Monitor the status of your language statistics by monitoring the page http://techbase.kde.org//your-language-code or simply [[Special:LanguageStats]] if you have your own language set as the interface language of TechBase.}}<br />
<br />
==Language-specific guideline pages ==<br />
<br />
Volunteer Team Leaders, please link your page from here (or ask for help)<br />
<br />
[[Translation_Workflow/Italian|Italian]]<br />
<br />
<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Translation_Workflow/14/cs&diff=63577Translations:Translation Workflow/14/cs2011-08-11T21:30:22Z<p>PingusPepan: Created page with "3. Další slovník: http://www.glossary.com/category.php?q=Computer"</p>
<hr />
<div>3. Další slovník: http://www.glossary.com/category.php?q=Computer</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translation_Workflow/cs&diff=63576Translation Workflow/cs2011-08-11T21:30:10Z<p>PingusPepan: Created page with "2. Slovník: http://translate.sourceforge.net/wiki/guide/glossary"</p>
<hr />
<div><languages /><br />
<br />
Some of the information that was on this page is now outdated. How-Tos exist for all the common contributor tasks, including translation, both on- and off-line, and can be found linked from [[Tasks_and_Tools|Tasks and Tools]]. <br />
<br />
{{Warning|1=When editing pages that are already marked for translation, you will see section markers similar to <nowiki><!--T:1--></nowiki>. Usually each paragraph is one section. You should not change the markers, unless you fully delete a section, in which case you should simply remove the old marker. When adding new sections, you don't need to add marker to it – the marker will be added automatically when your changes are approved for translation. If you want to move a section, move also the section marker with it. That is the only time when you touch the markers - the system will do the rest.}}<br />
<br />
=== Obecné pokyny ===<br />
<br />
;Expressions, jargon, and humor<br />
: As you translate, you may encounter expressions, puns, or jargon that are specific to the original language and may be difficult to translate effectively. <br />
: In such cases, translate the concept or point the article is trying to convey and not the exact words. : Take care to ensure you capture the overall message, and don't worry about losing the humor or the colloquialism.<br />
<br />
;Proper names<br />
: Company names and product names should never be translated. Proper company names and product names should always remain in English, no matter what language you are translating for. <br />
: People's names should remain in English for Latin-based languages, but you may transliterate them for non-Latinbased alphabets.<br />
<br />
;Terminology<br />
: For help with translating tricky constructions or technical terms, consult the translation-sharing site to: [http://www.tausdata.org/index.php/taus-search TAUS]. <br />
: Simply enter your desired text and then choose which language to translate it from and to. Not all terms are included for all languages, but this can be a helpful tool for completing accurate translations. <br />
<br />
;Titles of works<br />
: When you run across the title of a book, program, feature, distro, or other public work, check to see if that title has already been officially translated for your language (by the publisher or distributor), and if so, use that translation. <br />
: If you cannot find a translation for that particular title in your language, do your best to translate it as accurately as possible. <br />
<br />
;Units of measure<br />
: Convert units of measure to make them relevant for the intended language or region.<br />
<br />
;User interface terms<br />
: Translate user interface terms as appropriate for your language.<br />
<br />
<br />
See here for more information:<br />
<br />
1. http://translate.sourceforge.net/wiki/guide/start<br />
<br />
2. Slovník: http://translate.sourceforge.net/wiki/guide/glossary<br />
<br />
3. Another Glossary: http://www.glossary.com/category.php?q=Computer<br />
<br />
== Guidelines specific to a Language ==<br />
<br />
UserBase proposes to have Team Leaders for each language. Techbase may, at a later date, do the same. As we get leaders appointed, they will take charge of a page of guidelines for their specific language, where they will be named. They will have final say on any question relating to their language. The guidelines will be linked from [[Translation_Workflow#Language-specific_guideline_pages|Language-specific guideline pages]].<br />
<br />
== Keeping up to date with development ==<br />
<br />
I propose that the Discussion page attached to this page should be used for orderly debate about general issues noted, particularly issues where existing markup is causing problems. I would ask you to put a Watch on [[Talk:Translation_Workflow]].<br />
<br />
== Getting a Better Understanding of the Process ==<br />
<br />
For a fuller description of the Translate extension, read the description on [http://translatewiki.net/wiki/Translating:Page_translation_feature the developers' website]<br />
<br />
{{Tip|1=Monitor the status of your language statistics by monitoring the page http://techbase.kde.org//your-language-code or simply [[Special:LanguageStats]] if you have your own language set as the interface language of TechBase.}}<br />
<br />
==Language-specific guideline pages ==<br />
<br />
Volunteer Team Leaders, please link your page from here (or ask for help)<br />
<br />
[[Translation_Workflow/Italian|Italian]]<br />
<br />
<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Translation_Workflow/13/cs&diff=63575Translations:Translation Workflow/13/cs2011-08-11T21:30:10Z<p>PingusPepan: Created page with "2. Slovník: http://translate.sourceforge.net/wiki/guide/glossary"</p>
<hr />
<div>2. Slovník: http://translate.sourceforge.net/wiki/guide/glossary</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Translation_Workflow/12/cs&diff=63574Translations:Translation Workflow/12/cs2011-08-11T21:30:00Z<p>PingusPepan: Created page with "1. http://translate.sourceforge.net/wiki/guide/start"</p>
<hr />
<div>1. http://translate.sourceforge.net/wiki/guide/start</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translation_Workflow/cs&diff=63573Translation Workflow/cs2011-08-11T21:29:40Z<p>PingusPepan: Created page with "=== Obecné pokyny ==="</p>
<hr />
<div><languages /><br />
<br />
Some of the information that was on this page is now outdated. How-Tos exist for all the common contributor tasks, including translation, both on- and off-line, and can be found linked from [[Tasks_and_Tools|Tasks and Tools]]. <br />
<br />
{{Warning|1=When editing pages that are already marked for translation, you will see section markers similar to <nowiki><!--T:1--></nowiki>. Usually each paragraph is one section. You should not change the markers, unless you fully delete a section, in which case you should simply remove the old marker. When adding new sections, you don't need to add marker to it – the marker will be added automatically when your changes are approved for translation. If you want to move a section, move also the section marker with it. That is the only time when you touch the markers - the system will do the rest.}}<br />
<br />
=== Obecné pokyny ===<br />
<br />
;Expressions, jargon, and humor<br />
: As you translate, you may encounter expressions, puns, or jargon that are specific to the original language and may be difficult to translate effectively. <br />
: In such cases, translate the concept or point the article is trying to convey and not the exact words. : Take care to ensure you capture the overall message, and don't worry about losing the humor or the colloquialism.<br />
<br />
;Proper names<br />
: Company names and product names should never be translated. Proper company names and product names should always remain in English, no matter what language you are translating for. <br />
: People's names should remain in English for Latin-based languages, but you may transliterate them for non-Latinbased alphabets.<br />
<br />
;Terminology<br />
: For help with translating tricky constructions or technical terms, consult the translation-sharing site to: [http://www.tausdata.org/index.php/taus-search TAUS]. <br />
: Simply enter your desired text and then choose which language to translate it from and to. Not all terms are included for all languages, but this can be a helpful tool for completing accurate translations. <br />
<br />
;Titles of works<br />
: When you run across the title of a book, program, feature, distro, or other public work, check to see if that title has already been officially translated for your language (by the publisher or distributor), and if so, use that translation. <br />
: If you cannot find a translation for that particular title in your language, do your best to translate it as accurately as possible. <br />
<br />
;Units of measure<br />
: Convert units of measure to make them relevant for the intended language or region.<br />
<br />
;User interface terms<br />
: Translate user interface terms as appropriate for your language.<br />
<br />
<br />
See here for more information:<br />
<br />
1. http://translate.sourceforge.net/wiki/guide/start<br />
<br />
2. Glossary: http://translate.sourceforge.net/wiki/guide/glossary<br />
<br />
3. Another Glossary: http://www.glossary.com/category.php?q=Computer<br />
<br />
== Guidelines specific to a Language ==<br />
<br />
UserBase proposes to have Team Leaders for each language. Techbase may, at a later date, do the same. As we get leaders appointed, they will take charge of a page of guidelines for their specific language, where they will be named. They will have final say on any question relating to their language. The guidelines will be linked from [[Translation_Workflow#Language-specific_guideline_pages|Language-specific guideline pages]].<br />
<br />
== Keeping up to date with development ==<br />
<br />
I propose that the Discussion page attached to this page should be used for orderly debate about general issues noted, particularly issues where existing markup is causing problems. I would ask you to put a Watch on [[Talk:Translation_Workflow]].<br />
<br />
== Getting a Better Understanding of the Process ==<br />
<br />
For a fuller description of the Translate extension, read the description on [http://translatewiki.net/wiki/Translating:Page_translation_feature the developers' website]<br />
<br />
{{Tip|1=Monitor the status of your language statistics by monitoring the page http://techbase.kde.org//your-language-code or simply [[Special:LanguageStats]] if you have your own language set as the interface language of TechBase.}}<br />
<br />
==Language-specific guideline pages ==<br />
<br />
Volunteer Team Leaders, please link your page from here (or ask for help)<br />
<br />
[[Translation_Workflow/Italian|Italian]]<br />
<br />
<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Translation_Workflow/4/cs&diff=63572Translations:Translation Workflow/4/cs2011-08-11T21:29:40Z<p>PingusPepan: Created page with "=== Obecné pokyny ==="</p>
<hr />
<div>=== Obecné pokyny ===</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translate_a_Page/cs&diff=63571Translate a Page/cs2011-08-11T21:27:42Z<p>PingusPepan: Created page with "=== Info-boxy ==="</p>
<hr />
<div><languages /><br />
<br />
== Dostupné nástroje == <br />
<br />
* [[Special:myLanguage/Translation Workflow|Translation Workflow]] describes the workflow to migrate to the new translation system<br />
<br />
== Workflow == <br />
<br />
* Request addition to the Translator group:<br />
** Click on [[Special:myLanguage/Translator Account|Get a Translator Account]] in the sidebar<br />
** Click on the <menuchoice>Edit</menuchoice> icon [[Image:Userbase-edit.png|14px]] and enter your username, the language you want to translate for and whether you intend to translate off-line<br />
** Use <menuchoice>Save page</menuchoice> to save the information<br />
<br />
* When your user has been added to the group (you should get an notification), click on [[Special:LanguageStats|Start Translating]] in the sidebar<br />
<br />
* Enter the language you want to translate to in <menuchoice>Language code</menuchoice> and click on <menuchoice>Go</menuchoice><br />
<br />
{{Note|Entering ''en'' (English) as the language code won't display any untranslated messages since all original content is written in English}}<br />
<br />
* Ze seznamu si vyberte stránku, kterou chcete překládat a klikněte na ni<br />
<br />
* In the '''Translate page''' set <menuchoice>View all untranslated message</menuchoice> in the first drop-down list<br />
<br />
* Zkontrolujte podle kódu jazyka, jestli je pro překlad vybrán správný jazyk<br />
<br />
* In the <menuchoice>Navigation</menuchoice> section, click on the link to the left of the message you want to translate<br />
<br />
* Enter the translation - a Google translation is provided for reference, but your own translation is usually preferred.<br />
<br />
* Click on <menuchoice>Save and open next</menuchoice> to continue with the next message or <menuchoice>Save page</menuchoice> to save the translation if you wish to stop working.<br />
<br />
{{Warning|1=Do not create a localized page variant manually (by entering pagename/langcode and trying to translate the original). This will mess up the translation system and no translation will be shown at all.}}<br />
<br />
== Rady a tipy == <br />
<br />
=== Image display instructions === <br />
<br />
A typical example is <nowiki>[[Image:Plasma-kickoff.jpg|right|160px]]</nowiki>. The whole of this is a system instruction on how to display the image. None of it is translated.<br />
<br />
=== Category statements ===<br />
<br />
In this context, think of the word "Category" as a system word which therefore should not be translated. For example, <nowiki>[[Category:Administration]]</nowiki> would become <nowiki>[[Category:Administrasi/id]]</nowiki><br />
<br />
For consistency,UserBase has lists of approved translations of categories. Translation teams may find a similar list useful. Such tables can be seen at [{{UB}}Translation_Help_Needed Translation Help Needed]. Please request help if you need it.<br />
<br />
=== Links to other pages on TechBase === <br />
<br />
These take the form <nowiki>[[Special:myLanguage/Other page|link text]]</nowiki> The link should remain untranslated, whereas the link text should always be translated. If no link text is present, please add suitable (translated) link text.<br />
<br />
Note: "myLanguage" will try to load the translated version of the link in the language you have set in your user preferences. If it fails to load it will just load the English original, so it is safe to use it for any internal link.<br />
<br />
=== Odkazy na externí stránky === <br />
<br />
These take the form <nowiki>[http://example.com link text]</nowiki> Like the internal links, retain the actual link and translate the link text.<br />
<br />
=== Odkazy v postranním panelu ===<br />
<br />
Instructions for translating those sidebar links can be found at [[Modifying_the_Sidebar#Translating_Sidebar_Items]]<br />
<br />
<br />
=== Info-boxy === <br />
<br />
These generally consist of a header word "Information" and an editable information text. If the word "Information" is not recognizable in your language you may need a localized version of the template. Please ask if you need help with this.<br />
<br />
=== Translated units are marked as fuzzy === <br />
<br />
Sometimes it may happen that you have translated a page, but the translation is marked as incomplete. Certain errors in the markup of the original page can cause this. The most common type of error is the appearance of unbalanced brackets or parentheses. The translation system requires that all opening brackets ('[', '{' or '(' ) have a matching closing bracket (']', '}' or ')' ) in the same translation unit, otherwise the translation is considered incomplete.<br />
<br />
The same rule is not enforced by the wiki software, so it is easy for writers to miss those mistakes. If a bracket character is simply missing, just add it. However, sometimes the bracketed content extends over more than one translation unit, so that the matching closing bracket is in later unit. In this case you need to balance brackets in both units, but you can't simply add bracket characters without changing the meaning or formatting, so you must must comment out the added bracket character, like this<br />
<br />
{{Input|1=<nowiki><!--}}-->{{Info|1=Beginning of long info box... </nowiki>}}<br />
<br />
and in a later unit<br />
<br />
{{Input|1=<nowiki> ...end of long info box}}<!--{{--></nowiki>}}<br />
<br />
If the offending bracket is part of a smiley, please replace it with an emoticon icon. For the standard smiley, <!--(-->:-), you can use the template <nowiki>{{Smiley}}</nowiki><br />
<br />
Please also correct the original page so other translators won't have the same problem, or leave a message on the discussion page.<br />
<br />
=== Language Statistics discrepancies === <br />
<br />
You may notice some slight discrepancy between the percentages stated on your LanguageStats page and the percentage on the language bar. This is normal. LanguageStats compares only the number of messages that are untranslated or outdated. The language bar statistic tries to be more intelligent. For instance, in one page (100 messages) 8 messages had a small (re-branding-releated) change, in each case, a single word was involved. There was 8% difference between the two statistics, since it was a substantial proportion of the messages, but a small proportion of the whole translation.<br />
<br />
=== If you use the Chromium or Chrome browser.... === <br />
<br />
Be aware that there seems to be some sort of caching problem on the Chromium browser. I have noticed that even with forced refreshes, sometimes statistics do not show up as they should (I have seen other things affected, too), yet if I open the same page in Firefox I see the correct stats.<br />
<br />
== Also See == <br />
<br />
* [http://translatewiki.net/wiki/Translating:Page_translation_feature#Translators]<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Translate_a_Page/26/cs&diff=63570Translations:Translate a Page/26/cs2011-08-11T21:27:42Z<p>PingusPepan: Created page with "=== Info-boxy ==="</p>
<hr />
<div>=== Info-boxy ===</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translate_a_Page/cs&diff=63569Translate a Page/cs2011-08-11T21:27:33Z<p>PingusPepan: Created page with "=== Odkazy v postranním panelu ==="</p>
<hr />
<div><languages /><br />
<br />
== Dostupné nástroje == <br />
<br />
* [[Special:myLanguage/Translation Workflow|Translation Workflow]] describes the workflow to migrate to the new translation system<br />
<br />
== Workflow == <br />
<br />
* Request addition to the Translator group:<br />
** Click on [[Special:myLanguage/Translator Account|Get a Translator Account]] in the sidebar<br />
** Click on the <menuchoice>Edit</menuchoice> icon [[Image:Userbase-edit.png|14px]] and enter your username, the language you want to translate for and whether you intend to translate off-line<br />
** Use <menuchoice>Save page</menuchoice> to save the information<br />
<br />
* When your user has been added to the group (you should get an notification), click on [[Special:LanguageStats|Start Translating]] in the sidebar<br />
<br />
* Enter the language you want to translate to in <menuchoice>Language code</menuchoice> and click on <menuchoice>Go</menuchoice><br />
<br />
{{Note|Entering ''en'' (English) as the language code won't display any untranslated messages since all original content is written in English}}<br />
<br />
* Ze seznamu si vyberte stránku, kterou chcete překládat a klikněte na ni<br />
<br />
* In the '''Translate page''' set <menuchoice>View all untranslated message</menuchoice> in the first drop-down list<br />
<br />
* Zkontrolujte podle kódu jazyka, jestli je pro překlad vybrán správný jazyk<br />
<br />
* In the <menuchoice>Navigation</menuchoice> section, click on the link to the left of the message you want to translate<br />
<br />
* Enter the translation - a Google translation is provided for reference, but your own translation is usually preferred.<br />
<br />
* Click on <menuchoice>Save and open next</menuchoice> to continue with the next message or <menuchoice>Save page</menuchoice> to save the translation if you wish to stop working.<br />
<br />
{{Warning|1=Do not create a localized page variant manually (by entering pagename/langcode and trying to translate the original). This will mess up the translation system and no translation will be shown at all.}}<br />
<br />
== Rady a tipy == <br />
<br />
=== Image display instructions === <br />
<br />
A typical example is <nowiki>[[Image:Plasma-kickoff.jpg|right|160px]]</nowiki>. The whole of this is a system instruction on how to display the image. None of it is translated.<br />
<br />
=== Category statements ===<br />
<br />
In this context, think of the word "Category" as a system word which therefore should not be translated. For example, <nowiki>[[Category:Administration]]</nowiki> would become <nowiki>[[Category:Administrasi/id]]</nowiki><br />
<br />
For consistency,UserBase has lists of approved translations of categories. Translation teams may find a similar list useful. Such tables can be seen at [{{UB}}Translation_Help_Needed Translation Help Needed]. Please request help if you need it.<br />
<br />
=== Links to other pages on TechBase === <br />
<br />
These take the form <nowiki>[[Special:myLanguage/Other page|link text]]</nowiki> The link should remain untranslated, whereas the link text should always be translated. If no link text is present, please add suitable (translated) link text.<br />
<br />
Note: "myLanguage" will try to load the translated version of the link in the language you have set in your user preferences. If it fails to load it will just load the English original, so it is safe to use it for any internal link.<br />
<br />
=== Odkazy na externí stránky === <br />
<br />
These take the form <nowiki>[http://example.com link text]</nowiki> Like the internal links, retain the actual link and translate the link text.<br />
<br />
=== Odkazy v postranním panelu ===<br />
<br />
Instructions for translating those sidebar links can be found at [[Modifying_the_Sidebar#Translating_Sidebar_Items]]<br />
<br />
<br />
=== Info-boxes === <br />
<br />
These generally consist of a header word "Information" and an editable information text. If the word "Information" is not recognizable in your language you may need a localized version of the template. Please ask if you need help with this.<br />
<br />
=== Translated units are marked as fuzzy === <br />
<br />
Sometimes it may happen that you have translated a page, but the translation is marked as incomplete. Certain errors in the markup of the original page can cause this. The most common type of error is the appearance of unbalanced brackets or parentheses. The translation system requires that all opening brackets ('[', '{' or '(' ) have a matching closing bracket (']', '}' or ')' ) in the same translation unit, otherwise the translation is considered incomplete.<br />
<br />
The same rule is not enforced by the wiki software, so it is easy for writers to miss those mistakes. If a bracket character is simply missing, just add it. However, sometimes the bracketed content extends over more than one translation unit, so that the matching closing bracket is in later unit. In this case you need to balance brackets in both units, but you can't simply add bracket characters without changing the meaning or formatting, so you must must comment out the added bracket character, like this<br />
<br />
{{Input|1=<nowiki><!--}}-->{{Info|1=Beginning of long info box... </nowiki>}}<br />
<br />
and in a later unit<br />
<br />
{{Input|1=<nowiki> ...end of long info box}}<!--{{--></nowiki>}}<br />
<br />
If the offending bracket is part of a smiley, please replace it with an emoticon icon. For the standard smiley, <!--(-->:-), you can use the template <nowiki>{{Smiley}}</nowiki><br />
<br />
Please also correct the original page so other translators won't have the same problem, or leave a message on the discussion page.<br />
<br />
=== Language Statistics discrepancies === <br />
<br />
You may notice some slight discrepancy between the percentages stated on your LanguageStats page and the percentage on the language bar. This is normal. LanguageStats compares only the number of messages that are untranslated or outdated. The language bar statistic tries to be more intelligent. For instance, in one page (100 messages) 8 messages had a small (re-branding-releated) change, in each case, a single word was involved. There was 8% difference between the two statistics, since it was a substantial proportion of the messages, but a small proportion of the whole translation.<br />
<br />
=== If you use the Chromium or Chrome browser.... === <br />
<br />
Be aware that there seems to be some sort of caching problem on the Chromium browser. I have noticed that even with forced refreshes, sometimes statistics do not show up as they should (I have seen other things affected, too), yet if I open the same page in Firefox I see the correct stats.<br />
<br />
== Also See == <br />
<br />
* [http://translatewiki.net/wiki/Translating:Page_translation_feature#Translators]<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Translate_a_Page/43/cs&diff=63568Translations:Translate a Page/43/cs2011-08-11T21:27:33Z<p>PingusPepan: Created page with "=== Odkazy v postranním panelu ==="</p>
<hr />
<div>=== Odkazy v postranním panelu ===</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translate_a_Page/cs&diff=63567Translate a Page/cs2011-08-11T21:27:19Z<p>PingusPepan: Created page with "=== Odkazy na externí stránky ==="</p>
<hr />
<div><languages /><br />
<br />
== Dostupné nástroje == <br />
<br />
* [[Special:myLanguage/Translation Workflow|Translation Workflow]] describes the workflow to migrate to the new translation system<br />
<br />
== Workflow == <br />
<br />
* Request addition to the Translator group:<br />
** Click on [[Special:myLanguage/Translator Account|Get a Translator Account]] in the sidebar<br />
** Click on the <menuchoice>Edit</menuchoice> icon [[Image:Userbase-edit.png|14px]] and enter your username, the language you want to translate for and whether you intend to translate off-line<br />
** Use <menuchoice>Save page</menuchoice> to save the information<br />
<br />
* When your user has been added to the group (you should get an notification), click on [[Special:LanguageStats|Start Translating]] in the sidebar<br />
<br />
* Enter the language you want to translate to in <menuchoice>Language code</menuchoice> and click on <menuchoice>Go</menuchoice><br />
<br />
{{Note|Entering ''en'' (English) as the language code won't display any untranslated messages since all original content is written in English}}<br />
<br />
* Ze seznamu si vyberte stránku, kterou chcete překládat a klikněte na ni<br />
<br />
* In the '''Translate page''' set <menuchoice>View all untranslated message</menuchoice> in the first drop-down list<br />
<br />
* Zkontrolujte podle kódu jazyka, jestli je pro překlad vybrán správný jazyk<br />
<br />
* In the <menuchoice>Navigation</menuchoice> section, click on the link to the left of the message you want to translate<br />
<br />
* Enter the translation - a Google translation is provided for reference, but your own translation is usually preferred.<br />
<br />
* Click on <menuchoice>Save and open next</menuchoice> to continue with the next message or <menuchoice>Save page</menuchoice> to save the translation if you wish to stop working.<br />
<br />
{{Warning|1=Do not create a localized page variant manually (by entering pagename/langcode and trying to translate the original). This will mess up the translation system and no translation will be shown at all.}}<br />
<br />
== Rady a tipy == <br />
<br />
=== Image display instructions === <br />
<br />
A typical example is <nowiki>[[Image:Plasma-kickoff.jpg|right|160px]]</nowiki>. The whole of this is a system instruction on how to display the image. None of it is translated.<br />
<br />
=== Category statements ===<br />
<br />
In this context, think of the word "Category" as a system word which therefore should not be translated. For example, <nowiki>[[Category:Administration]]</nowiki> would become <nowiki>[[Category:Administrasi/id]]</nowiki><br />
<br />
For consistency,UserBase has lists of approved translations of categories. Translation teams may find a similar list useful. Such tables can be seen at [{{UB}}Translation_Help_Needed Translation Help Needed]. Please request help if you need it.<br />
<br />
=== Links to other pages on TechBase === <br />
<br />
These take the form <nowiki>[[Special:myLanguage/Other page|link text]]</nowiki> The link should remain untranslated, whereas the link text should always be translated. If no link text is present, please add suitable (translated) link text.<br />
<br />
Note: "myLanguage" will try to load the translated version of the link in the language you have set in your user preferences. If it fails to load it will just load the English original, so it is safe to use it for any internal link.<br />
<br />
=== Odkazy na externí stránky === <br />
<br />
These take the form <nowiki>[http://example.com link text]</nowiki> Like the internal links, retain the actual link and translate the link text.<br />
<br />
=== Links in the Sidebar ===<br />
<br />
Instructions for translating those sidebar links can be found at [[Modifying_the_Sidebar#Translating_Sidebar_Items]]<br />
<br />
<br />
=== Info-boxes === <br />
<br />
These generally consist of a header word "Information" and an editable information text. If the word "Information" is not recognizable in your language you may need a localized version of the template. Please ask if you need help with this.<br />
<br />
=== Translated units are marked as fuzzy === <br />
<br />
Sometimes it may happen that you have translated a page, but the translation is marked as incomplete. Certain errors in the markup of the original page can cause this. The most common type of error is the appearance of unbalanced brackets or parentheses. The translation system requires that all opening brackets ('[', '{' or '(' ) have a matching closing bracket (']', '}' or ')' ) in the same translation unit, otherwise the translation is considered incomplete.<br />
<br />
The same rule is not enforced by the wiki software, so it is easy for writers to miss those mistakes. If a bracket character is simply missing, just add it. However, sometimes the bracketed content extends over more than one translation unit, so that the matching closing bracket is in later unit. In this case you need to balance brackets in both units, but you can't simply add bracket characters without changing the meaning or formatting, so you must must comment out the added bracket character, like this<br />
<br />
{{Input|1=<nowiki><!--}}-->{{Info|1=Beginning of long info box... </nowiki>}}<br />
<br />
and in a later unit<br />
<br />
{{Input|1=<nowiki> ...end of long info box}}<!--{{--></nowiki>}}<br />
<br />
If the offending bracket is part of a smiley, please replace it with an emoticon icon. For the standard smiley, <!--(-->:-), you can use the template <nowiki>{{Smiley}}</nowiki><br />
<br />
Please also correct the original page so other translators won't have the same problem, or leave a message on the discussion page.<br />
<br />
=== Language Statistics discrepancies === <br />
<br />
You may notice some slight discrepancy between the percentages stated on your LanguageStats page and the percentage on the language bar. This is normal. LanguageStats compares only the number of messages that are untranslated or outdated. The language bar statistic tries to be more intelligent. For instance, in one page (100 messages) 8 messages had a small (re-branding-releated) change, in each case, a single word was involved. There was 8% difference between the two statistics, since it was a substantial proportion of the messages, but a small proportion of the whole translation.<br />
<br />
=== If you use the Chromium or Chrome browser.... === <br />
<br />
Be aware that there seems to be some sort of caching problem on the Chromium browser. I have noticed that even with forced refreshes, sometimes statistics do not show up as they should (I have seen other things affected, too), yet if I open the same page in Firefox I see the correct stats.<br />
<br />
== Also See == <br />
<br />
* [http://translatewiki.net/wiki/Translating:Page_translation_feature#Translators]<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Translate_a_Page/24/cs&diff=63566Translations:Translate a Page/24/cs2011-08-11T21:27:19Z<p>PingusPepan: Created page with "=== Odkazy na externí stránky ==="</p>
<hr />
<div>=== Odkazy na externí stránky ===</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translate_a_Page/cs&diff=63565Translate a Page/cs2011-08-11T21:26:40Z<p>PingusPepan: Created page with "== Rady a tipy =="</p>
<hr />
<div><languages /><br />
<br />
== Dostupné nástroje == <br />
<br />
* [[Special:myLanguage/Translation Workflow|Translation Workflow]] describes the workflow to migrate to the new translation system<br />
<br />
== Workflow == <br />
<br />
* Request addition to the Translator group:<br />
** Click on [[Special:myLanguage/Translator Account|Get a Translator Account]] in the sidebar<br />
** Click on the <menuchoice>Edit</menuchoice> icon [[Image:Userbase-edit.png|14px]] and enter your username, the language you want to translate for and whether you intend to translate off-line<br />
** Use <menuchoice>Save page</menuchoice> to save the information<br />
<br />
* When your user has been added to the group (you should get an notification), click on [[Special:LanguageStats|Start Translating]] in the sidebar<br />
<br />
* Enter the language you want to translate to in <menuchoice>Language code</menuchoice> and click on <menuchoice>Go</menuchoice><br />
<br />
{{Note|Entering ''en'' (English) as the language code won't display any untranslated messages since all original content is written in English}}<br />
<br />
* Ze seznamu si vyberte stránku, kterou chcete překládat a klikněte na ni<br />
<br />
* In the '''Translate page''' set <menuchoice>View all untranslated message</menuchoice> in the first drop-down list<br />
<br />
* Zkontrolujte podle kódu jazyka, jestli je pro překlad vybrán správný jazyk<br />
<br />
* In the <menuchoice>Navigation</menuchoice> section, click on the link to the left of the message you want to translate<br />
<br />
* Enter the translation - a Google translation is provided for reference, but your own translation is usually preferred.<br />
<br />
* Click on <menuchoice>Save and open next</menuchoice> to continue with the next message or <menuchoice>Save page</menuchoice> to save the translation if you wish to stop working.<br />
<br />
{{Warning|1=Do not create a localized page variant manually (by entering pagename/langcode and trying to translate the original). This will mess up the translation system and no translation will be shown at all.}}<br />
<br />
== Rady a tipy == <br />
<br />
=== Image display instructions === <br />
<br />
A typical example is <nowiki>[[Image:Plasma-kickoff.jpg|right|160px]]</nowiki>. The whole of this is a system instruction on how to display the image. None of it is translated.<br />
<br />
=== Category statements ===<br />
<br />
In this context, think of the word "Category" as a system word which therefore should not be translated. For example, <nowiki>[[Category:Administration]]</nowiki> would become <nowiki>[[Category:Administrasi/id]]</nowiki><br />
<br />
For consistency,UserBase has lists of approved translations of categories. Translation teams may find a similar list useful. Such tables can be seen at [{{UB}}Translation_Help_Needed Translation Help Needed]. Please request help if you need it.<br />
<br />
=== Links to other pages on TechBase === <br />
<br />
These take the form <nowiki>[[Special:myLanguage/Other page|link text]]</nowiki> The link should remain untranslated, whereas the link text should always be translated. If no link text is present, please add suitable (translated) link text.<br />
<br />
Note: "myLanguage" will try to load the translated version of the link in the language you have set in your user preferences. If it fails to load it will just load the English original, so it is safe to use it for any internal link.<br />
<br />
=== Links to external sites === <br />
<br />
These take the form <nowiki>[http://example.com link text]</nowiki> Like the internal links, retain the actual link and translate the link text.<br />
<br />
=== Links in the Sidebar ===<br />
<br />
Instructions for translating those sidebar links can be found at [[Modifying_the_Sidebar#Translating_Sidebar_Items]]<br />
<br />
<br />
=== Info-boxes === <br />
<br />
These generally consist of a header word "Information" and an editable information text. If the word "Information" is not recognizable in your language you may need a localized version of the template. Please ask if you need help with this.<br />
<br />
=== Translated units are marked as fuzzy === <br />
<br />
Sometimes it may happen that you have translated a page, but the translation is marked as incomplete. Certain errors in the markup of the original page can cause this. The most common type of error is the appearance of unbalanced brackets or parentheses. The translation system requires that all opening brackets ('[', '{' or '(' ) have a matching closing bracket (']', '}' or ')' ) in the same translation unit, otherwise the translation is considered incomplete.<br />
<br />
The same rule is not enforced by the wiki software, so it is easy for writers to miss those mistakes. If a bracket character is simply missing, just add it. However, sometimes the bracketed content extends over more than one translation unit, so that the matching closing bracket is in later unit. In this case you need to balance brackets in both units, but you can't simply add bracket characters without changing the meaning or formatting, so you must must comment out the added bracket character, like this<br />
<br />
{{Input|1=<nowiki><!--}}-->{{Info|1=Beginning of long info box... </nowiki>}}<br />
<br />
and in a later unit<br />
<br />
{{Input|1=<nowiki> ...end of long info box}}<!--{{--></nowiki>}}<br />
<br />
If the offending bracket is part of a smiley, please replace it with an emoticon icon. For the standard smiley, <!--(-->:-), you can use the template <nowiki>{{Smiley}}</nowiki><br />
<br />
Please also correct the original page so other translators won't have the same problem, or leave a message on the discussion page.<br />
<br />
=== Language Statistics discrepancies === <br />
<br />
You may notice some slight discrepancy between the percentages stated on your LanguageStats page and the percentage on the language bar. This is normal. LanguageStats compares only the number of messages that are untranslated or outdated. The language bar statistic tries to be more intelligent. For instance, in one page (100 messages) 8 messages had a small (re-branding-releated) change, in each case, a single word was involved. There was 8% difference between the two statistics, since it was a substantial proportion of the messages, but a small proportion of the whole translation.<br />
<br />
=== If you use the Chromium or Chrome browser.... === <br />
<br />
Be aware that there seems to be some sort of caching problem on the Chromium browser. I have noticed that even with forced refreshes, sometimes statistics do not show up as they should (I have seen other things affected, too), yet if I open the same page in Firefox I see the correct stats.<br />
<br />
== Also See == <br />
<br />
* [http://translatewiki.net/wiki/Translating:Page_translation_feature#Translators]<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Translate_a_Page/15/cs&diff=63564Translations:Translate a Page/15/cs2011-08-11T21:26:40Z<p>PingusPepan: Created page with "== Rady a tipy =="</p>
<hr />
<div>== Rady a tipy ==</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translate_a_Page/cs&diff=63563Translate a Page/cs2011-08-11T21:26:22Z<p>PingusPepan: Created page with "* Zkontrolujte podle kódu jazyka, jestli je pro překlad vybrán správný jazyk"</p>
<hr />
<div><languages /><br />
<br />
== Dostupné nástroje == <br />
<br />
* [[Special:myLanguage/Translation Workflow|Translation Workflow]] describes the workflow to migrate to the new translation system<br />
<br />
== Workflow == <br />
<br />
* Request addition to the Translator group:<br />
** Click on [[Special:myLanguage/Translator Account|Get a Translator Account]] in the sidebar<br />
** Click on the <menuchoice>Edit</menuchoice> icon [[Image:Userbase-edit.png|14px]] and enter your username, the language you want to translate for and whether you intend to translate off-line<br />
** Use <menuchoice>Save page</menuchoice> to save the information<br />
<br />
* When your user has been added to the group (you should get an notification), click on [[Special:LanguageStats|Start Translating]] in the sidebar<br />
<br />
* Enter the language you want to translate to in <menuchoice>Language code</menuchoice> and click on <menuchoice>Go</menuchoice><br />
<br />
{{Note|Entering ''en'' (English) as the language code won't display any untranslated messages since all original content is written in English}}<br />
<br />
* Ze seznamu si vyberte stránku, kterou chcete překládat a klikněte na ni<br />
<br />
* In the '''Translate page''' set <menuchoice>View all untranslated message</menuchoice> in the first drop-down list<br />
<br />
* Zkontrolujte podle kódu jazyka, jestli je pro překlad vybrán správný jazyk<br />
<br />
* In the <menuchoice>Navigation</menuchoice> section, click on the link to the left of the message you want to translate<br />
<br />
* Enter the translation - a Google translation is provided for reference, but your own translation is usually preferred.<br />
<br />
* Click on <menuchoice>Save and open next</menuchoice> to continue with the next message or <menuchoice>Save page</menuchoice> to save the translation if you wish to stop working.<br />
<br />
{{Warning|1=Do not create a localized page variant manually (by entering pagename/langcode and trying to translate the original). This will mess up the translation system and no translation will be shown at all.}}<br />
<br />
== Hints and Tips == <br />
<br />
=== Image display instructions === <br />
<br />
A typical example is <nowiki>[[Image:Plasma-kickoff.jpg|right|160px]]</nowiki>. The whole of this is a system instruction on how to display the image. None of it is translated.<br />
<br />
=== Category statements ===<br />
<br />
In this context, think of the word "Category" as a system word which therefore should not be translated. For example, <nowiki>[[Category:Administration]]</nowiki> would become <nowiki>[[Category:Administrasi/id]]</nowiki><br />
<br />
For consistency,UserBase has lists of approved translations of categories. Translation teams may find a similar list useful. Such tables can be seen at [{{UB}}Translation_Help_Needed Translation Help Needed]. Please request help if you need it.<br />
<br />
=== Links to other pages on TechBase === <br />
<br />
These take the form <nowiki>[[Special:myLanguage/Other page|link text]]</nowiki> The link should remain untranslated, whereas the link text should always be translated. If no link text is present, please add suitable (translated) link text.<br />
<br />
Note: "myLanguage" will try to load the translated version of the link in the language you have set in your user preferences. If it fails to load it will just load the English original, so it is safe to use it for any internal link.<br />
<br />
=== Links to external sites === <br />
<br />
These take the form <nowiki>[http://example.com link text]</nowiki> Like the internal links, retain the actual link and translate the link text.<br />
<br />
=== Links in the Sidebar ===<br />
<br />
Instructions for translating those sidebar links can be found at [[Modifying_the_Sidebar#Translating_Sidebar_Items]]<br />
<br />
<br />
=== Info-boxes === <br />
<br />
These generally consist of a header word "Information" and an editable information text. If the word "Information" is not recognizable in your language you may need a localized version of the template. Please ask if you need help with this.<br />
<br />
=== Translated units are marked as fuzzy === <br />
<br />
Sometimes it may happen that you have translated a page, but the translation is marked as incomplete. Certain errors in the markup of the original page can cause this. The most common type of error is the appearance of unbalanced brackets or parentheses. The translation system requires that all opening brackets ('[', '{' or '(' ) have a matching closing bracket (']', '}' or ')' ) in the same translation unit, otherwise the translation is considered incomplete.<br />
<br />
The same rule is not enforced by the wiki software, so it is easy for writers to miss those mistakes. If a bracket character is simply missing, just add it. However, sometimes the bracketed content extends over more than one translation unit, so that the matching closing bracket is in later unit. In this case you need to balance brackets in both units, but you can't simply add bracket characters without changing the meaning or formatting, so you must must comment out the added bracket character, like this<br />
<br />
{{Input|1=<nowiki><!--}}-->{{Info|1=Beginning of long info box... </nowiki>}}<br />
<br />
and in a later unit<br />
<br />
{{Input|1=<nowiki> ...end of long info box}}<!--{{--></nowiki>}}<br />
<br />
If the offending bracket is part of a smiley, please replace it with an emoticon icon. For the standard smiley, <!--(-->:-), you can use the template <nowiki>{{Smiley}}</nowiki><br />
<br />
Please also correct the original page so other translators won't have the same problem, or leave a message on the discussion page.<br />
<br />
=== Language Statistics discrepancies === <br />
<br />
You may notice some slight discrepancy between the percentages stated on your LanguageStats page and the percentage on the language bar. This is normal. LanguageStats compares only the number of messages that are untranslated or outdated. The language bar statistic tries to be more intelligent. For instance, in one page (100 messages) 8 messages had a small (re-branding-releated) change, in each case, a single word was involved. There was 8% difference between the two statistics, since it was a substantial proportion of the messages, but a small proportion of the whole translation.<br />
<br />
=== If you use the Chromium or Chrome browser.... === <br />
<br />
Be aware that there seems to be some sort of caching problem on the Chromium browser. I have noticed that even with forced refreshes, sometimes statistics do not show up as they should (I have seen other things affected, too), yet if I open the same page in Firefox I see the correct stats.<br />
<br />
== Also See == <br />
<br />
* [http://translatewiki.net/wiki/Translating:Page_translation_feature#Translators]<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Translate_a_Page/10/cs&diff=63562Translations:Translate a Page/10/cs2011-08-11T21:26:22Z<p>PingusPepan: Created page with "* Zkontrolujte podle kódu jazyka, jestli je pro překlad vybrán správný jazyk"</p>
<hr />
<div>* Zkontrolujte podle kódu jazyka, jestli je pro překlad vybrán správný jazyk</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translate_a_Page/cs&diff=63561Translate a Page/cs2011-08-11T21:25:34Z<p>PingusPepan: Created page with "* Ze seznamu si vyberte stránku, kterou chcete překládat a klikněte na ni"</p>
<hr />
<div><languages /><br />
<br />
== Dostupné nástroje == <br />
<br />
* [[Special:myLanguage/Translation Workflow|Translation Workflow]] describes the workflow to migrate to the new translation system<br />
<br />
== Workflow == <br />
<br />
* Request addition to the Translator group:<br />
** Click on [[Special:myLanguage/Translator Account|Get a Translator Account]] in the sidebar<br />
** Click on the <menuchoice>Edit</menuchoice> icon [[Image:Userbase-edit.png|14px]] and enter your username, the language you want to translate for and whether you intend to translate off-line<br />
** Use <menuchoice>Save page</menuchoice> to save the information<br />
<br />
* When your user has been added to the group (you should get an notification), click on [[Special:LanguageStats|Start Translating]] in the sidebar<br />
<br />
* Enter the language you want to translate to in <menuchoice>Language code</menuchoice> and click on <menuchoice>Go</menuchoice><br />
<br />
{{Note|Entering ''en'' (English) as the language code won't display any untranslated messages since all original content is written in English}}<br />
<br />
* Ze seznamu si vyberte stránku, kterou chcete překládat a klikněte na ni<br />
<br />
* In the '''Translate page''' set <menuchoice>View all untranslated message</menuchoice> in the first drop-down list<br />
<br />
* Check that the correct language code is showing<br />
<br />
* In the <menuchoice>Navigation</menuchoice> section, click on the link to the left of the message you want to translate<br />
<br />
* Enter the translation - a Google translation is provided for reference, but your own translation is usually preferred.<br />
<br />
* Click on <menuchoice>Save and open next</menuchoice> to continue with the next message or <menuchoice>Save page</menuchoice> to save the translation if you wish to stop working.<br />
<br />
{{Warning|1=Do not create a localized page variant manually (by entering pagename/langcode and trying to translate the original). This will mess up the translation system and no translation will be shown at all.}}<br />
<br />
== Hints and Tips == <br />
<br />
=== Image display instructions === <br />
<br />
A typical example is <nowiki>[[Image:Plasma-kickoff.jpg|right|160px]]</nowiki>. The whole of this is a system instruction on how to display the image. None of it is translated.<br />
<br />
=== Category statements ===<br />
<br />
In this context, think of the word "Category" as a system word which therefore should not be translated. For example, <nowiki>[[Category:Administration]]</nowiki> would become <nowiki>[[Category:Administrasi/id]]</nowiki><br />
<br />
For consistency,UserBase has lists of approved translations of categories. Translation teams may find a similar list useful. Such tables can be seen at [{{UB}}Translation_Help_Needed Translation Help Needed]. Please request help if you need it.<br />
<br />
=== Links to other pages on TechBase === <br />
<br />
These take the form <nowiki>[[Special:myLanguage/Other page|link text]]</nowiki> The link should remain untranslated, whereas the link text should always be translated. If no link text is present, please add suitable (translated) link text.<br />
<br />
Note: "myLanguage" will try to load the translated version of the link in the language you have set in your user preferences. If it fails to load it will just load the English original, so it is safe to use it for any internal link.<br />
<br />
=== Links to external sites === <br />
<br />
These take the form <nowiki>[http://example.com link text]</nowiki> Like the internal links, retain the actual link and translate the link text.<br />
<br />
=== Links in the Sidebar ===<br />
<br />
Instructions for translating those sidebar links can be found at [[Modifying_the_Sidebar#Translating_Sidebar_Items]]<br />
<br />
<br />
=== Info-boxes === <br />
<br />
These generally consist of a header word "Information" and an editable information text. If the word "Information" is not recognizable in your language you may need a localized version of the template. Please ask if you need help with this.<br />
<br />
=== Translated units are marked as fuzzy === <br />
<br />
Sometimes it may happen that you have translated a page, but the translation is marked as incomplete. Certain errors in the markup of the original page can cause this. The most common type of error is the appearance of unbalanced brackets or parentheses. The translation system requires that all opening brackets ('[', '{' or '(' ) have a matching closing bracket (']', '}' or ')' ) in the same translation unit, otherwise the translation is considered incomplete.<br />
<br />
The same rule is not enforced by the wiki software, so it is easy for writers to miss those mistakes. If a bracket character is simply missing, just add it. However, sometimes the bracketed content extends over more than one translation unit, so that the matching closing bracket is in later unit. In this case you need to balance brackets in both units, but you can't simply add bracket characters without changing the meaning or formatting, so you must must comment out the added bracket character, like this<br />
<br />
{{Input|1=<nowiki><!--}}-->{{Info|1=Beginning of long info box... </nowiki>}}<br />
<br />
and in a later unit<br />
<br />
{{Input|1=<nowiki> ...end of long info box}}<!--{{--></nowiki>}}<br />
<br />
If the offending bracket is part of a smiley, please replace it with an emoticon icon. For the standard smiley, <!--(-->:-), you can use the template <nowiki>{{Smiley}}</nowiki><br />
<br />
Please also correct the original page so other translators won't have the same problem, or leave a message on the discussion page.<br />
<br />
=== Language Statistics discrepancies === <br />
<br />
You may notice some slight discrepancy between the percentages stated on your LanguageStats page and the percentage on the language bar. This is normal. LanguageStats compares only the number of messages that are untranslated or outdated. The language bar statistic tries to be more intelligent. For instance, in one page (100 messages) 8 messages had a small (re-branding-releated) change, in each case, a single word was involved. There was 8% difference between the two statistics, since it was a substantial proportion of the messages, but a small proportion of the whole translation.<br />
<br />
=== If you use the Chromium or Chrome browser.... === <br />
<br />
Be aware that there seems to be some sort of caching problem on the Chromium browser. I have noticed that even with forced refreshes, sometimes statistics do not show up as they should (I have seen other things affected, too), yet if I open the same page in Firefox I see the correct stats.<br />
<br />
== Also See == <br />
<br />
* [http://translatewiki.net/wiki/Translating:Page_translation_feature#Translators]<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Translate_a_Page/8/cs&diff=63560Translations:Translate a Page/8/cs2011-08-11T21:25:34Z<p>PingusPepan: Created page with "* Ze seznamu si vyberte stránku, kterou chcete překládat a klikněte na ni"</p>
<hr />
<div>* Ze seznamu si vyberte stránku, kterou chcete překládat a klikněte na ni</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translate_a_Page/cs&diff=63559Translate a Page/cs2011-08-11T21:24:47Z<p>PingusPepan: Created page with "== Dostupné nástroje =="</p>
<hr />
<div><languages /><br />
<br />
== Dostupné nástroje == <br />
<br />
* [[Special:myLanguage/Translation Workflow|Translation Workflow]] describes the workflow to migrate to the new translation system<br />
<br />
== Workflow == <br />
<br />
* Request addition to the Translator group:<br />
** Click on [[Special:myLanguage/Translator Account|Get a Translator Account]] in the sidebar<br />
** Click on the <menuchoice>Edit</menuchoice> icon [[Image:Userbase-edit.png|14px]] and enter your username, the language you want to translate for and whether you intend to translate off-line<br />
** Use <menuchoice>Save page</menuchoice> to save the information<br />
<br />
* When your user has been added to the group (you should get an notification), click on [[Special:LanguageStats|Start Translating]] in the sidebar<br />
<br />
* Enter the language you want to translate to in <menuchoice>Language code</menuchoice> and click on <menuchoice>Go</menuchoice><br />
<br />
{{Note|Entering ''en'' (English) as the language code won't display any untranslated messages since all original content is written in English}}<br />
<br />
* Click on a page you want to translate in the list<br />
<br />
* In the '''Translate page''' set <menuchoice>View all untranslated message</menuchoice> in the first drop-down list<br />
<br />
* Check that the correct language code is showing<br />
<br />
* In the <menuchoice>Navigation</menuchoice> section, click on the link to the left of the message you want to translate<br />
<br />
* Enter the translation - a Google translation is provided for reference, but your own translation is usually preferred.<br />
<br />
* Click on <menuchoice>Save and open next</menuchoice> to continue with the next message or <menuchoice>Save page</menuchoice> to save the translation if you wish to stop working.<br />
<br />
{{Warning|1=Do not create a localized page variant manually (by entering pagename/langcode and trying to translate the original). This will mess up the translation system and no translation will be shown at all.}}<br />
<br />
== Hints and Tips == <br />
<br />
=== Image display instructions === <br />
<br />
A typical example is <nowiki>[[Image:Plasma-kickoff.jpg|right|160px]]</nowiki>. The whole of this is a system instruction on how to display the image. None of it is translated.<br />
<br />
=== Category statements ===<br />
<br />
In this context, think of the word "Category" as a system word which therefore should not be translated. For example, <nowiki>[[Category:Administration]]</nowiki> would become <nowiki>[[Category:Administrasi/id]]</nowiki><br />
<br />
For consistency,UserBase has lists of approved translations of categories. Translation teams may find a similar list useful. Such tables can be seen at [{{UB}}Translation_Help_Needed Translation Help Needed]. Please request help if you need it.<br />
<br />
=== Links to other pages on TechBase === <br />
<br />
These take the form <nowiki>[[Special:myLanguage/Other page|link text]]</nowiki> The link should remain untranslated, whereas the link text should always be translated. If no link text is present, please add suitable (translated) link text.<br />
<br />
Note: "myLanguage" will try to load the translated version of the link in the language you have set in your user preferences. If it fails to load it will just load the English original, so it is safe to use it for any internal link.<br />
<br />
=== Links to external sites === <br />
<br />
These take the form <nowiki>[http://example.com link text]</nowiki> Like the internal links, retain the actual link and translate the link text.<br />
<br />
=== Links in the Sidebar ===<br />
<br />
Instructions for translating those sidebar links can be found at [[Modifying_the_Sidebar#Translating_Sidebar_Items]]<br />
<br />
<br />
=== Info-boxes === <br />
<br />
These generally consist of a header word "Information" and an editable information text. If the word "Information" is not recognizable in your language you may need a localized version of the template. Please ask if you need help with this.<br />
<br />
=== Translated units are marked as fuzzy === <br />
<br />
Sometimes it may happen that you have translated a page, but the translation is marked as incomplete. Certain errors in the markup of the original page can cause this. The most common type of error is the appearance of unbalanced brackets or parentheses. The translation system requires that all opening brackets ('[', '{' or '(' ) have a matching closing bracket (']', '}' or ')' ) in the same translation unit, otherwise the translation is considered incomplete.<br />
<br />
The same rule is not enforced by the wiki software, so it is easy for writers to miss those mistakes. If a bracket character is simply missing, just add it. However, sometimes the bracketed content extends over more than one translation unit, so that the matching closing bracket is in later unit. In this case you need to balance brackets in both units, but you can't simply add bracket characters without changing the meaning or formatting, so you must must comment out the added bracket character, like this<br />
<br />
{{Input|1=<nowiki><!--}}-->{{Info|1=Beginning of long info box... </nowiki>}}<br />
<br />
and in a later unit<br />
<br />
{{Input|1=<nowiki> ...end of long info box}}<!--{{--></nowiki>}}<br />
<br />
If the offending bracket is part of a smiley, please replace it with an emoticon icon. For the standard smiley, <!--(-->:-), you can use the template <nowiki>{{Smiley}}</nowiki><br />
<br />
Please also correct the original page so other translators won't have the same problem, or leave a message on the discussion page.<br />
<br />
=== Language Statistics discrepancies === <br />
<br />
You may notice some slight discrepancy between the percentages stated on your LanguageStats page and the percentage on the language bar. This is normal. LanguageStats compares only the number of messages that are untranslated or outdated. The language bar statistic tries to be more intelligent. For instance, in one page (100 messages) 8 messages had a small (re-branding-releated) change, in each case, a single word was involved. There was 8% difference between the two statistics, since it was a substantial proportion of the messages, but a small proportion of the whole translation.<br />
<br />
=== If you use the Chromium or Chrome browser.... === <br />
<br />
Be aware that there seems to be some sort of caching problem on the Chromium browser. I have noticed that even with forced refreshes, sometimes statistics do not show up as they should (I have seen other things affected, too), yet if I open the same page in Firefox I see the correct stats.<br />
<br />
== Also See == <br />
<br />
* [http://translatewiki.net/wiki/Translating:Page_translation_feature#Translators]<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Translate_a_Page/1/cs&diff=63558Translations:Translate a Page/1/cs2011-08-11T21:24:46Z<p>PingusPepan: Created page with "== Dostupné nástroje =="</p>
<hr />
<div>== Dostupné nástroje ==</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translate_a_Page/cs&diff=63557Translate a Page/cs2011-08-11T21:24:32Z<p>PingusPepan: Created page with "Přeložit stránku"</p>
<hr />
<div><languages /><br />
<br />
== Available Tools == <br />
<br />
* [[Special:myLanguage/Translation Workflow|Translation Workflow]] describes the workflow to migrate to the new translation system<br />
<br />
== Workflow == <br />
<br />
* Request addition to the Translator group:<br />
** Click on [[Special:myLanguage/Translator Account|Get a Translator Account]] in the sidebar<br />
** Click on the <menuchoice>Edit</menuchoice> icon [[Image:Userbase-edit.png|14px]] and enter your username, the language you want to translate for and whether you intend to translate off-line<br />
** Use <menuchoice>Save page</menuchoice> to save the information<br />
<br />
* When your user has been added to the group (you should get an notification), click on [[Special:LanguageStats|Start Translating]] in the sidebar<br />
<br />
* Enter the language you want to translate to in <menuchoice>Language code</menuchoice> and click on <menuchoice>Go</menuchoice><br />
<br />
{{Note|Entering ''en'' (English) as the language code won't display any untranslated messages since all original content is written in English}}<br />
<br />
* Click on a page you want to translate in the list<br />
<br />
* In the '''Translate page''' set <menuchoice>View all untranslated message</menuchoice> in the first drop-down list<br />
<br />
* Check that the correct language code is showing<br />
<br />
* In the <menuchoice>Navigation</menuchoice> section, click on the link to the left of the message you want to translate<br />
<br />
* Enter the translation - a Google translation is provided for reference, but your own translation is usually preferred.<br />
<br />
* Click on <menuchoice>Save and open next</menuchoice> to continue with the next message or <menuchoice>Save page</menuchoice> to save the translation if you wish to stop working.<br />
<br />
{{Warning|1=Do not create a localized page variant manually (by entering pagename/langcode and trying to translate the original). This will mess up the translation system and no translation will be shown at all.}}<br />
<br />
== Hints and Tips == <br />
<br />
=== Image display instructions === <br />
<br />
A typical example is <nowiki>[[Image:Plasma-kickoff.jpg|right|160px]]</nowiki>. The whole of this is a system instruction on how to display the image. None of it is translated.<br />
<br />
=== Category statements ===<br />
<br />
In this context, think of the word "Category" as a system word which therefore should not be translated. For example, <nowiki>[[Category:Administration]]</nowiki> would become <nowiki>[[Category:Administrasi/id]]</nowiki><br />
<br />
For consistency,UserBase has lists of approved translations of categories. Translation teams may find a similar list useful. Such tables can be seen at [{{UB}}Translation_Help_Needed Translation Help Needed]. Please request help if you need it.<br />
<br />
=== Links to other pages on TechBase === <br />
<br />
These take the form <nowiki>[[Special:myLanguage/Other page|link text]]</nowiki> The link should remain untranslated, whereas the link text should always be translated. If no link text is present, please add suitable (translated) link text.<br />
<br />
Note: "myLanguage" will try to load the translated version of the link in the language you have set in your user preferences. If it fails to load it will just load the English original, so it is safe to use it for any internal link.<br />
<br />
=== Links to external sites === <br />
<br />
These take the form <nowiki>[http://example.com link text]</nowiki> Like the internal links, retain the actual link and translate the link text.<br />
<br />
=== Links in the Sidebar ===<br />
<br />
Instructions for translating those sidebar links can be found at [[Modifying_the_Sidebar#Translating_Sidebar_Items]]<br />
<br />
<br />
=== Info-boxes === <br />
<br />
These generally consist of a header word "Information" and an editable information text. If the word "Information" is not recognizable in your language you may need a localized version of the template. Please ask if you need help with this.<br />
<br />
=== Translated units are marked as fuzzy === <br />
<br />
Sometimes it may happen that you have translated a page, but the translation is marked as incomplete. Certain errors in the markup of the original page can cause this. The most common type of error is the appearance of unbalanced brackets or parentheses. The translation system requires that all opening brackets ('[', '{' or '(' ) have a matching closing bracket (']', '}' or ')' ) in the same translation unit, otherwise the translation is considered incomplete.<br />
<br />
The same rule is not enforced by the wiki software, so it is easy for writers to miss those mistakes. If a bracket character is simply missing, just add it. However, sometimes the bracketed content extends over more than one translation unit, so that the matching closing bracket is in later unit. In this case you need to balance brackets in both units, but you can't simply add bracket characters without changing the meaning or formatting, so you must must comment out the added bracket character, like this<br />
<br />
{{Input|1=<nowiki><!--}}-->{{Info|1=Beginning of long info box... </nowiki>}}<br />
<br />
and in a later unit<br />
<br />
{{Input|1=<nowiki> ...end of long info box}}<!--{{--></nowiki>}}<br />
<br />
If the offending bracket is part of a smiley, please replace it with an emoticon icon. For the standard smiley, <!--(-->:-), you can use the template <nowiki>{{Smiley}}</nowiki><br />
<br />
Please also correct the original page so other translators won't have the same problem, or leave a message on the discussion page.<br />
<br />
=== Language Statistics discrepancies === <br />
<br />
You may notice some slight discrepancy between the percentages stated on your LanguageStats page and the percentage on the language bar. This is normal. LanguageStats compares only the number of messages that are untranslated or outdated. The language bar statistic tries to be more intelligent. For instance, in one page (100 messages) 8 messages had a small (re-branding-releated) change, in each case, a single word was involved. There was 8% difference between the two statistics, since it was a substantial proportion of the messages, but a small proportion of the whole translation.<br />
<br />
=== If you use the Chromium or Chrome browser.... === <br />
<br />
Be aware that there seems to be some sort of caching problem on the Chromium browser. I have noticed that even with forced refreshes, sometimes statistics do not show up as they should (I have seen other things affected, too), yet if I open the same page in Firefox I see the correct stats.<br />
<br />
== Also See == <br />
<br />
* [http://translatewiki.net/wiki/Translating:Page_translation_feature#Translators]<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Translate_a_Page/Page_display_title/cs&diff=63556Translations:Translate a Page/Page display title/cs2011-08-11T21:24:32Z<p>PingusPepan: Created page with "Přeložit stránku"</p>
<hr />
<div>Přeložit stránku</div>PingusPepanhttps://techbase.kde.org/index.php?title=MediaWiki:Tb-trans-tool/cs&diff=63555MediaWiki:Tb-trans-tool/cs2011-08-11T21:22:19Z<p>PingusPepan: Created page with "Statistiky překladů"</p>
<hr />
<div>Statistiky překladů</div>PingusPepanhttps://techbase.kde.org/index.php?title=MediaWiki:Tb-offline-trans/cs&diff=63554MediaWiki:Tb-offline-trans/cs2011-08-11T21:22:01Z<p>PingusPepan: Created page with "Off-line překlad"</p>
<hr />
<div>Off-line překlad</div>PingusPepanhttps://techbase.kde.org/index.php?title=MediaWiki:Tb-trans-page/cs&diff=63553MediaWiki:Tb-trans-page/cs2011-08-11T21:21:49Z<p>PingusPepan: Created page with "Přeložit stránku"</p>
<hr />
<div>Přeložit stránku</div>PingusPepanhttps://techbase.kde.org/index.php?title=MediaWiki:Tb-get-trans-account/cs&diff=63552MediaWiki:Tb-get-trans-account/cs2011-08-11T21:21:27Z<p>PingusPepan: Created page with "Získejte překladatelský účet"</p>
<hr />
<div>Získejte překladatelský účet</div>PingusPepanhttps://techbase.kde.org/index.php?title=MediaWiki:Tb-development/cs&diff=63551MediaWiki:Tb-development/cs2011-08-11T21:20:52Z<p>PingusPepan: Created page with "Vývoj"</p>
<hr />
<div>Vývoj</div>PingusPepanhttps://techbase.kde.org/index.php?title=MediaWiki:Tb-getting-started/cs&diff=63550MediaWiki:Tb-getting-started/cs2011-08-11T21:20:47Z<p>PingusPepan: Created page with "Začínáme"</p>
<hr />
<div>Začínáme</div>PingusPepanhttps://techbase.kde.org/index.php?title=MediaWiki:Tb-projects/cs&diff=63549MediaWiki:Tb-projects/cs2011-08-11T21:19:38Z<p>PingusPepan: Created page with "Projekty"</p>
<hr />
<div>Projekty</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Off-line_Translation/Page_display_title/cs&diff=63548Translations:Off-line Translation/Page display title/cs2011-08-11T21:17:42Z<p>PingusPepan: Created page with "Off-line překlad"</p>
<hr />
<div>Off-line překlad</div>PingusPepanhttps://techbase.kde.org/index.php?title=Off-line_Translation/cs&diff=63547Off-line Translation/cs2011-08-11T21:17:18Z<p>PingusPepan: Created page with "===Import nového překladu==="</p>
<hr />
<div><languages /><br />
<br />
It is assumed that if you intend translating pages off-line you have some experience with '''Lokalize''' or a similar tool, therefore this page only addresses the on-line part of the process, the part that is carried out within TechBase.<br />
<br />
== Workflow == <br />
<br />
* Request addition to the Translator group:<br />
** Click on [[Special:myLanguage/Translator Account|Get a Translator Account]] in the sidebar<br />
** Click on the <menuchoice>Edit</menuchoice> tab and enter your username, the language you want to translate for and if you intend to translate off-line<br />
** Use <menuchoice>Save page</menuchoice> to save the information<br />
* When your user has been added to the group (you should get an e-mail notification), click on [[Special:LanguageStats|Start Translating]] in the sidebar<br />
* Enter the language you want to translate to in <menuchoice>Language code </menuchoice> and click on <menuchoice>Go</menuchoice> (You can select to suppress pages that are 100% complete.)<br />
* Choose your page to work on, from the list presented - this will take you to the tool where you choose on-line or off-line translation.<br />
* In order to reduce the risk of edit conflicts, upload your work frequently. You can continue to work on other sections from your downloaded file - import will know which sections are new.<br />
<br />
===Export stránky=== <br />
<br />
* The top combi-box <menuchoice>I want to...</menuchoice> should be set to <menuchoice>Export translation in Gettext format</menuchoice>.<br />
* Check that the page-name and language are correctly set.<br />
* <menuchoice>Go</menuchoice> completes the export.<br />
<br />
===Import nového překladu=== <br />
<br />
Initially you are requested to send the translated file to us. Here is the procedure:<br />
<br />
* Use the <menuchoice>Upload file</menuchoice> link in the sidebar to import your file.<br />
* Place a message on [[New Imports]] giving the filename of the upload.<br />
* Once we have confirmed that there are no problems we will show you how to upload your own future translations.<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Off-line_Translation/6/cs&diff=63546Translations:Off-line Translation/6/cs2011-08-11T21:17:18Z<p>PingusPepan: Created page with "===Import nového překladu==="</p>
<hr />
<div>===Import nového překladu===</div>PingusPepanhttps://techbase.kde.org/index.php?title=Off-line_Translation/cs&diff=63545Off-line Translation/cs2011-08-11T21:17:05Z<p>PingusPepan: Created page with "===Export stránky==="</p>
<hr />
<div><languages /><br />
<br />
It is assumed that if you intend translating pages off-line you have some experience with '''Lokalize''' or a similar tool, therefore this page only addresses the on-line part of the process, the part that is carried out within TechBase.<br />
<br />
== Workflow == <br />
<br />
* Request addition to the Translator group:<br />
** Click on [[Special:myLanguage/Translator Account|Get a Translator Account]] in the sidebar<br />
** Click on the <menuchoice>Edit</menuchoice> tab and enter your username, the language you want to translate for and if you intend to translate off-line<br />
** Use <menuchoice>Save page</menuchoice> to save the information<br />
* When your user has been added to the group (you should get an e-mail notification), click on [[Special:LanguageStats|Start Translating]] in the sidebar<br />
* Enter the language you want to translate to in <menuchoice>Language code </menuchoice> and click on <menuchoice>Go</menuchoice> (You can select to suppress pages that are 100% complete.)<br />
* Choose your page to work on, from the list presented - this will take you to the tool where you choose on-line or off-line translation.<br />
* In order to reduce the risk of edit conflicts, upload your work frequently. You can continue to work on other sections from your downloaded file - import will know which sections are new.<br />
<br />
===Export stránky=== <br />
<br />
* The top combi-box <menuchoice>I want to...</menuchoice> should be set to <menuchoice>Export translation in Gettext format</menuchoice>.<br />
* Check that the page-name and language are correctly set.<br />
* <menuchoice>Go</menuchoice> completes the export.<br />
<br />
===Import the new translation=== <br />
<br />
Initially you are requested to send the translated file to us. Here is the procedure:<br />
<br />
* Use the <menuchoice>Upload file</menuchoice> link in the sidebar to import your file.<br />
* Place a message on [[New Imports]] giving the filename of the upload.<br />
* Once we have confirmed that there are no problems we will show you how to upload your own future translations.<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Off-line_Translation/4/cs&diff=63544Translations:Off-line Translation/4/cs2011-08-11T21:17:05Z<p>PingusPepan: Created page with "===Export stránky==="</p>
<hr />
<div>===Export stránky===</div>PingusPepanhttps://techbase.kde.org/index.php?title=Typographical_Guidelines/cs&diff=63343Typographical Guidelines/cs2011-08-03T11:32:22Z<p>PingusPepan: Created page with "== Seznamy =="</p>
<hr />
<div><languages /><br />
<br />
''There is a separate pages explaining [[Special:myLanguage/Toolbox|general syntax]] with example code.''<br />
<br />
Adhering to these typographic guidelines will ensure that your documentation can be accurately and easily exported for translation purposes.<br />
<br />
== Tučný text == <br />
<br />
Use bold text to highlight<br />
* Window titles<br />
* Common labels that are not user-configurable<br />
* Icon captions<br />
* Program names<br />
<br />
For example:<br />
<br />
* Highlighting a selection of text will copy it to '''Klipper'''.<br />
<br />
== Kurzíva == <br />
<br />
Use italic text to emphasise <br />
* Words or phrases as in general writing.<br />
* Titles when referencing other works.<br />
* The first use of an unfamiliar word.<br />
<br />
Some examples:<br />
* ''Save your work at this point.''<br />
* Details can be found in ''Samba 3 by Example''....<br />
* KDE Manuals are in ''Docbook'' format.<br />
<br />
{{Tip|1=''Programs'' are launched by users, ''components'' are used by programs}}<br />
<br />
== Combined Bold and Italic Text == <br />
<br />
Use this combination for replaceable or variable text.<br />
<br />
Some examples:<br />
* To connect to your remote server, type <code>ssh</code> '''''username@domain.name''''' in '''Konsole'''.<br />
* In rpm-based distributions, the command <code>rpm -q</code> '''''packagename''''' will result in '''''package-version-release'''''.<br />
<br />
== Mono-spaced Text == <br />
<br />
Code should be presented in mono-spaced text, usually boxed, as shown below. Input text will be on a pale yellow background. For output text, the background colour will be violet-grey. <br />
<br />
* Code, whether single lines or blocks, use templates to ensure consistency<br />
<br />
* Use the Input template like this: {{Input|1=<nowiki>{{Input|1=<nowiki><br />
qdbus org.kde.NepomukServer /nepomukserver org.kde.NepomukServer.quit<br />
rm -r ~/.kde/share/apps/nepomuk<br />
rm -r ~/.kde4/share/apps/nepomuk<br />
nepomukserver&lt;/nowiki>}}</nowiki>}} This will display like this: {{Input|1=<nowiki><br />
qdbus org.kde.NepomukServer /nepomukserver org.kde.NepomukServer.quit<br />
rm -r ~/.kde/share/apps/nepomuk<br />
rm -r ~/.kde4/share/apps/nepomuk<br />
nepomukserver</nowiki>}}<br />
<br />
<br />
* Output works the same way: {{Output|1=<nowiki>{{Output|1=<nowiki>terminal output <br />
is also shown as code, <br />
but on a grey background&lt;/nowiki>}}</nowiki>}} which displays as {{Output|1=<nowiki>terminal output <br />
is also shown as code, <br />
but on a grey background</nowiki>}}<br />
<br />
{{Note|1=Note the use of <code><nowiki>1=<nowiki> some text &lt;/nowiki></nowiki></code> to avoid situations that break the display format}}<br />
<br />
* Starting an Input or Output template on a new line will break the display format if it is within lists. Simply continue on the same line if you need to correct this.<br />
<br />
* You can also combine input/output areas with [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi GeSHi syntaxhiglighting]. An input area like this {{Input|1=<nowiki>{{Input|<syntaxhighlight lang="php" line><br />
# Initialise common code<br />
$preIP = dirname( __FILE__ );<br />
require_once( "$preIP/includes/WebStart.php" );<br />
</syntaxhighlight>}}</nowiki><br />
}} will result in {{Input|<syntaxhighlight lang="php" line><br />
# Initialise common code<br />
$preIP = dirname( __FILE__ );<br />
require_once( "$preIP/includes/WebStart.php" );<br />
</syntaxhighlight>}}<br />
<br />
* Single code words can be kept in-line by using {{Input|1=<nowiki><code></code></nowiki>}} It will <code>display</code> like this.<br />
<br />
* {{Input|1=<nowiki>&lt;tt> &lt;/tt></nowiki>}} is useful for displaying filenames and paths. This looks like this: <tt> a/path/to/here </tt><br />
<br />
== Block Quotes == <br />
<br />
The tags <nowiki><blockquote></nowiki> and <nowiki></blockquote></nowiki> should be used when quoting other works or other pages. This produces a proportional italic font, with some padding.<br />
<br />
<blockquote>Here is an example of the display that you get by using the blockquote tags.</blockquote><br />
<br />
== Text in Section Headers == <br />
<br />
Even though the criteria above may be met, do not use Bold text in section headers or in links.<br />
<br />
== Text in Information, Note, Tip or Warning Templates == <br />
<br />
Bold text should be avoided in the text within these templates. Italic text for emphasis may still be used - use sparingly for maximum effect.<br />
<br />
== Seznamy == <br />
<br />
You can have various kinds of lists in your pages &mdash; bulleted, numbered or itemized. Find details on the [[Special:myLanguage/Toolbox#Bulleted Lists|Toolbox]] page.<br />
<br />
== Keeping things together == <br />
<br />
After your text is written some markup is automatically added by the translation system. This means that whenever it sees a blank line, it starts a new unit. When your text is presented to translators, they typically see it one unit at a time, so it is important not to leave a blank lines in the middle of something that should be treated as a unit. Normally an entire paragraph should be kept in a single unit; and under no circumstance should a sentence be split between units!<br />
<br />
If you need a linebreak in the middle of a section, the preferred way to achieve this is without breaking units is to use <nowiki><br /></nowiki> at the end of the line where you want to break to occur (not on a new line). If you need space between the lines add <nowiki><br /><br /></nowiki>.<br />
<br />
== Unbalanced brackets == <br />
<br />
<!--}}-->The translation system marks any translated unit as incompletely translated if it contains any kind of unbalanced brackets. If you need to have unbalanced brackets in your text, please add a balancing bracket in a comment tag, like this:<br /><br />
{{Input|1=<br />
<nowiki><!-- }} -->{{ A line <br />
<br />
Another line}}<!-- {{ --></nowiki><br />
}}<!--{{--><br />
This goes for all kinds of brackets, even ordinary parentheses. (Of course it is normally better to avoid blank lines within a mark up unit - see [[Special:myLanguage/Typographical_Guidelines#Keeping_things_together|Keeping things together]].)<br />
<br />
== Special Tags == <br />
<br />
* <nowiki> <keycap></nowiki> and <nowiki> </keycap> </nowiki> denote (keyboard) key names e.g. <keycap>Enter</keycap><br />
* <nowiki><keycap></keycap></nowiki> can also be used around groups of keys to be used concurrently, e.g. <keycap>Ctrl + Alt + F1</keycap> to launch a virtual terminal. (Note that "(space)+(space)" is used to link keys to be pressed concurrently).<br />
* Sequences of menu choices should use <nowiki> <menuchoice> </nowiki>and <nowiki> </menuchoice> </nowiki> for example <menuchoice> View -> Message List -> Aggregation -> Standard Mailing List </menuchoice><br />
* In general, if the user needs to choose an element, even if it is not in a menu, the <nowiki><menuchoice></menuchoiсe></nowiki> markup should be used.<br />
<br />
== The Problematic Pipe Symbol ==<br />
<br />
In some situations the pipe symbol cannot be used - for instance when giving parameters in a template - as it has a system meaning. In such cases please use <nowiki>{{!}}</nowiki>. For example, if you want to display a command line containing the pipe character using the <nowiki>{{Input|...}}</nowiki> template, the simplest way to do it is this: <code><nowiki>{{Input|1=cmd1 {{!}} cnd2}}</nowiki></code> which displays {{Input|1=cmd1 {{!}} cnd2}}<br />
<br />
<br />If you just write <code><nowiki>{{Input|1=cmd1 | cnd2}}</nowiki></code> you get instead {{Input|1=cmd1 | cnd2}}<br />
the problem being, that <code>cmd2</code> is seen as a second parameter to the template, which in this case is not used.<br />
<br />
In many cases, you can also enclose the text containing the pipe character between <nowiki><nowiki>...</nowiki> </nowiki> tags, like this <code><nowiki>{{Input|1=<nowiki>cmd1 | cmd2</nowiki></nowiki><nowiki>}}</nowiki></code>, which also displays {{Input|1=<nowiki>cmd1 | cmd2</nowiki>}}<br />
<br />
== Translatable Content == <br />
<br />
Everything that is translatable is contained within <nowiki><translate> and </translate></nowiki> tags. In most cases any images should be contained within the translatable section, as it is sometimes necessary to use localised versions of the images to explain a point. The rule of thumb is "If in doubt, include it!".<br />
<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Typographical_Guidelines/31/cs&diff=63342Translations:Typographical Guidelines/31/cs2011-08-03T11:32:22Z<p>PingusPepan: Created page with "== Seznamy =="</p>
<hr />
<div>== Seznamy ==</div>PingusPepanhttps://techbase.kde.org/index.php?title=Typographical_Guidelines/cs&diff=63341Typographical Guidelines/cs2011-08-03T11:32:09Z<p>PingusPepan: Created page with "== Kurzíva =="</p>
<hr />
<div><languages /><br />
<br />
''There is a separate pages explaining [[Special:myLanguage/Toolbox|general syntax]] with example code.''<br />
<br />
Adhering to these typographic guidelines will ensure that your documentation can be accurately and easily exported for translation purposes.<br />
<br />
== Tučný text == <br />
<br />
Use bold text to highlight<br />
* Window titles<br />
* Common labels that are not user-configurable<br />
* Icon captions<br />
* Program names<br />
<br />
For example:<br />
<br />
* Highlighting a selection of text will copy it to '''Klipper'''.<br />
<br />
== Kurzíva == <br />
<br />
Use italic text to emphasise <br />
* Words or phrases as in general writing.<br />
* Titles when referencing other works.<br />
* The first use of an unfamiliar word.<br />
<br />
Some examples:<br />
* ''Save your work at this point.''<br />
* Details can be found in ''Samba 3 by Example''....<br />
* KDE Manuals are in ''Docbook'' format.<br />
<br />
{{Tip|1=''Programs'' are launched by users, ''components'' are used by programs}}<br />
<br />
== Combined Bold and Italic Text == <br />
<br />
Use this combination for replaceable or variable text.<br />
<br />
Some examples:<br />
* To connect to your remote server, type <code>ssh</code> '''''username@domain.name''''' in '''Konsole'''.<br />
* In rpm-based distributions, the command <code>rpm -q</code> '''''packagename''''' will result in '''''package-version-release'''''.<br />
<br />
== Mono-spaced Text == <br />
<br />
Code should be presented in mono-spaced text, usually boxed, as shown below. Input text will be on a pale yellow background. For output text, the background colour will be violet-grey. <br />
<br />
* Code, whether single lines or blocks, use templates to ensure consistency<br />
<br />
* Use the Input template like this: {{Input|1=<nowiki>{{Input|1=<nowiki><br />
qdbus org.kde.NepomukServer /nepomukserver org.kde.NepomukServer.quit<br />
rm -r ~/.kde/share/apps/nepomuk<br />
rm -r ~/.kde4/share/apps/nepomuk<br />
nepomukserver&lt;/nowiki>}}</nowiki>}} This will display like this: {{Input|1=<nowiki><br />
qdbus org.kde.NepomukServer /nepomukserver org.kde.NepomukServer.quit<br />
rm -r ~/.kde/share/apps/nepomuk<br />
rm -r ~/.kde4/share/apps/nepomuk<br />
nepomukserver</nowiki>}}<br />
<br />
<br />
* Output works the same way: {{Output|1=<nowiki>{{Output|1=<nowiki>terminal output <br />
is also shown as code, <br />
but on a grey background&lt;/nowiki>}}</nowiki>}} which displays as {{Output|1=<nowiki>terminal output <br />
is also shown as code, <br />
but on a grey background</nowiki>}}<br />
<br />
{{Note|1=Note the use of <code><nowiki>1=<nowiki> some text &lt;/nowiki></nowiki></code> to avoid situations that break the display format}}<br />
<br />
* Starting an Input or Output template on a new line will break the display format if it is within lists. Simply continue on the same line if you need to correct this.<br />
<br />
* You can also combine input/output areas with [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi GeSHi syntaxhiglighting]. An input area like this {{Input|1=<nowiki>{{Input|<syntaxhighlight lang="php" line><br />
# Initialise common code<br />
$preIP = dirname( __FILE__ );<br />
require_once( "$preIP/includes/WebStart.php" );<br />
</syntaxhighlight>}}</nowiki><br />
}} will result in {{Input|<syntaxhighlight lang="php" line><br />
# Initialise common code<br />
$preIP = dirname( __FILE__ );<br />
require_once( "$preIP/includes/WebStart.php" );<br />
</syntaxhighlight>}}<br />
<br />
* Single code words can be kept in-line by using {{Input|1=<nowiki><code></code></nowiki>}} It will <code>display</code> like this.<br />
<br />
* {{Input|1=<nowiki>&lt;tt> &lt;/tt></nowiki>}} is useful for displaying filenames and paths. This looks like this: <tt> a/path/to/here </tt><br />
<br />
== Block Quotes == <br />
<br />
The tags <nowiki><blockquote></nowiki> and <nowiki></blockquote></nowiki> should be used when quoting other works or other pages. This produces a proportional italic font, with some padding.<br />
<br />
<blockquote>Here is an example of the display that you get by using the blockquote tags.</blockquote><br />
<br />
== Text in Section Headers == <br />
<br />
Even though the criteria above may be met, do not use Bold text in section headers or in links.<br />
<br />
== Text in Information, Note, Tip or Warning Templates == <br />
<br />
Bold text should be avoided in the text within these templates. Italic text for emphasis may still be used - use sparingly for maximum effect.<br />
<br />
== Lists == <br />
<br />
You can have various kinds of lists in your pages &mdash; bulleted, numbered or itemized. Find details on the [[Special:myLanguage/Toolbox#Bulleted Lists|Toolbox]] page.<br />
<br />
== Keeping things together == <br />
<br />
After your text is written some markup is automatically added by the translation system. This means that whenever it sees a blank line, it starts a new unit. When your text is presented to translators, they typically see it one unit at a time, so it is important not to leave a blank lines in the middle of something that should be treated as a unit. Normally an entire paragraph should be kept in a single unit; and under no circumstance should a sentence be split between units!<br />
<br />
If you need a linebreak in the middle of a section, the preferred way to achieve this is without breaking units is to use <nowiki><br /></nowiki> at the end of the line where you want to break to occur (not on a new line). If you need space between the lines add <nowiki><br /><br /></nowiki>.<br />
<br />
== Unbalanced brackets == <br />
<br />
<!--}}-->The translation system marks any translated unit as incompletely translated if it contains any kind of unbalanced brackets. If you need to have unbalanced brackets in your text, please add a balancing bracket in a comment tag, like this:<br /><br />
{{Input|1=<br />
<nowiki><!-- }} -->{{ A line <br />
<br />
Another line}}<!-- {{ --></nowiki><br />
}}<!--{{--><br />
This goes for all kinds of brackets, even ordinary parentheses. (Of course it is normally better to avoid blank lines within a mark up unit - see [[Special:myLanguage/Typographical_Guidelines#Keeping_things_together|Keeping things together]].)<br />
<br />
== Special Tags == <br />
<br />
* <nowiki> <keycap></nowiki> and <nowiki> </keycap> </nowiki> denote (keyboard) key names e.g. <keycap>Enter</keycap><br />
* <nowiki><keycap></keycap></nowiki> can also be used around groups of keys to be used concurrently, e.g. <keycap>Ctrl + Alt + F1</keycap> to launch a virtual terminal. (Note that "(space)+(space)" is used to link keys to be pressed concurrently).<br />
* Sequences of menu choices should use <nowiki> <menuchoice> </nowiki>and <nowiki> </menuchoice> </nowiki> for example <menuchoice> View -> Message List -> Aggregation -> Standard Mailing List </menuchoice><br />
* In general, if the user needs to choose an element, even if it is not in a menu, the <nowiki><menuchoice></menuchoiсe></nowiki> markup should be used.<br />
<br />
== The Problematic Pipe Symbol ==<br />
<br />
In some situations the pipe symbol cannot be used - for instance when giving parameters in a template - as it has a system meaning. In such cases please use <nowiki>{{!}}</nowiki>. For example, if you want to display a command line containing the pipe character using the <nowiki>{{Input|...}}</nowiki> template, the simplest way to do it is this: <code><nowiki>{{Input|1=cmd1 {{!}} cnd2}}</nowiki></code> which displays {{Input|1=cmd1 {{!}} cnd2}}<br />
<br />
<br />If you just write <code><nowiki>{{Input|1=cmd1 | cnd2}}</nowiki></code> you get instead {{Input|1=cmd1 | cnd2}}<br />
the problem being, that <code>cmd2</code> is seen as a second parameter to the template, which in this case is not used.<br />
<br />
In many cases, you can also enclose the text containing the pipe character between <nowiki><nowiki>...</nowiki> </nowiki> tags, like this <code><nowiki>{{Input|1=<nowiki>cmd1 | cmd2</nowiki></nowiki><nowiki>}}</nowiki></code>, which also displays {{Input|1=<nowiki>cmd1 | cmd2</nowiki>}}<br />
<br />
== Translatable Content == <br />
<br />
Everything that is translatable is contained within <nowiki><translate> and </translate></nowiki> tags. In most cases any images should be contained within the translatable section, as it is sometimes necessary to use localised versions of the images to explain a point. The rule of thumb is "If in doubt, include it!".<br />
<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Typographical_Guidelines/7/cs&diff=63340Translations:Typographical Guidelines/7/cs2011-08-03T11:32:09Z<p>PingusPepan: Created page with "== Kurzíva =="</p>
<hr />
<div>== Kurzíva ==</div>PingusPepanhttps://techbase.kde.org/index.php?title=Typographical_Guidelines/cs&diff=63339Typographical Guidelines/cs2011-08-03T11:31:56Z<p>PingusPepan: Created page with "== Tučný text =="</p>
<hr />
<div><languages /><br />
<br />
''There is a separate pages explaining [[Special:myLanguage/Toolbox|general syntax]] with example code.''<br />
<br />
Adhering to these typographic guidelines will ensure that your documentation can be accurately and easily exported for translation purposes.<br />
<br />
== Tučný text == <br />
<br />
Use bold text to highlight<br />
* Window titles<br />
* Common labels that are not user-configurable<br />
* Icon captions<br />
* Program names<br />
<br />
For example:<br />
<br />
* Highlighting a selection of text will copy it to '''Klipper'''.<br />
<br />
== Italic Text == <br />
<br />
Use italic text to emphasise <br />
* Words or phrases as in general writing.<br />
* Titles when referencing other works.<br />
* The first use of an unfamiliar word.<br />
<br />
Some examples:<br />
* ''Save your work at this point.''<br />
* Details can be found in ''Samba 3 by Example''....<br />
* KDE Manuals are in ''Docbook'' format.<br />
<br />
{{Tip|1=''Programs'' are launched by users, ''components'' are used by programs}}<br />
<br />
== Combined Bold and Italic Text == <br />
<br />
Use this combination for replaceable or variable text.<br />
<br />
Some examples:<br />
* To connect to your remote server, type <code>ssh</code> '''''username@domain.name''''' in '''Konsole'''.<br />
* In rpm-based distributions, the command <code>rpm -q</code> '''''packagename''''' will result in '''''package-version-release'''''.<br />
<br />
== Mono-spaced Text == <br />
<br />
Code should be presented in mono-spaced text, usually boxed, as shown below. Input text will be on a pale yellow background. For output text, the background colour will be violet-grey. <br />
<br />
* Code, whether single lines or blocks, use templates to ensure consistency<br />
<br />
* Use the Input template like this: {{Input|1=<nowiki>{{Input|1=<nowiki><br />
qdbus org.kde.NepomukServer /nepomukserver org.kde.NepomukServer.quit<br />
rm -r ~/.kde/share/apps/nepomuk<br />
rm -r ~/.kde4/share/apps/nepomuk<br />
nepomukserver&lt;/nowiki>}}</nowiki>}} This will display like this: {{Input|1=<nowiki><br />
qdbus org.kde.NepomukServer /nepomukserver org.kde.NepomukServer.quit<br />
rm -r ~/.kde/share/apps/nepomuk<br />
rm -r ~/.kde4/share/apps/nepomuk<br />
nepomukserver</nowiki>}}<br />
<br />
<br />
* Output works the same way: {{Output|1=<nowiki>{{Output|1=<nowiki>terminal output <br />
is also shown as code, <br />
but on a grey background&lt;/nowiki>}}</nowiki>}} which displays as {{Output|1=<nowiki>terminal output <br />
is also shown as code, <br />
but on a grey background</nowiki>}}<br />
<br />
{{Note|1=Note the use of <code><nowiki>1=<nowiki> some text &lt;/nowiki></nowiki></code> to avoid situations that break the display format}}<br />
<br />
* Starting an Input or Output template on a new line will break the display format if it is within lists. Simply continue on the same line if you need to correct this.<br />
<br />
* You can also combine input/output areas with [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi GeSHi syntaxhiglighting]. An input area like this {{Input|1=<nowiki>{{Input|<syntaxhighlight lang="php" line><br />
# Initialise common code<br />
$preIP = dirname( __FILE__ );<br />
require_once( "$preIP/includes/WebStart.php" );<br />
</syntaxhighlight>}}</nowiki><br />
}} will result in {{Input|<syntaxhighlight lang="php" line><br />
# Initialise common code<br />
$preIP = dirname( __FILE__ );<br />
require_once( "$preIP/includes/WebStart.php" );<br />
</syntaxhighlight>}}<br />
<br />
* Single code words can be kept in-line by using {{Input|1=<nowiki><code></code></nowiki>}} It will <code>display</code> like this.<br />
<br />
* {{Input|1=<nowiki>&lt;tt> &lt;/tt></nowiki>}} is useful for displaying filenames and paths. This looks like this: <tt> a/path/to/here </tt><br />
<br />
== Block Quotes == <br />
<br />
The tags <nowiki><blockquote></nowiki> and <nowiki></blockquote></nowiki> should be used when quoting other works or other pages. This produces a proportional italic font, with some padding.<br />
<br />
<blockquote>Here is an example of the display that you get by using the blockquote tags.</blockquote><br />
<br />
== Text in Section Headers == <br />
<br />
Even though the criteria above may be met, do not use Bold text in section headers or in links.<br />
<br />
== Text in Information, Note, Tip or Warning Templates == <br />
<br />
Bold text should be avoided in the text within these templates. Italic text for emphasis may still be used - use sparingly for maximum effect.<br />
<br />
== Lists == <br />
<br />
You can have various kinds of lists in your pages &mdash; bulleted, numbered or itemized. Find details on the [[Special:myLanguage/Toolbox#Bulleted Lists|Toolbox]] page.<br />
<br />
== Keeping things together == <br />
<br />
After your text is written some markup is automatically added by the translation system. This means that whenever it sees a blank line, it starts a new unit. When your text is presented to translators, they typically see it one unit at a time, so it is important not to leave a blank lines in the middle of something that should be treated as a unit. Normally an entire paragraph should be kept in a single unit; and under no circumstance should a sentence be split between units!<br />
<br />
If you need a linebreak in the middle of a section, the preferred way to achieve this is without breaking units is to use <nowiki><br /></nowiki> at the end of the line where you want to break to occur (not on a new line). If you need space between the lines add <nowiki><br /><br /></nowiki>.<br />
<br />
== Unbalanced brackets == <br />
<br />
<!--}}-->The translation system marks any translated unit as incompletely translated if it contains any kind of unbalanced brackets. If you need to have unbalanced brackets in your text, please add a balancing bracket in a comment tag, like this:<br /><br />
{{Input|1=<br />
<nowiki><!-- }} -->{{ A line <br />
<br />
Another line}}<!-- {{ --></nowiki><br />
}}<!--{{--><br />
This goes for all kinds of brackets, even ordinary parentheses. (Of course it is normally better to avoid blank lines within a mark up unit - see [[Special:myLanguage/Typographical_Guidelines#Keeping_things_together|Keeping things together]].)<br />
<br />
== Special Tags == <br />
<br />
* <nowiki> <keycap></nowiki> and <nowiki> </keycap> </nowiki> denote (keyboard) key names e.g. <keycap>Enter</keycap><br />
* <nowiki><keycap></keycap></nowiki> can also be used around groups of keys to be used concurrently, e.g. <keycap>Ctrl + Alt + F1</keycap> to launch a virtual terminal. (Note that "(space)+(space)" is used to link keys to be pressed concurrently).<br />
* Sequences of menu choices should use <nowiki> <menuchoice> </nowiki>and <nowiki> </menuchoice> </nowiki> for example <menuchoice> View -> Message List -> Aggregation -> Standard Mailing List </menuchoice><br />
* In general, if the user needs to choose an element, even if it is not in a menu, the <nowiki><menuchoice></menuchoiсe></nowiki> markup should be used.<br />
<br />
== The Problematic Pipe Symbol ==<br />
<br />
In some situations the pipe symbol cannot be used - for instance when giving parameters in a template - as it has a system meaning. In such cases please use <nowiki>{{!}}</nowiki>. For example, if you want to display a command line containing the pipe character using the <nowiki>{{Input|...}}</nowiki> template, the simplest way to do it is this: <code><nowiki>{{Input|1=cmd1 {{!}} cnd2}}</nowiki></code> which displays {{Input|1=cmd1 {{!}} cnd2}}<br />
<br />
<br />If you just write <code><nowiki>{{Input|1=cmd1 | cnd2}}</nowiki></code> you get instead {{Input|1=cmd1 | cnd2}}<br />
the problem being, that <code>cmd2</code> is seen as a second parameter to the template, which in this case is not used.<br />
<br />
In many cases, you can also enclose the text containing the pipe character between <nowiki><nowiki>...</nowiki> </nowiki> tags, like this <code><nowiki>{{Input|1=<nowiki>cmd1 | cmd2</nowiki></nowiki><nowiki>}}</nowiki></code>, which also displays {{Input|1=<nowiki>cmd1 | cmd2</nowiki>}}<br />
<br />
== Translatable Content == <br />
<br />
Everything that is translatable is contained within <nowiki><translate> and </translate></nowiki> tags. In most cases any images should be contained within the translatable section, as it is sometimes necessary to use localised versions of the images to explain a point. The rule of thumb is "If in doubt, include it!".<br />
<br />
<br />
[[Category:Translator_Help]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Typographical_Guidelines/3/cs&diff=63338Translations:Typographical Guidelines/3/cs2011-08-03T11:31:55Z<p>PingusPepan: Created page with "== Tučný text =="</p>
<hr />
<div>== Tučný text ==</div>PingusPepanhttps://techbase.kde.org/index.php?title=Policies/Kdelibs_Coding_Style/cs&diff=63337Policies/Kdelibs Coding Style/cs2011-08-03T11:30:24Z<p>PingusPepan: Created page with "Při použití astyle (>=2.01) musíte spustit následující příkaz:"</p>
<hr />
<div>This document describes the recommended coding style for kdelibs. Nobody is forced to use this style, but to have consistent formatting of the source code files it is recommended to make use of it.<br />
<br />
'''In short: Kdelibs coding style follows the Qt 4 coding style.'''<br />
<br />
== Odsazení ==<br />
* Bez tabulátorů<br />
* 4 mezery namísto jednoho tabulátoru<br />
<br />
== Variable declaration ==<br />
* Each variable declaration on a new line<br />
* Each new word in a variable name starts with a capital letter (so-called camelCase)<br />
* Avoid abbreviations<br />
* Take useful names. No short names, except:<br />
** Single character variable names can denote counters and temporary variables whose purpose is obvious<br />
** Variables and functions start with a lowercase letter<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
// špatně<br />
KProgressBar *prbar;<br />
QString prtxt, errstr;<br />
<br />
// správně<br />
KProgressBar *downloadProgressBar;<br />
QString progressText;<br />
QString errorString;<br />
</syntaxhighlight><br />
<br />
== Whitespace ==<br />
* Use blank lines to group statements<br />
* Use only one empty line<br />
* Use one space after each keyword<br />
* For pointers or references, use a single space before '*' or '&', but not after<br />
* No space after a cast<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
// špatně<br />
QString* myString;<br />
if(true){<br />
}<br />
<br />
// správně<br />
QString *myString;<br />
if (true) {<br />
}<br />
</syntaxhighlight><br />
<br />
== Braces ==<br />
As a base rule, the left curly brace goes on the same line as the start of the statement.<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
// špatně<br />
if (true)<br />
{<br />
}<br />
<br />
// správně<br />
if (true) {<br />
}<br />
</syntaxhighlight><br />
<br />
Exception: Function implementations, class, struct and namespace declarations always have the opening brace on the start of a line.<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
void debug(int i)<br />
{<br />
qDebug("foo: %i", i);<br />
}<br />
<br />
class Debug<br />
{<br />
};<br />
</syntaxhighlight><br />
<br />
Use curly braces even when the body of a conditional statement contains only one line.<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
// špatně<br />
if (true)<br />
return true;<br />
<br />
for (int i = 0; i < 10; ++i)<br />
qDebug("%i", i);<br />
<br />
// správně<br />
if (true) {<br />
return true;<br />
}<br />
<br />
for (int i = 0; i < 10; ++i) {<br />
qDebug("%i", i);<br />
}<br />
</syntaxhighlight><br />
<br />
== Switch statements ==<br />
Case labels are on the same column as the switch<br />
<br />
Example:<br />
<syntaxhighlight lang="cpp-qt"><br />
switch (myEnum) {<br />
case Value1:<br />
doSomething();<br />
break;<br />
case Value2:<br />
doSomethingElse();<br />
// fall through<br />
default:<br />
defaultHandling();<br />
break;<br />
}<br />
</syntaxhighlight><br />
<br />
== Line breaks ==<br />
Try to keep lines shorter than 100 characters, inserting line breaks as necessary.<br />
<br />
== Qt Includes ==<br />
* If you add #includes for Qt classes, use both the module and class name. This allows library code to be used by applications without excessive compiler include paths.<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
// špatně<br />
#include <QString><br />
<br />
// správně<br />
#include <QtCore/QString><br />
</syntaxhighlight><br />
<br />
== Artistic Style (astyle) automatic code formatting ==<br />
You can use [http://astyle.sourceforge.net/ astyle] (>=1.23) to format code or to test if you have followed this document. Run the following command:<br />
<syntaxhighlight lang="text"><br />
astyle --indent=spaces=4 --brackets=linux \<br />
--indent-labels --pad-oper --unpad-paren \<br />
--one-line=keep-statements --convert-tabs \<br />
--indent-preprocessor \<br />
`find -type f -name '*.cpp'` `find -type f -name '*.cc'` `find -type f -name '*.h'`<br />
</syntaxhighlight><br />
<br />
Při použití astyle (>=2.01) musíte spustit následující příkaz:<br />
<syntaxhighlight lang="text"><br />
astyle --indent=spaces=4 --brackets=linux \<br />
--indent-labels --pad-oper --unpad-paren \<br />
--keep-one-line-statements --convert-tabs \<br />
--indent-preprocessor \<br />
`find -type f -name '*.cpp'` `find -type f -name '*.cc'` `find -type f -name '*.h'`<br />
</syntaxhighlight><br />
<br />
A related shell script could be found for unix in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/astyle-kdelibs kdesdk/scripts/astyle-kdelibs] and for windows in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/astyle-kdelibs.bat kdesdk/scripts/astyle-kdelibs.bat].<br />
<br />
== Emacs and Vim scripts ==<br />
The "scripts" directory in the kdesdk module contains, among other useful things, some useful additions to the Emacs and Vim text editors that make it easier to edit KDE code with them.<br />
<br />
=== Emacs ===<br />
The [http://websvn.kde.org/trunk/KDE/kdesdk/scripts/kde-emacs kde-emacs] directory contains a set of key bindings, macros and general useful code. It is compatible with both GNU Emacs and XEmacs.<br />
<br />
To start using kde-emacs, add the following to your .emacs:<br />
<br />
<syntaxhighlight lang="text"><br />
(add-to-list 'load-path "/path/to/kde-emacs")<br />
(require 'kde-emacs)<br />
</syntaxhighlight><br />
<br />
Many settings can be changed by editing the "kde-emacs" group via <tt>M-x customize-group</tt>.<br />
<br />
For more information, including what the key bindings are and what additional settings you could add to your .emacs, please check <tt>kde-emacs.el</tt> itself.<br />
<br />
=== Vim ===<br />
You can find a vim script in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/kde-devel-vim.vim kdesdk/scripts/kde-devel-vim.vim] that helps you to keep the coding style correct. In addition to defaulting to the kdelibs coding style it will automatically use the correct style for Solid and kdepim code. If you want to add rules for other projects feel free to add them in the SetCodingStyle function.<br />
<br />
To use the script, include it in your {{path|~/.vimrc}} like this:<br />
<syntaxhighlight lang="text"><br />
source /path/to/kde/sources/kdesdk/scripts/kde-devel-vim.vim<br />
</syntaxhighlight><br />
<br />
<br />
Document started by Urs Wolfer. Some parts of this document have been adopted from the Qt Coding Style document posted by Zack Rusin on kde-core-devel.<br />
<br />
[[Category:Policies]] [[Category:C++]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Policies/Kdelibs_Coding_Style/30/cs&diff=63336Translations:Policies/Kdelibs Coding Style/30/cs2011-08-03T11:30:24Z<p>PingusPepan: Created page with "Při použití astyle (>=2.01) musíte spustit následující příkaz:"</p>
<hr />
<div>Při použití astyle (>=2.01) musíte spustit následující příkaz:</div>PingusPepanhttps://techbase.kde.org/index.php?title=Policies/Kdelibs_Coding_Style/cs&diff=63335Policies/Kdelibs Coding Style/cs2011-08-03T11:29:47Z<p>PingusPepan: Created page with "// správně"</p>
<hr />
<div>This document describes the recommended coding style for kdelibs. Nobody is forced to use this style, but to have consistent formatting of the source code files it is recommended to make use of it.<br />
<br />
'''In short: Kdelibs coding style follows the Qt 4 coding style.'''<br />
<br />
== Odsazení ==<br />
* Bez tabulátorů<br />
* 4 mezery namísto jednoho tabulátoru<br />
<br />
== Variable declaration ==<br />
* Each variable declaration on a new line<br />
* Each new word in a variable name starts with a capital letter (so-called camelCase)<br />
* Avoid abbreviations<br />
* Take useful names. No short names, except:<br />
** Single character variable names can denote counters and temporary variables whose purpose is obvious<br />
** Variables and functions start with a lowercase letter<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
// špatně<br />
KProgressBar *prbar;<br />
QString prtxt, errstr;<br />
<br />
// správně<br />
KProgressBar *downloadProgressBar;<br />
QString progressText;<br />
QString errorString;<br />
</syntaxhighlight><br />
<br />
== Whitespace ==<br />
* Use blank lines to group statements<br />
* Use only one empty line<br />
* Use one space after each keyword<br />
* For pointers or references, use a single space before '*' or '&', but not after<br />
* No space after a cast<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
// špatně<br />
QString* myString;<br />
if(true){<br />
}<br />
<br />
// správně<br />
QString *myString;<br />
if (true) {<br />
}<br />
</syntaxhighlight><br />
<br />
== Braces ==<br />
As a base rule, the left curly brace goes on the same line as the start of the statement.<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
// špatně<br />
if (true)<br />
{<br />
}<br />
<br />
// správně<br />
if (true) {<br />
}<br />
</syntaxhighlight><br />
<br />
Exception: Function implementations, class, struct and namespace declarations always have the opening brace on the start of a line.<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
void debug(int i)<br />
{<br />
qDebug("foo: %i", i);<br />
}<br />
<br />
class Debug<br />
{<br />
};<br />
</syntaxhighlight><br />
<br />
Use curly braces even when the body of a conditional statement contains only one line.<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
// špatně<br />
if (true)<br />
return true;<br />
<br />
for (int i = 0; i < 10; ++i)<br />
qDebug("%i", i);<br />
<br />
// správně<br />
if (true) {<br />
return true;<br />
}<br />
<br />
for (int i = 0; i < 10; ++i) {<br />
qDebug("%i", i);<br />
}<br />
</syntaxhighlight><br />
<br />
== Switch statements ==<br />
Case labels are on the same column as the switch<br />
<br />
Example:<br />
<syntaxhighlight lang="cpp-qt"><br />
switch (myEnum) {<br />
case Value1:<br />
doSomething();<br />
break;<br />
case Value2:<br />
doSomethingElse();<br />
// fall through<br />
default:<br />
defaultHandling();<br />
break;<br />
}<br />
</syntaxhighlight><br />
<br />
== Line breaks ==<br />
Try to keep lines shorter than 100 characters, inserting line breaks as necessary.<br />
<br />
== Qt Includes ==<br />
* If you add #includes for Qt classes, use both the module and class name. This allows library code to be used by applications without excessive compiler include paths.<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
// špatně<br />
#include <QString><br />
<br />
// správně<br />
#include <QtCore/QString><br />
</syntaxhighlight><br />
<br />
== Artistic Style (astyle) automatic code formatting ==<br />
You can use [http://astyle.sourceforge.net/ astyle] (>=1.23) to format code or to test if you have followed this document. Run the following command:<br />
<syntaxhighlight lang="text"><br />
astyle --indent=spaces=4 --brackets=linux \<br />
--indent-labels --pad-oper --unpad-paren \<br />
--one-line=keep-statements --convert-tabs \<br />
--indent-preprocessor \<br />
`find -type f -name '*.cpp'` `find -type f -name '*.cc'` `find -type f -name '*.h'`<br />
</syntaxhighlight><br />
<br />
With astyle (>=2.01) you need to run the following command:<br />
<syntaxhighlight lang="text"><br />
astyle --indent=spaces=4 --brackets=linux \<br />
--indent-labels --pad-oper --unpad-paren \<br />
--keep-one-line-statements --convert-tabs \<br />
--indent-preprocessor \<br />
`find -type f -name '*.cpp'` `find -type f -name '*.cc'` `find -type f -name '*.h'`<br />
</syntaxhighlight><br />
<br />
A related shell script could be found for unix in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/astyle-kdelibs kdesdk/scripts/astyle-kdelibs] and for windows in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/astyle-kdelibs.bat kdesdk/scripts/astyle-kdelibs.bat].<br />
<br />
== Emacs and Vim scripts ==<br />
The "scripts" directory in the kdesdk module contains, among other useful things, some useful additions to the Emacs and Vim text editors that make it easier to edit KDE code with them.<br />
<br />
=== Emacs ===<br />
The [http://websvn.kde.org/trunk/KDE/kdesdk/scripts/kde-emacs kde-emacs] directory contains a set of key bindings, macros and general useful code. It is compatible with both GNU Emacs and XEmacs.<br />
<br />
To start using kde-emacs, add the following to your .emacs:<br />
<br />
<syntaxhighlight lang="text"><br />
(add-to-list 'load-path "/path/to/kde-emacs")<br />
(require 'kde-emacs)<br />
</syntaxhighlight><br />
<br />
Many settings can be changed by editing the "kde-emacs" group via <tt>M-x customize-group</tt>.<br />
<br />
For more information, including what the key bindings are and what additional settings you could add to your .emacs, please check <tt>kde-emacs.el</tt> itself.<br />
<br />
=== Vim ===<br />
You can find a vim script in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/kde-devel-vim.vim kdesdk/scripts/kde-devel-vim.vim] that helps you to keep the coding style correct. In addition to defaulting to the kdelibs coding style it will automatically use the correct style for Solid and kdepim code. If you want to add rules for other projects feel free to add them in the SetCodingStyle function.<br />
<br />
To use the script, include it in your {{path|~/.vimrc}} like this:<br />
<syntaxhighlight lang="text"><br />
source /path/to/kde/sources/kdesdk/scripts/kde-devel-vim.vim<br />
</syntaxhighlight><br />
<br />
<br />
Document started by Urs Wolfer. Some parts of this document have been adopted from the Qt Coding Style document posted by Zack Rusin on kde-core-devel.<br />
<br />
[[Category:Policies]] [[Category:C++]]</div>PingusPepanhttps://techbase.kde.org/index.php?title=Translations:Policies/Kdelibs_Coding_Style/28/cs&diff=63334Translations:Policies/Kdelibs Coding Style/28/cs2011-08-03T11:29:47Z<p>PingusPepan: Created page with "// správně"</p>
<hr />
<div>// správně</div>PingusPepanhttps://techbase.kde.org/index.php?title=Policies/Kdelibs_Coding_Style/cs&diff=63333Policies/Kdelibs Coding Style/cs2011-08-03T11:29:43Z<p>PingusPepan: Created page with "// špatně"</p>
<hr />
<div>This document describes the recommended coding style for kdelibs. Nobody is forced to use this style, but to have consistent formatting of the source code files it is recommended to make use of it.<br />
<br />
'''In short: Kdelibs coding style follows the Qt 4 coding style.'''<br />
<br />
== Odsazení ==<br />
* Bez tabulátorů<br />
* 4 mezery namísto jednoho tabulátoru<br />
<br />
== Variable declaration ==<br />
* Each variable declaration on a new line<br />
* Each new word in a variable name starts with a capital letter (so-called camelCase)<br />
* Avoid abbreviations<br />
* Take useful names. No short names, except:<br />
** Single character variable names can denote counters and temporary variables whose purpose is obvious<br />
** Variables and functions start with a lowercase letter<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
// špatně<br />
KProgressBar *prbar;<br />
QString prtxt, errstr;<br />
<br />
// správně<br />
KProgressBar *downloadProgressBar;<br />
QString progressText;<br />
QString errorString;<br />
</syntaxhighlight><br />
<br />
== Whitespace ==<br />
* Use blank lines to group statements<br />
* Use only one empty line<br />
* Use one space after each keyword<br />
* For pointers or references, use a single space before '*' or '&', but not after<br />
* No space after a cast<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
// špatně<br />
QString* myString;<br />
if(true){<br />
}<br />
<br />
// správně<br />
QString *myString;<br />
if (true) {<br />
}<br />
</syntaxhighlight><br />
<br />
== Braces ==<br />
As a base rule, the left curly brace goes on the same line as the start of the statement.<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
// špatně<br />
if (true)<br />
{<br />
}<br />
<br />
// správně<br />
if (true) {<br />
}<br />
</syntaxhighlight><br />
<br />
Exception: Function implementations, class, struct and namespace declarations always have the opening brace on the start of a line.<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
void debug(int i)<br />
{<br />
qDebug("foo: %i", i);<br />
}<br />
<br />
class Debug<br />
{<br />
};<br />
</syntaxhighlight><br />
<br />
Use curly braces even when the body of a conditional statement contains only one line.<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
// špatně<br />
if (true)<br />
return true;<br />
<br />
for (int i = 0; i < 10; ++i)<br />
qDebug("%i", i);<br />
<br />
// správně<br />
if (true) {<br />
return true;<br />
}<br />
<br />
for (int i = 0; i < 10; ++i) {<br />
qDebug("%i", i);<br />
}<br />
</syntaxhighlight><br />
<br />
== Switch statements ==<br />
Case labels are on the same column as the switch<br />
<br />
Example:<br />
<syntaxhighlight lang="cpp-qt"><br />
switch (myEnum) {<br />
case Value1:<br />
doSomething();<br />
break;<br />
case Value2:<br />
doSomethingElse();<br />
// fall through<br />
default:<br />
defaultHandling();<br />
break;<br />
}<br />
</syntaxhighlight><br />
<br />
== Line breaks ==<br />
Try to keep lines shorter than 100 characters, inserting line breaks as necessary.<br />
<br />
== Qt Includes ==<br />
* If you add #includes for Qt classes, use both the module and class name. This allows library code to be used by applications without excessive compiler include paths.<br />
<br />
Příklad:<br />
<syntaxhighlight lang="cpp-qt"><br />
// špatně<br />
#include <QString><br />
<br />
// correct<br />
#include <QtCore/QString><br />
</syntaxhighlight><br />
<br />
== Artistic Style (astyle) automatic code formatting ==<br />
You can use [http://astyle.sourceforge.net/ astyle] (>=1.23) to format code or to test if you have followed this document. Run the following command:<br />
<syntaxhighlight lang="text"><br />
astyle --indent=spaces=4 --brackets=linux \<br />
--indent-labels --pad-oper --unpad-paren \<br />
--one-line=keep-statements --convert-tabs \<br />
--indent-preprocessor \<br />
`find -type f -name '*.cpp'` `find -type f -name '*.cc'` `find -type f -name '*.h'`<br />
</syntaxhighlight><br />
<br />
With astyle (>=2.01) you need to run the following command:<br />
<syntaxhighlight lang="text"><br />
astyle --indent=spaces=4 --brackets=linux \<br />
--indent-labels --pad-oper --unpad-paren \<br />
--keep-one-line-statements --convert-tabs \<br />
--indent-preprocessor \<br />
`find -type f -name '*.cpp'` `find -type f -name '*.cc'` `find -type f -name '*.h'`<br />
</syntaxhighlight><br />
<br />
A related shell script could be found for unix in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/astyle-kdelibs kdesdk/scripts/astyle-kdelibs] and for windows in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/astyle-kdelibs.bat kdesdk/scripts/astyle-kdelibs.bat].<br />
<br />
== Emacs and Vim scripts ==<br />
The "scripts" directory in the kdesdk module contains, among other useful things, some useful additions to the Emacs and Vim text editors that make it easier to edit KDE code with them.<br />
<br />
=== Emacs ===<br />
The [http://websvn.kde.org/trunk/KDE/kdesdk/scripts/kde-emacs kde-emacs] directory contains a set of key bindings, macros and general useful code. It is compatible with both GNU Emacs and XEmacs.<br />
<br />
To start using kde-emacs, add the following to your .emacs:<br />
<br />
<syntaxhighlight lang="text"><br />
(add-to-list 'load-path "/path/to/kde-emacs")<br />
(require 'kde-emacs)<br />
</syntaxhighlight><br />
<br />
Many settings can be changed by editing the "kde-emacs" group via <tt>M-x customize-group</tt>.<br />
<br />
For more information, including what the key bindings are and what additional settings you could add to your .emacs, please check <tt>kde-emacs.el</tt> itself.<br />
<br />
=== Vim ===<br />
You can find a vim script in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/kde-devel-vim.vim kdesdk/scripts/kde-devel-vim.vim] that helps you to keep the coding style correct. In addition to defaulting to the kdelibs coding style it will automatically use the correct style for Solid and kdepim code. If you want to add rules for other projects feel free to add them in the SetCodingStyle function.<br />
<br />
To use the script, include it in your {{path|~/.vimrc}} like this:<br />
<syntaxhighlight lang="text"><br />
source /path/to/kde/sources/kdesdk/scripts/kde-devel-vim.vim<br />
</syntaxhighlight><br />
<br />
<br />
Document started by Urs Wolfer. Some parts of this document have been adopted from the Qt Coding Style document posted by Zack Rusin on kde-core-devel.<br />
<br />
[[Category:Policies]] [[Category:C++]]</div>PingusPepan