Contribute/ko - Revision history

FuzzyBot: Updating to match new version of source page

2012-12-20T19:00:03Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2012-12-08T17:00:03Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2012-11-04T10:00:07Z

Updating to match new version of source page

AnneW at 18:08, 19 July 2012

2012-07-19T18:08:21Z

FuzzyBot: Updating to match new version of source page

2012-05-31T20:13:45Z

Updating to match new version of source page

Peremen: Created page with "KDE에는 클래스 API 문서가 있습니다. API 문서는 KDE API 참조 설명서 부분에서 볼 수 있으며, 클래스 문..."

2011-12-17T15:38:35Z

Created page with "KDE에는 클래스 API 문서가 있습니다. API 문서는 KDE API 참조 설명서 부분에서 볼 수 있으며, 클래스 문..."

Peremen: Created page with "KDE 코딩에 관한 책도 알아보십시오."

2011-12-17T15:37:07Z

Created page with "KDE 코딩에 관한 책도 알아보십시오."

Peremen: Created page with "KDE 코딩에 대한 더 많은 정보는 FAQ 페이지에서 참조할 수 있습니다. 이 정보는 KDE 4 기준으로는 오래되었지만, KDE 이외..."

2011-12-17T15:36:50Z

Created page with "KDE 코딩에 대한 더 많은 정보는 FAQ 페이지에서 참조할 수 있습니다. 이 정보는 KDE 4 기준으로는 오래되었지만, KDE 이외..."

Peremen: Created page with "KDE에서 사용하는 기술은 튜토리얼에서 찾아볼 수 있습니다. 일부 튜토리얼은 KDE3을 대상으로 하고 있으므로, 현재 ..."

2011-12-17T15:36:11Z

Created page with "KDE에서 사용하는 기술은 튜토리얼에서 찾아볼 수 있습니다. 일부 튜토리얼은 KDE3을 대상으로 하고 있으므로, 현재 ..."

Peremen: Created page with "다른 책을 알아보고 싶으면 [http://qt.nokia.com/developer/books/ Qt에 관한 책] 페이지를 참조하십시오. Qt에 친숙해지는 다른 방법은 [http://doc.q..."

2011-12-17T15:31:14Z

Created page with "다른 책을 알아보고 싶으면 [http://qt.nokia.com/developer/books/ Qt에 관한 책] 페이지를 참조하십시오. Qt에 친숙해지는 다른 방법은 [http://doc.q..."

@@ Line 46: / Line 46: @@
 === Qt ===
 KDE 코딩에 익숙해지려면 Qt 툴킷을 이해해야 합니다. Qt에 친숙하지 않다면 [http://doc.qt.nokia.com/latest Qt 참조 문서]를 통하여 Qt를 익히십시오.
 <span class="mw-translate-fuzzy">
@@ Line 52: / Line 54: @@
 </span>
 다른 책을 알아보고 싶으면 [http://qt.nokia.com/developer/books/ Qt에 관한 책] 페이지를 참조하십시오. Qt에 친숙해지는 다른 방법은 [http://doc.qt.nokia.com/latest/how-to-learn-qt.html Qt 배우기] 페이지에 더 있습니다.
 === KDE ===

@@ Line 102: / Line 102: @@
 :* '''Read the Developer FAQ'''. Many common developer questions have been answered in the [[Development/FAQs|KDE Developer FAQ]]
 :* '''Search/browse KDE websites'''. A lot of questions can also be answered from the KDE websites, and the documentation included on it. You can search all the KDE websites on the homepage. In addition, you can browse the [http://techbase.kde.org KDE TechBase website]. And if possible, help edit it for clarity, and use the talk page if something is unclear.
-:* '''Search mailing lists'''. A lot of questions have already been answered on the KDE mailing lists, particular the lists kde-devel, kde2-porting, kde-core-devel, kde-games-devel, kfm-devel and koffice-devel. You can search these lists either at [http://lists.kde.org/ lists.kde.org]. You should always search for your answer before asking questions on the mailing lists. When you ask a question on a mailing list you are emailing thousands of people -- please do this only if the answer is not available through a simple search.
+:* '''Search mailing lists'''. A lot of questions have already been answered on the KDE mailing lists, particular the lists kde-devel, kde2-porting, kde-core-devel, kde-games-devel, kfm-devel and koffice-devel. You can search these lists at [http://lists.kde.org/ lists.kde.org]. You should always search for your answer before asking questions on the mailing lists. When you ask a question on a mailing list you are emailing thousands of people -- please do this only if the answer is not available through a simple search.
 :* '''Search engines'''. Do not forget about your favorite search engine. One of the best search engines is Google. With Google you can also [http://groups.google.com/ search] the great bulk of Usenet news sites, which is also particularly helpful, especially for general programming and gcc-related questions.

@@ Line 48: / Line 48: @@
 KDE 코딩에 익숙해지려면 Qt 툴킷을 이해해야 합니다. Qt에 친숙하지 않다면 [http://doc.qt.nokia.com/latest Qt 참조 문서]를 통하여 Qt를 익히십시오.
 더 친절한 Qt 소개 문서를 보고 싶거나, 다른 문서를 보고 싶으면 [http://qt4.digitalfanatics.org/tiqt/ The Independent Qt Tutorial]을 참고하십시오. (출판 문제로 현재 사용할 수 없습니다.)
 다른 책을 알아보고 싶으면 [http://qt.nokia.com/developer/books/ Qt에 관한 책] 페이지를 참조하십시오. Qt에 친숙해지는 다른 방법은 [http://doc.qt.nokia.com/latest/how-to-learn-qt.html Qt 배우기] 페이지에 더 있습니다.
 === KDE ===

@@ Line 1: / Line 1: @@
 <languages />
-{{Template:I18n/Language Navigation Bar|Contribute}}
 이 페이지에서는 KDE 개발을 비롯한 KDE의 여러 부분에 관한 정보를 제공합니다. KDE는 도와 주는 모든 사람을 환영합니다.

@@ Line 63: / Line 63: @@
 A more detailed description of the steps above is available in our [http://quality.kde.org/develop/howto/howtohack.php Programming Guide].
 == Getting Involved in Bug Hunting and Application Quality ==
@@ Line 68: / Line 76: @@
 There is a large number of applications within KDE, and not all of them have a maintainer dedicated to managing bugs and generally helping out with all the issues associated with turning some working code into a polished application.
-If you are interested in helping out with KDE, but don't know where to start, becoming a member of the KDE Quality Team might appeal to you - see the [http://quality.kde.org Quality Team website] for more information. Note that you do not need any programming skills to become involved. In particular developers regularly publish so-called [http://community.kde.org/KDE/Junior_Jobs Junior Jobs] to encourage new contributions.
+If you are interested in helping out with KDE, but don't know where to start, becoming a member of the KDE Quality Team might appeal to you - see the [http://techbase.kde.org/Contribute/Quality_Team Quality Team website] for more information. Note that you do not need any programming skills to become involved. In particular developers regularly publish so-called [http://community.kde.org/KDE/Junior_Jobs Junior Jobs] to encourage new contributions.
 Of course, you can become involved in bug hunting without being part of the KDE Quality Team - just create yourself an account on the KDE [http://bugs.kde.org bug tracking system], and start searching / sorting through the bugs. Again, you don't have to have programming skills - it helps the programmers enormously just to have a procedure that allows a bug to be consistently reproduced.
 The [[Contribute/Bugsquad|Bugsquad]] tries to keep track of bugs in KDE software and make sure that valid bugs are noticed by developers. You do not need any programming knowledge to be in the Bugsquad; in fact it is a great way to return something to the KDE community if you cannot program.
 ==Getting Answers to Your Questions==

@@ Line 60: / Line 60: @@
 [[Development/Further Information#Books|KDE 코딩에 관한 책]]도 알아보십시오.
-Last, but by no means least, KDE comes with extensive class (Application Programmer Interface) documentation. This is available in the
+KDE에는 클래스 API 문서가 있습니다. API 문서는 [[Development/Tutorials/API Documentation|KDE API 참조 설명서]] 부분에서 볼 수 있으며, 클래스 문서를 작성하거나 업데이트하는 방법도 포함하고 있습니다. 직접 문서를 생성하거나, 온라인에서 [http://api.kde.org/ API 문서]를 읽어볼 수 있습니다.
-[[Development/Tutorials/API Documentation|KDE API Reference Manuals]] section, which also contains a number of useful links on how to write or update the class documentation. You can also generate these on your own machine, or refer to a more up-to-date online version at [http://api.kde.org/ API Reference].
 A more detailed description of the steps above is available in our [http://quality.kde.org/develop/howto/howtohack.php Programming Guide].

@@ Line 58: / Line 58: @@
 KDE 코딩에 대한 더 많은 정보는 [[Development/FAQs|FAQ]] 페이지에서 참조할 수 있습니다. 이 정보는 KDE 4 기준으로는 오래되었지만, KDE 이외의 영역에서도 유용합니다.
-You can also read [[Development/Further Information#Books|KDE coding books]].
+[[Development/Further Information#Books|KDE 코딩에 관한 책]]도 알아보십시오.
 Last, but by no means least, KDE comes with extensive class (Application Programmer Interface) documentation. This is available in the

@@ Line 56: / Line 56: @@
 KDE에서 사용하는 기술은 [[Development/Tutorials|튜토리얼]]에서 찾아볼 수 있습니다. 일부 튜토리얼은 KDE3을 대상으로 하고 있으므로, 현재 시점에서는 적합하지 않습니다.
-You will also find useful information on KDE coding in the [[Development/FAQs|FAQs]] section. This information may also be somewhat dated for KDE4, however much of it is broadly applicable, even outside KDE.
+KDE 코딩에 대한 더 많은 정보는 [[Development/FAQs|FAQ]] 페이지에서 참조할 수 있습니다. 이 정보는 KDE 4 기준으로는 오래되었지만, KDE 이외의 영역에서도 유용합니다.
 You can also read [[Development/Further Information#Books|KDE coding books]].