원문

Alphabet

A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P|Q|R|S|T|U|V|W|X|Y|Z

Back to Top

A

anonymous#
An anonymous user is a visitor to a Drupal website who is not currently logged in. Drupal considers any such visitor as being the anonymous user, with the user ID 0, and belonging to the anonymous user role.
argument #
A section of the URL for a page on a Drupal website. For example, in the URL for this page (http://drupal.org/node/937), the first argument is "node", and the second is "937". Some modules, most notably Views, allow the use of "wildcard" arguments that allow a particular page to vary depending on context.

Back to Top

B

block #
Blocks are a method for positioning data within a page. They often contain lists of nodes or other navigational content and are frequently placed in the left or right regions of a page. Assignment to a region is specified through the admin settings. Blocks themselves are not nodes. You can specify that a block only appears on certain pages or in certain contexts. The appearance of a block is controlled in a theme by the (code: block($subject, $content, $region = "main") method.
Configuring and Managing Blocks
책 (book) #
A book is a set of book pages tied together in a hierarchical sequence, perhaps with chapters, sections, subsections, and so on. You can use books for manuals, site resource guides, Frequently Asked Questions (FAQs), or whatever you'd like. To use books, enable the core Book module.

Back to Top

C

CCK (Content Construction Kit) #
A contributed module which permits site developers to define custom fields and content types. A variety of extension modules to CCK exist permitting specialized field definitions such as images, dates, and computed values.
child #
Used to describe objects that can have hierarchical relationships, such as menu items, book pages, taxonomy terms and so on. A "child" menu item, for example, is nested under another menu item, which is referred to as the "parent" menu item. See also: parent
code freeze #
Refers to a date at which no new features can go in the next version of Drupal, unless specific dispensations have been made by the core committers (even then, only when the impact on other systems is minimal). At code freeze, the focus in Drupal core shifts to bug fixing and usability improvements. It is the time when contributed module developers can begin working on updating their code to work with the next version of Drupal.
content #
Often erroneously used in Drupal documentation as a synonym for node, content refers generically to the text, images, and other information on a web site. Some content on a typical Drupal site is not actually nodes, such as comments that are attached to nodes, and file attachments.
content type #
Every node belongs to a single 'node type' or 'content type', which defines various default settings for nodes of that type, such as whether the node is published automatically and whether comments are permitted. Modules can define their own content types; the core Drupal Book and Poll modules are two examples of modules that define content types. You can find out more about content types on the content types handbook page.
core or Drupal core #
Refers to the Drupal files and modules included with the Drupal project download.
core committers #
A team of Drupal developers that review proposed changes to the Drupal core and maintain code. They are the only ones who have write access to the core CVS repository.
core contributor #
Core contributors are software developers who contribute code patches or documentation for the Drupal core. Contributions are peer reviewed and then evaluated by the core committers.
cron #
Cron (short for chronograph) is a command scheduler that executes commands or scripts (groups of commands) automatically at specified time/date intervals. Drupal uses a 'cron job' to perform periodic tasks that help Drupal to run smoothly and efficiently.
CVS (Concurrent Versions System) #
CVS is a version control system used by Drupal code contributors to coordinate their individual code changes. CVS records everyone's changes to a given project in a directory tree called a CVS repository .

Back to Top

F

filter #
Filters are used to strip out HTML, PHP, JavaScript, and other undesirable elements from content before pages are displayed. Other filters add formatting and features such as smilies. It is possible to create custom filters that allow or forbid only those tags you wish. Text filters and input formats

Back to Top

I

input format #
An input format is a collection of filters, arranged in a certain order, that defines the processing that happens to user-entered text before it is shown in the browser. Usually different user roles are given permission to use different input formats depending on how much they are trusted. For those roles, the input format may often be available an an option that shows up underneath the body of a node edit form. Text filters and input formats

Back to Top

L

log #
A log is a list of recorded events. A log may contain usage data, performance data, errors, warnings and operational information. Watchdog is Drupal's primary event log.

Back to Top

M

In Drupal, the term menu refers both to the clickable navigational elements on a page, and to Drupal's internal system for handling requests. When a request is sent to Drupal, the menu system uses the provided URL to determine what functions to call.
모듈 (module) #
A module is software (code) that extends Drupal features and/or functionality. Core modules are those included with the main download of Drupal. Contributed (or "contrib") modules are available for separate download from the modules section of downloads. Note: Be sure that the version of the contributed module you wish to use matches your version of Drupal -- when you are viewing the list of modules, you can filter for compatibility to a particular version of Drupal by clicking on links in the sidebar.

Back to Top

N

노드 (node) #
A node is a piece of content in Drupal, typically corresponding to a single page on the site, that has a Title an optional Body, and perhaps additional fields. Every node also belongs to a particular content type, and can additionally be classified using the taxonomy system. Examples of nodes are polls, stories, book pages, images, etc.
node type #
See content type.

Back to Top

P

parent #
Used to describe objects that can have hierarchical relationships, such as menu items, book pages, taxonomy terms and so on. A "parent" menu item, for example, contains other menu items, which are referred to as "children" menu items. See also: child
path #
In Drupal terms, path is the unique, last part of the URL for a specific function or piece of content. For instance, for a page whose full URL is http://example.com/?q=node/7, the path is node/7. Drupal can use "clean URLs" if the Path module is enabled, which would change the full URL in this example to http://example.com/node/7; the path would still be node/7.
permission #
1) Drupal - Permissions control access to content creation, modification and site administration at the application level. Administrators assign permissions to roles, then assign roles to users. The first user ID (uid) of a Drupal site (uid=1) automatically receives all permissions, no matter what role that user belongs to. Any anonymous user has uid=0 (see also anonymous).

2) UNIX/Linux/Windows - Permissions are security settings restricting or allowing users to access information or perform certain functions at the operating system level. In the case of files on UNIX or Linux systems, there are three types of permissions: read, write, and execute.

프로젝트 (project) #
An open-source collaborative effort; there are several types of projects in the Drupal community, including contributed modules, contributed themes, handbook documentation on the drupal.org web site, and the core Drupal software itself.

Back to Top

R

역할 (role) #
Roles are sets of permissions that can be applied to individual users. Users can belong to more than one role. Two roles, authenticated users (those users that sign up for an account) and anonymous users (those either without an account or not logged in), are supplied by default with Drupal installations. Users with sufficient permission can create additional roles, and the permissions granted to the two default roles can also be configured.
RSS #
RSS (Really Simple Syndication) is a family of Web feed formats used to publish frequently updated content such as blog entries, news headlines or podcasts. An RSS document (which is called a feed or web feed or channel) contains either a summary of content (teaser) from an associated web site or the full text.

Back to Top

S

story #
A type of node that is defined in a default Drupal installation, typically used for content that has a date associated with it, such as a news item.
style #
A CSS file (or files) replacing the default CSS of a theme or engine. Appears in the theme selection list with the same precedence as themes and templates.

Back to Top

T

tarball #
In computing, tar ("short for tape archive") is both a file format and the name of the program used to handle such files. The jargon term tarball is used to describe an archive that has been created with the tar command. A .tar file is commonly referred to as a tarball. Tarballs are used within the developer community to collate collections of files into one larger file, for distribution or archiving, while preserving file system information such as user and group permissions, dates, and directory structures.
taxonomy #
Taxonomy is literally "the science of classification". The Drupal taxonomy system enables authorized users to categorize content using both tags and administrator-defined terms. It is a flexible tool for classifying content with many advanced features. Further information can be found within the taxonomy system documentation.

  • term # - a category or tag or keyword ie what gets assigned to nodes. Terms can be structured as children and parents to create hierarchies.
  • vocabulary # - a collection of terms that share some sort of relationship with each other. The vocabulary isn't part of any hierarchy as such.
  • Taxonomy - the name of the whole system and the name of the module that implements it. In some versions of Drupal, that is also the name of the menu item in the admin menu.
  • category # - A synonym for taxonomy, and the name of the menu item in some versions of Drupal.
teaser #
The first few words or sentences of a piece of content, usually with a link to the complete node.
template #
A file that is mostly HTML with some special PHP code to substitute in values provided by an engine.
theme #
A theme is a file or collection of files (PHP, INFO, CSS, JPG, GIF, PNG), which together determine the look and feel of a site. Drupal modules define themeable functions which can be overridden by the theme file. There are additional themes available in the themes section of downloads.
theme engine #
A theme engine is a set of scripts that interprets code and makes theming a site easier. This takes the dynamically generated content and outputs it to HTML. Drupal has three theme engines in addition to being able to write a theme that bypasses the theme engine. The default theme engine is phpTemplate. See the theme engines section of downloads for contributed engines.

Back to Top

U

URL (uniform resource locator) #
A URL is the address that defines the route to locate an object on an Internet server. Generally, the syntax for a URL contains the scheme, host-name, port, path and filename, for example; http://www.drupal.org/node/937

Back to Top

V

Views #
A contributed module which allows site developers a simple graphical interface for modifying the presentation of content. Views permits selection of specific fields to display, filtration against various node attributes, choice of basic layout options (ie. list, full nodes, teasers, etc.), and other more advanced features. Many Drupal sites use Views extensively.

Back to Top

W

무게 (weight) #
Weight is a term used by Drupal to define the priority or order in which an function is processed or a block / node is displayed. From Drupal 6, the weight field is adjusted dynamically using a drag-and-drop interface. Note: A lower weight value (-10) will float to the top of lists, while heavier (+10) weights will appear lower in lists.
WYSIWYG #
WYSIWYG is an acronym for What You See Is What You Get, used in computing to describe a method in which content is edited and formatted by interacting with an interface that closely resembles the final product.
Groups audience: 

Comments

"drupal" 이라는 단어가 번역 문자열에 포함되어 있는 경우
"드루팔" 이런 식으로 한글로 읽어줘야 하는지
아니면 원문 그대로 "drupal"로 써야하는지 커뮤니티의 방침이 뭔지 잘 모르겠습니다.

저는 드루팔 이렇게 읽었는데요 승인된 문자열의 경우 drupal로 적혀있는 경우가 있어서요.
앞으로의 contributor들의 번역 작업을 위해서도 결정이 필요한 것 같습니다.

말씀하신대로 섞여있습니다 :)

전 우리말 - "드루팔" - 로 통일하는 것에 한표입니다. 다른 분은 어떠세요?

저도 '드루팔'로 표기에 찬성입니다.

드루팔을 듣고 drupal 이외에 다른 것을 떠올리시는 분은 없을 것 같습니다.

실제로 발음이 "쥬팔"에 더 가깝긴 하지만요.

말투는 어떤 것이 좋을지요. 이를테면,

- 확인하여주십시오
- 확인해주세요

두 가지 중 어느 것이 나을지...

조인스 회원가입 페이지의 예를 보면, https://my.joinsmsn.com/register/member_reg_f4.asp?regist_location=K0001,
위에는 '확인하여주십시오'라고 써있고 주소 부분에 보면 '입력하세요'라고 되어있습니다.

상단은 방침에 관한 것이니 좀 딱딱한 '하시오'의 표현이 어울리는 것 같고 주소 옆에는 안내를 하는 느낌이니 '하세요'의 표현이 더 적절해 보이니, 어느 하나만 써야 한다기 보다는 그 때에 따라 적절한 느낌에 맞는 표현이 다를 수도 있을 것 같습니다.

하지만 번역할 문장만 따로 보아서는 어떤 문맥 속에서 쓰이는 경우인지 확실치가 않으니 그리 쉬운 문제는 아닌 것 같아 보입니다. 번역에 한가지 길만 있는 것은 아니니 역시 일관성이 더 중요하다는 생각입니다.

먼저 안녕하세요? 반갑습니다!
올해 들어서 보니 갑자기 번역을 많이 한 분이 계셔서 반가웠고
자극을 받아서 요즘 저도 꾸준히 번역해오고 있습니다.
번역을 꾸준히 하다보니 말씀하신 문체를 포함한 몇 가지 중요한 문제들이 있더라고요.

어쨌든 문체에 대해서라면,
기존에 수많은 번역팀 선배들께서 깨알같이 하신 6 버전대 번역 문체들은
상당히 딱딱하고 포멀(어색한 번역체도 일조. 사실 의미전달에도 다소 무리가 있음)합니다.
기본적으로 저도 이 분들의 작업에 감사하는 마음에서 번역을 시작하게 됐지만,
좀 변화가 필요하다고 생각합니다.
저는 개인적으로 좀 더 친숙하고 편안했으면 하는 바람으로,
실제 번역을 진행하면서 부드러운 문체를 좀 적극적으로 사용했습니다.

드루팔 메인 커뮤니티 문서 중 번역관련된 글을 읽으며 고민을 하다가
이 작업이 기업에 제품을 팔기 위한 번역 작업이 아니고,
국내 사용자들이 좀 더 편하고 재밌게 드루팔을 사용할 수 있도록
돕는 작업이라는 생각하게 됐습니다.
그래서 부드러운 문체 포함 유머도 약간씩 가미하면 어떨까(물론 의미는 정확하게 전달하면서)하는 생각에 번역 작업에 좀 반영했었습니다.

그렇지만 역시 문체는 일관성이 중요해서 막상 저지르고 나니 번역팀의 논의나 합의가 어느정도 필요하지 않을까
생각이 들었습니다. 글이 좀 장황해지는데 제 결론을 요약하자면, 다음과 같습니다.

1. 좀 심각한 내용 (경고, 주의 등 주로 관리영역) 이런 부분에서는 다소간 경각심을 전달하기 위해 진지한 문체를...
2. 일반적인 내용 (사용자들이나 사이트 관리자 등이 자주 사용하는 프로트엔드쪽 부분)은 부드럽고 친근한 문체를...

저는 지금 번역 작업하면서 생기는 이슈들을 그때그때 정리하면서 문서화하고 있는데요.
조만간 kldp 및 여기 게시판에 포스팅하려고 합니다. (아 관리자님이 kldp에 하라고 했었나요? ㅎㅎ)
중요한 문제들은 꼭 의견을 교환하고 좀 더 좋은 방향으로 진전됐으면 합니다.

동감입니다.

제가 번역을 몇개 했는데, mozolady님께서 무척 많이 하셨더군요. 번역의 질도 중요하지만 번역자가 많지 않은 상황에서는 일단 번역율을 높이는 것이 중요한 것 같습니다. 그런 다음에 좀 더 다듬어도 되겠지요. 벌써 80%가 넘었으니 머지않아 다 될 것 같습니다 ;)