編輯“WordPress:Reporting Bugs”（章節(jié)）

=== 修補程序錯誤===

If you and are familiar with [[WordPress:Glossary#PHP|PHP]] and [[WordPress:Glossary#MySQL|MySQL]], and would like to help in the development of WordPress, then you are encouraged to patch WordPress bugs. Here are the steps to follow:

如果你熟悉[[WordPress:Glossary#PHP|PHP]] 和[[WordPress:Glossary#MySQL|MySQL]]，并且希望在WordPress發(fā)展過程中，盡自己的一臂之力，你可以解決程序錯誤問題。下面是一些你可以遵循的步驟：

#Read [[WordPress:#Finding Bugs to Fix|Finding Bugs to Fix (above)]], and find a bug to fix in [http://trac.wordpress.org Trac].

#請閱讀[[WordPress:#Finding Bugs to Fix|查找修正程序錯誤 (上面的)]]，查找程序錯誤，在[http://trac.wordpress.org Trac]中修正。

#Connect to the [http://wordpress.org/download/svn/ WordPress Subversion (SVN) Repository] using the username and password you acquired when [http://wordpress.org/support/register.php registering]. Read [[WordPress:Using Subversion]] if you are unfamiliar with SVN.  All patches should be submitted against the latest code in the SVN repository.

#連接到[http://wordpress.org/download/svn/ WordPress 子版本(SVN) 資源庫]，[http://wordpress.org/support/register.php 注冊]時，使用你得到的用戶名和密碼。如果你不熟悉子版本，請閱讀[[WordPress:Using Subversion|使用子版本]]。所有的補丁都必須根據(jù)子版本資源庫中最新的代碼，遞交。

# Figure out how to fix the bug, by modifying WordPress core files. You may want to discuss your proposed solution on the [[WordPress:Mailing_Lists#Hackers|wp-hackers mailing list]] before finalizing it.

#了解怎樣通過更改WordPress核心文件，解決程序錯誤問題。你可能希望在[[WordPress:Mailing_Lists#Hackers|wp-hackers 郵件列表]]上討論你建議的解決辦法，再最后決定使用這個方法。

# Test your fix, verifying that the bug has been fixed, and that nothing else in WordPress is broken in the process.

#測試你的方法，確認程序錯誤已經(jīng)得到了解決，而且在解決過程中，WordPress中的其它內(nèi)容都沒有受損。

# Create a ''patch file'' (or files) containing your fix. This is basically a ''diff'' of the fixed file(s) and the originals from SVN. See [http://asymptomatic.net/2005/12/03/586/how-to-patch-wordpress How to Patch WordPress by Owen Winkler] for detailed instructions. There are also instructions for Linux/Mac command-line users in [http://markjaquith.wordpress.com/2005/11/02/my-wordpress-toolbox/ Mark Jaquith's Toolbox] and Windows Tortoise SVN users in [http://blog.ftwr.co.uk/archives/2005/11/03/windows-wordpress-toolbox/ Westi's Blog].

#創(chuàng)建一個(或者多個)包含解決方法的''補丁文件''。這基本上是固定文件的''diff''，而且是SVN的原始資料。請看看[http://asymptomatic.net/2005/12/03/586/how-to-patch-wordpress Owen Winkler的怎樣修補WordPress]上面的詳細指示。在[http://markjaquith.wordpress.com/2005/11/02/my-wordpress-toolbox/ Mark Jaquith's Toolbox]上也有對于Linux/Mac 命令行用戶的指導和[http://blog.ftwr.co.uk/archives/2005/11/03/windows-wordpress-toolbox/ Westi的博客]上的Windows Tortoise SVN用戶的指導。

# Upload it to the ticket using the [http://trac.wordpress.org/ Trac] ''Attach file'' button, and add ''has-patch'' to the keywords. If the patch needs testing, you might also put ''needs-testing'', or one of the other Trac keywords; see [[WordPress:#Trac Keywords|Trac Keywords (below)]] for more information.

#使用[http://trac.wordpress.org/ Trac] ''附加文件''按鈕，將其上傳到ticket上，并且將''has-patch''添加到關鍵詞上。如果補丁需要測試，你可能需要加入''需要測試''，或者其它的某個Trac關鍵詞；更多的信息，請看看[[WordPress:#Trac Keywords|Trac 關鍵詞 (下面的)]]