Skip to content

Introduction 翻譯 #15

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Oct 6, 2014
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 10 additions & 10 deletions manual/zh-TW/coding-standards/introduction.md
Original file line number Diff line number Diff line change
@@ -1,19 +1,19 @@
## Introduction
## 前言

Good coding standards are important in any software development project. These standards are even more important when a large, diverse and worldwide community of developers are contributing to a project. One of the things that sets good software apart from great software is not only the features or the actual function the software performs, but the quality of its source code.
好的編碼規範對於任何軟體開發專案來說都是非常重要的。當大型、多樣化且世界級的開發者社群在對專案提交貢獻時,這些標準尤其重要。令軟體變得更好的其中一項因素,不只在於它提供了多少優異的功能,也需關注它的原始碼品質有多優良。
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is not only ... but

對等連連接詞 “ not only A but also B ” 雖然有 not,但意思卻是「肯定的」,意指 「不只是 A 而且連 B 都 …」,即 A 和 B 兩者都…。其中 only 可換成 merely,而 also 可省略。

所以跟 並非... 而 ... 的意思有一點點不一樣。

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

應該是要用「並非只」

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

不過就中文來說,有時候 並非... 而 ... 就含有「並非只」的意思了

因為講完全的,「並非只在於...而」這樣的用詞在傳統中文中其實很少見

我改成「不只在於」好了

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

我改成「不只在於它提供了多少優異的功能,也需關注它的原始碼品質有多優良」

不過說真的原文就很文言了,照翻會很難讀

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

好的好的


In order to perform in the highly competitive Open Source and proprietary software industries, source code not only needs to be beautifully designed, it also needs to be beautiful and elegant to look at. The Joomla Coding Standards Manual is to help ensure our code is the highest quality which will make it easy to read, debug, and maintain.
為了在競爭激烈的開源環境與專有軟體中佔有一席之地,原始碼不只需要優美的結構設計,更需要在閱讀上看起來同樣美麗而優雅。Joomla 編碼標準就是用來幫助我們確認程式碼擁有最高的品質,使其易於閱讀、除錯與維護的手冊。

## Guiding Principles
## 指導原則

Since readable code is more maintainable, the compass that guides us in achieving that goal is a set of well thought out coding standards for the different software languages that are employed in the Joomla software project. Joomla has a solid heritage of striving to support a great looking product with great looking code.
可讀性高的代碼也是易於維護的,而靠著一套針對 Joomla! 所使用的各種程式語言所攥寫的完善編碼標準,能夠指引我們實現可讀性的這個目標。Joomla! 有著堅實的傳統與努力過程來實現一個偉大的產品與美觀的代碼。
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the different software languages that are employed in the Joomla software project
讓許多不同程式語言專案的工程師一同維護專案

一個是 Joomla 專案使用各種不同的語言, 一個是使用不同程式語言的工程師,主詞不一樣。不過應該意思有到就好了。

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

你給個範例好了,這句跟「庭院深深身幾許」有得拼

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

有點像是

可讀性高的代碼也是易於維護的,而靠著一套針對 Joomla! 所使用的不同程式語言所攥寫的完善的編碼標準,可以指引我們實現可讀性的這個目標。

相當難翻XDDD

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

反正我就放上去了,你覺得ok就 merge吧


This manual compiles the collective wisdom of past and present contributors to the project to form the definitive standard for coding in Joomla, whether that is for the core Joomla Framework or an extension that forms part of the stack of the Joomla CMS. This manual also serves as a lighthouse to the Joomla developer community, to safely guide developers around the pitfalls of becoming lackadaisical with respect to writing clean, beautiful code.
這份文件彙整過去和現在許多貢獻者的集體智慧,形成一個權威的標準,無論是核心Joomla!框架還是CMS的擴充套件。而這份文件也可以成為一座燈塔,以安全的指引社群開發者們編寫漂亮、乾淨的代碼。

The Joomla Coding Standards borrows heavily from the PEAR coding standard for PHP files, augmenting and diverging where it is deemed sensible to do so.
Joomla 編碼標準在 PHP 檔案的部份大量借鑑 PEAR 標準,並在這之上做了一定程度被認為是明智的增加與擴充。

There are [tools available](appendices/analysis.md) to help your code conform to our standards.
我們準備了一些 [好用的工具](appendices/analysis.md) 來幫助您確認您的代碼是否符合我們的標準。

## Contributing to this manual
## 貢獻與改善這份手冊

If you want to contribute and improve this manual, you can find the source files at [https://github.com/joomla/coding-standards/tree/gh-pages](https://github.com/joomla/coding-standards/tree/gh-pages).
如果您想要改善這份手冊並提交貢獻,可以在 [https://github.com/joomla/coding-standards/tree/gh-pages](https://github.com/joomla/coding-standards/tree/gh-pages) 之中找到其原始文件。