documentation/locale/ko/LC_MESSAGES/studio.po

# SOME DESCRIPTIVE TITLE.
# Copyright (C) Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
# 
# Translators:
# Daye Jeong, 2024
# Sarah Park, 2024
# Wil Odoo, 2024
# 
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-03-25 16:01+0000\n"
"PO-Revision-Date: 2024-03-30 23:40+0000\n"
"Last-Translator: Wil Odoo, 2024\n"
"Language-Team: Korean (https://app.transifex.com/odoo/teams/41243/ko/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ko\n"
"Plural-Forms: nplurals=1; plural=0;\n"

#: ../../content/applications/studio.rst:6
msgid "Studio"
msgstr "스튜디오"

#: ../../content/applications/studio.rst:17
msgid ""
"Studio is a toolbox that allows you to customize Odoo without coding "
"knowledge. For example, you can, on any app, add or modify:"
msgstr ""

#: ../../content/applications/studio.rst:20
msgid ":doc:`Fields <studio/fields>`"
msgstr ":doc:`필드 <studio/fields>`"

#: ../../content/applications/studio.rst:21
msgid ":doc:`Views <studio/views>`"
msgstr ":doc:`화면 <studio/views>`"

#: ../../content/applications/studio.rst:22
msgid ":doc:`Models <studio/models_modules_apps>`"
msgstr ":doc:`모델s <studio/models_modules_apps>`"

#: ../../content/applications/studio.rst:23
msgid ":doc:`Automated actions <studio/automated_actions>`"
msgstr ""

#: ../../content/applications/studio.rst:24
msgid ":doc:`PDF reports <studio/pdf_reports>`"
msgstr ""

#: ../../content/applications/studio.rst:25
msgid "Approval rules"
msgstr ""

#: ../../content/applications/studio.rst:26
msgid "Security rules"
msgstr ""

#: ../../content/applications/studio.rst:28
msgid ""
"Or you can :doc:`build an app from scratch <studio/models_modules_apps>`."
msgstr ""

#: ../../content/applications/studio.rst:31
msgid "`Odoo Tutorials: Studio <https://www.odoo.com/slides/studio-31>`_"
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:3
msgid "Automated actions (automations)"
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:5
msgid ""
"Automated actions are used to trigger automatic changes based on user "
"actions (e.g., apply a modification when a field is set to a specific value)"
" or on time conditions (e.g., archive a record 7 days after its last "
"update)."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:9
msgid ""
"To create an automated action with Studio, go to :guilabel:`Automations` "
"from anywhere within Studio."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:12
msgid ""
"For every automated action you create, the following elements should be "
"defined: the :ref:`studio/automated-actions/model`, the "
":ref:`studio/automated-actions/trigger`, the :ref:`studio/automated-"
"actions/apply-on`, and the :ref:`studio/automated-actions/action`."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:0
msgid "Example of an automated action on the Subscription model"
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:25
msgid "Model"
msgstr "모델"

#: ../../content/applications/studio/automated_actions.rst:27
msgid "Select the model where the automated action should be applied."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:30
msgid ""
"The model you are on when you click on :guilabel:`Automations` is pre-"
"selected by default."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:35
msgid "Trigger"
msgstr "자동 실행"

#: ../../content/applications/studio/automated_actions.rst:37
msgid ""
"Define when the automated action should be applied. Six triggers are "
"available."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:42
msgid "On Creation"
msgstr "생성할 때"

#: ../../content/applications/studio/automated_actions.rst:44
msgid "The action is triggered when a record is created and then saved."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:49
msgid "On Update"
msgstr "갱신할 때"

#: ../../content/applications/studio/automated_actions.rst:51
msgid ""
"The action is triggered when a previously saved record is edited and then "
"saved."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:53
msgid ""
"Use :guilabel:`Trigger Fields` to specify which fields - and only those - "
"trigger the action on their update."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:55
msgid ""
"To detect when a record changes from one state to another, define a "
":guilabel:`Before Update Domain` filter, which checks if the condition is "
"satisfied before the record is updated. Then set an :ref:`studio/automated-"
"actions/apply-on` filter, which checks if the condition is met after the "
"record is updated."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:61
msgid ""
"If you want the automated action to happen when an email address is set on a"
" contact, define the :guilabel:`Before Update Domain` to `Email is not set`,"
" and the :guilabel:`Apply on` domain to `Email is set`."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:0
msgid "Example of an On Update trigger"
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:72
msgid "On Creation & Update"
msgstr "생성 또는 갱신할 때"

#: ../../content/applications/studio/automated_actions.rst:74
msgid ""
"The action is triggered when a record is created and saved or edited "
"afterward and saved."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:79
msgid "On Deletion"
msgstr "삭제할 때"

#: ../../content/applications/studio/automated_actions.rst:81
msgid "The action is triggered when a record is deleted."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:84
msgid ""
"This trigger is rarely used, as archiving records is usually preferred to "
"deletion."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:89
msgid "Based on Form Modification"
msgstr "양식 수정에 기반"

#: ../../content/applications/studio/automated_actions.rst:91
msgid ""
"The action is triggered when any change is done to a trigger field's value "
"on the :ref:`Form view <studio/views/general/form>`, even before saving the "
"record. This trigger only works on the user interface when a modification is"
" made by a user. If the field is changed through another action and not by "
"the user, the action will not run."
msgstr ""
"레코드를 저장하기 전이더라도, :ref:`양식보기 <studio/views/general/form>`에서 필드 값이 변경될 경우에는 "
"작업이 실행됩니다. 해당 작업 실행은 사용자가 수정하는 경우에 사용자의 인터페이스에서만 동작합니다. 필드값 변경이 다른 작업을 통해서 된"
" 경우 및 해당 사용자가 하지 않은 경우에는 작업이 실행되지 않습니다."

#: ../../content/applications/studio/automated_actions.rst:97
msgid ""
"This trigger can only be used with the :ref:`Execute Python Code action "
"<studio/automated-actions/action/python-code>`, so development is required."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:103
msgid "Based on Timed Condition"
msgstr "시간 기반 조건"

#: ../../content/applications/studio/automated_actions.rst:105
msgid ""
"The action is triggered when a trigger field's date or date & time value is "
"reached."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:107
msgid ""
"To trigger the action after the :guilabel:`Trigger Date`, add a number of "
"minutes, hours, days, or months under :guilabel:`Delay after trigger date`. "
"To trigger the action before, add a negative number instead."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:112
msgid ""
"If you want to send a reminder email 30 minutes before the start of a "
"calendar event, select the :guilabel:`Start (Calendar Event)` under "
":guilabel:`Trigger Date` and set the :guilabel:`Delay after trigger date` to"
" **-30** :guilabel:`Minutes`."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:0
msgid "Example of a Based on Timed Condition trigger"
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:121
msgid "By default, the scheduler checks for trigger dates every 4 hours."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:126
msgid "Apply on"
msgstr "적용"

#: ../../content/applications/studio/automated_actions.rst:128
msgid ""
"Define on which records of the model the automated action should be applied."
" It works the same way as when you apply filters on a model."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:134
msgid "Action"
msgstr "추가 작업"

#: ../../content/applications/studio/automated_actions.rst:136
msgid ""
"Determine what the automated action should do (server action). There are "
"eight types of action to choose from."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:142
msgid "Execute Python Code"
msgstr "파이썬 코드 실행"

#: ../../content/applications/studio/automated_actions.rst:144
msgid ""
"The action is used to execute Python code. The available variables are "
"described on the :guilabel:`Python Code` tab, which is also used to write "
"your code, or on the :guilabel:`Help` tab."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:147
msgid ""
"To allow the action to be run through the website, tick :guilabel:`Available"
" on the Website` and add a :guilabel:`Website Path`."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:153
msgid "Create a new Record"
msgstr "새 레코드 만들기"

#: ../../content/applications/studio/automated_actions.rst:155
msgid "The action is used to create a new record on any model."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:158
msgid ""
"Selecting a :guilabel:`Target Model` is only required if you want to target "
"another model than the one you are on."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:161
msgid ""
"To link the record that triggered the creation of the new record, select a "
"field under :guilabel:`Link Field`. For example, you could create a contact "
"automatically when a lead is turned into an opportunity."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:164
msgid ""
":guilabel:`Data to Write` tab: the tab is used to specify the new record's "
"values. After selecting a :guilabel:`Field`, select its "
":guilabel:`Evaluation Type`:"
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:167
msgid ""
":guilabel:`Value`: used to directly give the field's raw value in the "
":guilabel:`Value` column."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:168
msgid ""
":guilabel:`Reference`: used to select the record under the "
":guilabel:`Record` column and let Studio add the internal ID in the "
":guilabel:`Value` column."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:172
msgid ""
"If an automated action creates a new task in a project, you can assign it to"
" a specific user by setting the :guilabel:`Field` to :guilabel:`Responsible "
"User (Project)`, the :guilabel:`Evaluation Type` to :guilabel:`Reference`, "
"and the :guilabel:`Record` to a specific user."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:0
msgid "Example of a Create a new Record action"
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:181
msgid ""
":guilabel:`Python expression`: used to dynamically define the newly created "
"record’s value for a field using Python code in the :guilabel:`Value` "
"column."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:187
msgid "Update the Record"
msgstr "레코드 업데이트"

#: ../../content/applications/studio/automated_actions.rst:189
msgid ""
"The action is used to set value(s) for field(s) of any record on the current"
" model."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:192
msgid ""
"The process to fill in the :guilabel:`Data to Write` tab is the same as "
"described under :ref:`studio/automated-actions/action/new-record`."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:198
msgid "Execute several actions"
msgstr "몇 가지 작업 실행"

#: ../../content/applications/studio/automated_actions.rst:200
msgid ""
"The action is used to trigger multiple actions at the same time. To do so, "
"click on :guilabel:`Add a line` under the :guilabel:`Actions` tab. In the "
":guilabel:`Child Actions` pop-up, click on :guilabel:`Create` and configure "
"the action."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:207
msgid "Send Email"
msgstr "이메일 전송"

#: ../../content/applications/studio/automated_actions.rst:209
msgid ""
"The action is used to send an email to a contact linked to a specific "
"record. To do so, select or create an :guilabel:`Email Template`."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:215
msgid "Add Followers"
msgstr "팔로워 추가하기"

#: ../../content/applications/studio/automated_actions.rst:217
msgid "The action is used to subscribe existing contacts to the record."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:222
msgid "Create Next Activity"
msgstr "다음 활동 만들기"

#: ../../content/applications/studio/automated_actions.rst:224
msgid ""
"The action is used to schedule a new activity linked to the record. Use the "
":guilabel:`Activity` tab to set it up as usual, but instead of the "
":guilabel:`Assigned to` field, select an :guilabel:`Activity User Type`. "
"Select :guilabel:`Specific User` and add the user under "
":guilabel:`Responsible` if the activity should always be assigned to the "
"same user. To dynamically target a user linked to the record, select "
":guilabel:`Generic User From Record` instead and change the :guilabel:`User "
"field name` if necessary."
msgstr ""
"작업은 기록에 연결된 새로운 활동을 예약하는 데 사용합니다. :guilabel:`활동` 탭을 사용하여 평소대로 설정하되, "
":guilabel:`배정 대상` 필드 대신 :guilabel:`활동 사용자 유형`을 선택합니다. 활동이 항상 동일한 사용자에게 할당되어야"
" 하는 경우에는 :guilabel:`특정 사용자`를 선택하고 :guilabel:`담당자` 아래에 사용자를 추가합니다. 레코드에 연결된 "
"사용자를 동적으로 타겟팅하려면 대신 :guilabel:`레코드의 일반 사용자`를 선택하고 필요한 경우 :guilabel:`사용자 필드 "
"이름`을 변경합니다."

#: ../../content/applications/studio/automated_actions.rst:232
msgid ""
"After a lead is turned into an opportunity, you want your automated action "
"to set up a call for the user responsible for the lead. To do so, set the "
":guilabel:`Activity` to :guilabel:`Call` and set the :guilabel:`Activity "
"User Type` to :guilabel:`Generic User From Record`."
msgstr ""
"영업제안이 영업기회로 전환된 후에는, 자동화 작업을 통하여 해당 영업제안 담당자에게 전화를 걸도록 설정하고자 하는 경우가 있습니다. "
"이렇게 하려면, :guilabel:`활동`을 :guilabel:`통화`로 설정하고 :guilabel:`활동 사용자 유형`을 "
":guilabel:`레코드의 일반 사용자`로 설정합니다."

#: ../../content/applications/studio/automated_actions.rst:0
msgid "Example of a Create Next Activity action"
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:243
msgid "Send SMS Text Message"
msgstr "SMS 문자메시지 전송"

#: ../../content/applications/studio/automated_actions.rst:245
msgid ""
"The action is used to send an SMS to a contact linked to the record. To do "
"so, select or create an :guilabel:`SMS Template`."
msgstr ""

#: ../../content/applications/studio/automated_actions.rst:249
msgid ""
"If you want sent messages to be logged in the Chatter, tick :guilabel:`Log "
"as Note`."
msgstr ""

#: ../../content/applications/studio/fields.rst:3
msgid "Fields and widgets"
msgstr ""

#: ../../content/applications/studio/fields.rst:5
msgid ""
"Fields structure the models of a database. If you picture a model as a table"
" or spreadsheet, fields are the columns where data is stored in the records "
"(i.e., the rows). Fields also define the type of data that is stored within "
"them. How the data is presented and formatted on the :abbr:`UI (User "
"Interface)` is defined by their widget."
msgstr ""
"필드에서 데이터베이스의 모델을 구조화합니다. 모델을 테이블이나 스프레드시트라고 가정한다면, 필드는 레코드에 데이터가 저장되는 열 (즉, "
"행)입니다. 또한 필드는 내부에 저장되는 데이터의 유형을 정의합니다. 데이터가 표시되고 형식이 지정되는 방식은 해당 위젯에 의해 "
"정의됩니다."

#: ../../content/applications/studio/fields.rst:10
msgid ""
"From a technical point of view, there are 15 field types in Odoo. However, "
"you can choose from 20 fields in Studio, as some field types are available "
"more than once with a different default widget."
msgstr ""

#: ../../content/applications/studio/fields.rst:14
msgid ""
":guilabel:`New Fields` can only be added to the "
":ref:`studio/views/general/form` and :ref:`studio/views/multiple-"
"records/list` views. On other views, you can only add :guilabel:`Existing "
"Fields` :dfn:`(fields already on the model)`."
msgstr ""

#: ../../content/applications/studio/fields.rst:21
msgid "Simple fields"
msgstr ""

#: ../../content/applications/studio/fields.rst:23
msgid "Simple fields contain basic values, such as text, numbers, files, etc."
msgstr ""

#: ../../content/applications/studio/fields.rst:26
#: ../../content/applications/studio/fields.rst:325
msgid ""
"Non-default widgets, when available, are presented as bullet points below."
msgstr ""

#: ../../content/applications/studio/fields.rst:31
msgid "Text (`char`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:33
msgid ""
"The :guilabel:`Text` field is used for short text containing any character. "
"One text line is displayed when filling out the field."
msgstr ""

#: ../../content/applications/studio/fields.rst:36
#: ../../content/applications/studio/fields.rst:220
msgid ""
":guilabel:`Badge`: displays the value inside a rounded shape, similar to a "
"tag. The value cannot be edited on the UI, but a default value can be set."
msgstr ""

#: ../../content/applications/studio/fields.rst:38
#: ../../content/applications/studio/fields.rst:71
msgid ""
":guilabel:`Copy to Clipboard`: users can copy the value by clicking a "
"button."
msgstr ""

#: ../../content/applications/studio/fields.rst:39
msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link."
msgstr ""

#: ../../content/applications/studio/fields.rst:40
msgid ""
":guilabel:`Image`: displays an image using a URL. The value cannot be edited"
" manually, but a default value can be set."
msgstr ""

#: ../../content/applications/studio/fields.rst:44
msgid ""
"This works differently than selecting the :ref:`Image field "
"<studio/fields/simple-fields/image>` directly, as the image is not stored in"
" Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget."
" For example, it can be useful if you want to save disk space."
msgstr ""

#: ../../content/applications/studio/fields.rst:49
msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link."
msgstr ""

#: ../../content/applications/studio/fields.rst:52
msgid ""
"Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from "
"Odoo next to the field."
msgstr ""

#: ../../content/applications/studio/fields.rst:55
msgid ":guilabel:`URL`: the value becomes a clickable URL."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Text fields with different widgets"
msgstr ""

#: ../../content/applications/studio/fields.rst:66
msgid "Multiline Text (`text`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:68
msgid ""
"The :guilabel:`Multiline Text` field is used for longer text containing any "
"type of character. Two text lines are displayed on the UI when filling out "
"the field."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Multiline Text fields with different widgets"
msgstr ""

#: ../../content/applications/studio/fields.rst:82
msgid "Integer (`integer`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:84
msgid ""
"The :guilabel:`Integer` field is used for all integer numbers "
"(:dfn:`positive, negative, or zero, without a decimal`)."
msgstr ""

#: ../../content/applications/studio/fields.rst:87
msgid ""
":guilabel:`Percentage Pie`: displays the value inside a percentage circle, "
"usually for a computed value. The value cannot be edited on the UI, but a "
"default value can be set."
msgstr ""

#: ../../content/applications/studio/fields.rst:89
#: ../../content/applications/studio/fields.rst:118
msgid ""
":guilabel:`Progress Bar`: displays the value next to a percentage bar, "
"usually for a computed value. The field cannot be edited manually, but a "
"default value can be set."
msgstr ""

#: ../../content/applications/studio/fields.rst:91
msgid ""
":guilabel:`Handle`: displays a drag handle icon to order records manually in"
" :ref:`List view <studio/views/multiple-records/list>`."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Integer fields with different widgets"
msgstr ""

#: ../../content/applications/studio/fields.rst:103
msgid "Decimal (`float`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:105
msgid ""
"The :guilabel:`Decimal` field is used for all decimal numbers "
"(:dfn:`positive, negative, or zero, with a decimal`)."
msgstr ""

#: ../../content/applications/studio/fields.rst:109
msgid ""
"Decimal numbers are displayed with two decimals after the decimal point on "
"the UI, but they are stored in the database with more precision."
msgstr ""

#: ../../content/applications/studio/fields.rst:112
msgid ""
":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field "
"<studio/fields/simple-fields/monetary>`. It is recommended to use the later "
"as it offers more functionalities."
msgstr ""

#: ../../content/applications/studio/fields.rst:115
msgid ""
":guilabel:`Percentage`: displays a percent character `%` after the value."
msgstr ""

#: ../../content/applications/studio/fields.rst:116
msgid ""
":guilabel:`Percentage Pie`: displays the value inside a percentage circle, "
"usually for a computed value. The field cannot be edited manually, but a "
"default value can be set."
msgstr ""

#: ../../content/applications/studio/fields.rst:120
msgid ""
":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum "
"of 59 minutes."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Decimal fields with different widgets"
msgstr ""

#: ../../content/applications/studio/fields.rst:131
msgid "Monetary (`monetary`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:133
msgid "The :guilabel:`Monetary` field is used for all monetary values."
msgstr ""

#: ../../content/applications/studio/fields.rst:136
msgid ""
"When you first add a :guilabel:`Monetary` field, you are prompted to add a "
":guilabel:`Currency` field if none exists already on the model. Odoo offers "
"to add the :guilabel:`Currency` field for you. Once it is added, add the "
":guilabel:`Monetary` field again."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Example of a Monetary field along with its Currency field"
msgstr ""

#: ../../content/applications/studio/fields.rst:149
msgid "Html (`html`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:151
msgid ""
"The :guilabel:`Html` field is used to add text that can be edited using the "
"Odoo HTML editor."
msgstr ""

#: ../../content/applications/studio/fields.rst:153
msgid ""
":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing "
"raw HTML."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Html fields with different widgets"
msgstr ""

#: ../../content/applications/studio/fields.rst:164
msgid "Date (`date`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:166
msgid "The :guilabel:`Date` field is used to select a date on a calendar."
msgstr ""

#: ../../content/applications/studio/fields.rst:168
msgid ""
":guilabel:`Remaining Days`: the remaining number of days before the selected"
" date is displayed (e.g., *In 5 days*), based on the current date."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Date fields with different widgets"
msgstr ""

#: ../../content/applications/studio/fields.rst:180
msgid "Date & Time (`datetime`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:182
msgid ""
"The :guilabel:`Date & Time` field is used to select a date on a calendar and"
" a time on a clock. The user's current time is automatically used if no time"
" is set."
msgstr ""

#: ../../content/applications/studio/fields.rst:185
msgid ""
":guilabel:`Date`: used to record the time without displaying it on the UI."
msgstr ""

#: ../../content/applications/studio/fields.rst:186
msgid ""
":guilabel:`Remaining days`: displays the remaining number of days before the"
" selected date (e.g., *In 5 days*), based on the current date and time."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Date & Time fields with different widgets"
msgstr ""

#: ../../content/applications/studio/fields.rst:198
msgid "Checkbox (`boolean`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:200
msgid ""
"The :guilabel:`Checkbox` field is used when a value should only be true or "
"false, indicated by checking or unchecking a checkbox."
msgstr ""

#: ../../content/applications/studio/fields.rst:203
msgid ""
":guilabel:`Button`: displays a radio button. The widget works without "
"switching to the edit mode."
msgstr ""

#: ../../content/applications/studio/fields.rst:204
msgid ""
":guilabel:`Toggle`: displays a toggle button. The widget works without "
"switching to the edit mode."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Checkbox fields with different widgets"
msgstr ""

#: ../../content/applications/studio/fields.rst:215
msgid "Selection (`selection`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:217
msgid ""
"The :guilabel:`Selection` field is used when users should select a single "
"value from a group of predefined values."
msgstr ""

#: ../../content/applications/studio/fields.rst:222
msgid ""
":guilabel:`Badges`: displays all selectable values simultaneously inside "
"rectangular shapes, organized horizontally."
msgstr ""

#: ../../content/applications/studio/fields.rst:224
msgid ""
":guilabel:`Priority`: displays star symbols instead of values, which can be "
"used to indicate an importance or satisfaction level, for example. This has "
"the same effect as selecting the :ref:`Priority field <studio/fields/simple-"
"fields/priority>`, although, for the latter, four priority values are "
"already predefined."
msgstr ""

#: ../../content/applications/studio/fields.rst:228
#: ../../content/applications/studio/fields.rst:352
msgid ""
":guilabel:`Radio`: displays all selectable values at the same time as radio "
"buttons."
msgstr ""

#: ../../content/applications/studio/fields.rst:231
msgid ""
"By default, radio buttons are organized vertically. Tick :guilabel:`display "
"horizontally` to switch the way they are displayed."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Examples of Selection fields with different widgets"
msgstr ""

#: ../../content/applications/studio/fields.rst:243
msgid "Priority (`selection`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:245
msgid ""
"The :guilabel:`Priority` field is used to display a three-star rating "
"system, which can be used to indicate importance or satisfaction level. This"
" field type is a :ref:`Selection field <studio/fields/simple-"
"fields/selection>` with the :guilabel:`Priority` widget selected by default "
"and four priority values predefined. Consequently, the :guilabel:`Badge`, "
":guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets "
"have the same effects as described under :ref:`Selection "
"<studio/fields/simple-fields/selection>`."
msgstr ""
":guilabel:`우선순위` 필드는 별 3개로 등급 시스템을 표시하여 중요도나 만족도 수준을 나타내는 데 사용할 수 있습니다. 이 필드"
" 유형은 :ref:`선택 필드 <studio/fields/simple-fields/selection>`로, 기본값을 "
":guilabel:`우선순위` 위젯으로 하여 우선순위 값 4개가 사전 지정되어 있습니다. 따라서, :guilabel:`배지`, "
":guilabel:`배지들`, :guilabel:`라디오` 및 :guilabel:`선택` 위젯은 :ref:`선택 "
"<studio/fields/simple-fields/selection>` 항목에서 설명한 것과 같은 효과를 가져오게 됩니다."

#: ../../content/applications/studio/fields.rst:253
msgid ""
"To change the number of available stars by adding or removing values, click "
":guilabel:`Edit Values`. Note that the first value is equal to 0 stars "
"(i.e., when no selection is made), so having four values results in a three-"
"star rating system, for example."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Example of a Priority field"
msgstr ""

#: ../../content/applications/studio/fields.rst:266
msgid "File (`binary`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:268
msgid ""
"The :guilabel:`File` field is used to upload any type of file, or sign a "
"form (:guilabel:`Sign` widget)."
msgstr ""

#: ../../content/applications/studio/fields.rst:271
msgid ""
":guilabel:`Image`: users can upload an image file, which is then displayed "
"in :ref:`Form view <studio/views/general/form>`. This has the same effect as"
" using the :ref:`Image field <studio/fields/simple-fields/image>`."
msgstr ""

#: ../../content/applications/studio/fields.rst:274
msgid ""
":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then "
"browsed from the :ref:`Form view <studio/views/general/form>`."
msgstr ""

#: ../../content/applications/studio/fields.rst:276
msgid ""
":guilabel:`Sign`: users can electronically sign the form. This has the same "
"effect as selecting the :ref:`Sign field <studio/fields/simple-"
"fields/sign>`."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Examples of File fields with different widgets"
msgstr ""

#: ../../content/applications/studio/fields.rst:288
msgid "Image (`binary`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:290
msgid ""
"The :guilabel:`Image` field is used to upload an image and display it in "
":ref:`Form view <studio/views/general/form>`. This field type is a "
":ref:`File field <studio/fields/simple-fields/file>` with the "
":guilabel:`Image` widget selected by default. Consequently, the "
":guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have "
"the same effects as described under :ref:`File <studio/fields/simple-"
"fields/file>`."
msgstr ""

#: ../../content/applications/studio/fields.rst:297
msgid ""
"To change the display size of uploaded images, select :guilabel:`Small`, "
":guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option."
msgstr ""

#: ../../content/applications/studio/fields.rst:303
msgid "Sign (`binary`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:305
msgid ""
"The :guilabel:`Sign` field is used to sign the form electronically. This "
"field type is a :ref:`File field <studio/fields/simple-fields/file>` with "
"the :guilabel:`Sign` widget selected by default. Consequently, the "
":guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have"
" the same effects as described under :ref:`File <studio/fields/simple-"
"fields/file>`."
msgstr ""

#: ../../content/applications/studio/fields.rst:311
msgid ""
"To give users the :guilabel:`Auto` option when having to draw their "
"signature, select one of the available :guilabel:`Auto-complete with` fields"
" (:ref:`Text <studio/fields/simple-fields/text>`, :ref:`Many2One "
"<studio/fields/relational-fields/many2one>`, and :ref:`Related Field "
"<studio/fields/relational-fields/related-field>` on the model only). The "
"signature is automatically generated using the data from the selected field."
msgstr ""

#: ../../content/applications/studio/fields.rst:320
msgid "Relational fields"
msgstr ""

#: ../../content/applications/studio/fields.rst:322
msgid ""
"Relational fields are used to link and display the data from records on "
"another model."
msgstr ""

#: ../../content/applications/studio/fields.rst:330
msgid "Many2One (`many2one`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:332
msgid ""
"The :guilabel:`Many2One` field is used to link another record (from another "
"model) to the record being edited. The record's name from the other model is"
" then displayed on the record being edited."
msgstr ""

#: ../../content/applications/studio/fields.rst:336
msgid ""
"On the *Sales Order* model, the :guilabel:`Customer` field is a "
":guilabel:`Many2One` field pointing at the *Contact* model. This allows "
"**many** sales orders to be linked to **one** contact (customer)."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Diagram showing a many2one relationship"
msgstr ""

#: ../../content/applications/studio/fields.rst:345
msgid ""
"To prevent users from creating a new record in the linked model, tick "
":guilabel:`Disable creation`."
msgstr ""

#: ../../content/applications/studio/fields.rst:347
msgid ""
"To prevent users from opening records in a pop-up window, tick "
":guilabel:`Disable opening`."
msgstr ""

#: ../../content/applications/studio/fields.rst:348
msgid ""
"To help users only select the right record, click on :guilabel:`Domain` to "
"create a filter."
msgstr ""

#: ../../content/applications/studio/fields.rst:350
msgid ""
":guilabel:`Badge`: displays the value inside a rounded shape, similar to a "
"tag. The value cannot be edited on the UI."
msgstr ""

#: ../../content/applications/studio/fields.rst:357
msgid "One2Many (`one2many`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:359
msgid ""
"The :guilabel:`One2Many` field is used to display the existing relations "
"between a record on the current model and multiple records from another "
"model."
msgstr ""

#: ../../content/applications/studio/fields.rst:363
msgid ""
"You could add a :guilabel:`One2Many` field on the *Contact* model to look at"
" **one** customer's **many** sales orders."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Diagram showing a one2many relationship"
msgstr ""

#: ../../content/applications/studio/fields.rst:371
msgid ""
"To use a :guilabel:`One2Many` field, the two models must have been linked "
"already using a :ref:`Many2One field <studio/fields/relational-"
"fields/many2one>`. One2Many relations do not exist independently: a reverse-"
"search of existing Many2One relations is performed."
msgstr ""

#: ../../content/applications/studio/fields.rst:378
msgid "Lines (`one2many`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:380
msgid ""
"The :guilabel:`Lines` field is used to create a table with rows and columns "
"(e.g., the lines of products on a sales order)."
msgstr ""

#: ../../content/applications/studio/fields.rst:384
msgid ""
"To modify the columns, click on the :guilabel:`Lines` field and then "
":guilabel:`Edit List View`. To edit the form that pops up when a user clicks"
" on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Example of a Lines field"
msgstr ""

#: ../../content/applications/studio/fields.rst:397
msgid "Many2Many (`many2many`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:399
msgid ""
"The :guilabel:`Many2Many` field is used to link multiple records from "
"another model to multiple records on the current model. Many2Many fields can"
" use :guilabel:`Disable creation`, :guilabel:`Disable opening`, "
":guilabel:`Domain`, just like :ref:`Many2One fields "
"<studio/fields/relational-fields/many2one>`."
msgstr ""

#: ../../content/applications/studio/fields.rst:405
msgid ""
"On the *Task* model, the :guilabel:`Assignees` field is a "
":guilabel:`Many2Many` field pointing at the *Contact* model. This allows a "
"single user to be assigned to **many** tasks and **many** users to be "
"assigned to a single task."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Diagram showing many2many relationships"
msgstr ""

#: ../../content/applications/studio/fields.rst:413
msgid ""
":guilabel:`Checkboxes`: users can select several values using checkboxes."
msgstr ""

#: ../../content/applications/studio/fields.rst:414
msgid ""
":guilabel:`Tags`: users can select several values appearing in rounded "
"shapes, also known as *tags*. This has the same effect as selecting the "
":ref:`Tags field <studio/fields/relational-fields/tags>`."
msgstr ""

#: ../../content/applications/studio/fields.rst:421
msgid "Tags (`many2many`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:423
msgid ""
"The :guilabel:`Tags` field is used to display several values from another "
"model appearing in rounded shapes, also known as *tags*. This field type is "
"a :ref:`Many2Many field <studio/fields/relational-fields/many2many>` with "
"the :guilabel:`Tags` widget selected by default. Consequently, the "
":guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same "
"effects as described under :ref:`Many2Many <studio/fields/relational-"
"fields/many2many>`."
msgstr ""
":guilabel:`태그` 필드는 다른 모델에 있는 여러 가지의 값을 나타내기 위해 사용하며, 원 모양으로 표시하여 *태그*라고 "
"지칭합니다. 이 필드 유형의 기본값은 :guilabel:`태그` 위젯이 기본적으로 선택되어 있는 :ref:`다대다 필드 "
"<studio/fields/relational-fields/many2many>`입니다. 따라서, :guilabel:`체크박스` 및 "
":guilabel:`다대다` 위젯은 :ref:`다대다 <studio/fields/relational-fields/many2many>` "
"항목에서 설명된 것과 동일한 효과를 가져오게 됩니다."

#: ../../content/applications/studio/fields.rst:430
msgid ""
"To display tags with different background colors, tick :guilabel:`Use "
"colors`."
msgstr ""

#: ../../content/applications/studio/fields.rst:0
msgid "Example of a Tags field"
msgstr ""

#: ../../content/applications/studio/fields.rst:441
msgid "Related Field (`related`)"
msgstr ""

#: ../../content/applications/studio/fields.rst:443
msgid ""
"A :guilabel:`Related Field` is not a relational field per se; no "
"relationship is created between models. It uses an existing relationship to "
"fetch and display information from another record."
msgstr ""

#: ../../content/applications/studio/fields.rst:447
msgid ""
"To display the email address of a customer on the *Sales Order* model, use "
"the :guilabel:`Related Field` `partner_id.email` by selecting "
":guilabel:`Customer` and then :guilabel:`Email`."
msgstr ""

#: ../../content/applications/studio/fields.rst:453
msgid "Properties"
msgstr "속성"

#: ../../content/applications/studio/fields.rst:455
msgid ""
":guilabel:`Invisible`: When it is not necessary for users to view a field on"
" the UI, tick :guilabel:`Invisible`. It helps clear the UI by only showing "
"the essential fields depending on a specific situation."
msgstr ""

#: ../../content/applications/studio/fields.rst:460
msgid ""
"On the *Form* view of the *Contact* model, the :guilabel:`Title` field only "
"appears when :guilabel:`Individual` is selected, as that field would not be "
"helpful for a :guilabel:`Company` contact."
msgstr ""

#: ../../content/applications/studio/fields.rst:465
msgid ""
"The :guilabel:`Invisible` attribute also applies to Studio. To view hidden "
"fields inside Studio, click on a view's :guilabel:`View` tab and tick "
":guilabel:`Show Invisible Elements`."
msgstr ""

#: ../../content/applications/studio/fields.rst:469
msgid ""
":guilabel:`Required`: If a field should always be completed by the user "
"before being able to proceed, tick :guilabel:`Required`."
msgstr ""

#: ../../content/applications/studio/fields.rst:471
msgid ""
":guilabel:`Read only`: If users should not be able to modify a field, tick "
":guilabel:`Read only`."
msgstr ""

#: ../../content/applications/studio/fields.rst:474
msgid ""
"You can choose to apply these three properties only for specific records by "
"clicking on :guilabel:`Conditional` and creating a filter."
msgstr ""

#: ../../content/applications/studio/fields.rst:477
msgid ""
":guilabel:`Label`: The :guilabel:`Label` is the field's name on the UI."
msgstr ""

#: ../../content/applications/studio/fields.rst:480
msgid ""
"This is not the same name as used in the PostgreSQL database. To view and "
"change the latter, activate the :ref:`Developer mode <developer-mode>`, and "
"edit the :guilabel:`Technical Name`."
msgstr ""

#: ../../content/applications/studio/fields.rst:483
msgid ""
":guilabel:`Help Tooltip`: To explain the purpose of a field, write a "
"description under :guilabel:`Help Tooltip`. It is displayed inside a tooltip"
" box when hovering with your mouse over the field's label."
msgstr ""

#: ../../content/applications/studio/fields.rst:486
msgid ""
":guilabel:`Placeholder`: To provide an example of how a field should be "
"completed, write it under :guilabel:`Placeholder`. It is displayed in light "
"gray in lieu of the field's value."
msgstr ""

#: ../../content/applications/studio/fields.rst:488
msgid ""
":guilabel:`Widget`: To change the default appearance or functionality of a "
"field, select one of the available widgets."
msgstr ""

#: ../../content/applications/studio/fields.rst:490
msgid ""
":guilabel:`Default value`: To add a default value to a field when a record "
"is created, use :guilabel:`Default value`."
msgstr ""

#: ../../content/applications/studio/fields.rst:492
msgid ""
":guilabel:`Limit visibility to groups`: To limit which users can see the "
"field, select a user access group."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:3
msgid "Models, modules, and apps"
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:5
msgid ""
"Models determine the logical structure of a database and how data is stored,"
" organized, and manipulated. In other words, a model is a table of "
"information that can be linked with other tables. A model usually represents"
" a business concept, such as a *sales order*, *contact*, or *product*."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:9
msgid ""
"Modules and apps contain various elements, such as models, views, data "
"files, web controllers, and static web data."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:13
msgid ""
"All apps are modules. Larger, standalone modules are typically referred to "
"as apps, whereas other modules usually serve as add-ons to said apps."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:19
msgid "Suggested features"
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:21
msgid ""
"When you create a new model or app with Studio, you can choose to add up to "
"14 features to speed up the creation process. These features bundle fields, "
"default settings, and views that are usually used together to provide some "
"standard functionality. Most of these features can be added later on, but "
"adding them from the start makes the model creation process much easier. "
"Furthermore, these features interact together in some cases to increase "
"their usefulness."
msgstr ""
"스튜디오를 사용하여 새로 모델이나 앱을 생성하는 경우 최대 14개 기능을 추가하여 생성 프로세스 속도를 높일 수 있습니다. 해당 기능은 "
"일반적으로 일부 표준 기능과 함께 사용되는 필드, 기본 설정 및 화면과 함께 번들로 제공됩니다. 대부분의 기능을 추후에 추가할 수 "
"있지만, 처음부터 추가해 놓으면 모델 생성 프로세스가 훨씬 쉬워집니다. 또한 이러한 기능은 함께 사용하면 경우에 따라 더욱 편리하게 "
"사용할 수 있습니다."

#: ../../content/applications/studio/models_modules_apps.rst:28
msgid ""
"Creating a model with the :ref:`studio/models-modules-apps/suggested-"
"features/picture` and :ref:`studio/models-modules-apps/suggested-"
"features/pipeline-stages` features enabled adds the image in the card layout"
" of the :ref:`Kanban view <studio/views/multiple-records/kanban>`."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:0
msgid ""
"Combination of the Picture and Pipeline stages features on the Kanban view"
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:39
msgid "Contact details"
msgstr "연락처 상세 정보"

#: ../../content/applications/studio/models_modules_apps.rst:41
msgid ""
"Selecting :guilabel:`Contact details` adds to the :ref:`Form view "
"<studio/views/general/form>` a :ref:`Many2One field "
"<studio/fields/relational-fields/many2one>` linked to the *Contact* model "
"and two of its :ref:`Related Fields <studio/fields/relational-"
"fields/related-field>`: :guilabel:`Phone` and :guilabel:`Email`. The "
":guilabel:`Contact` field is also added to the :ref:`List view "
"<studio/views/multiple-records/list>`, and the :ref:`Map view "
"<studio/views/multiple-records/map>` is activated."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:0
msgid "Contact details feature on the Form view"
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:57
msgid "User assignment"
msgstr "사용자 배정"

#: ../../content/applications/studio/models_modules_apps.rst:59
msgid ""
"Selecting :guilabel:`User assignment` adds to the :ref:`Form view "
"<studio/views/general/form>` a :ref:`Many2One field "
"<studio/fields/relational-fields/many2one>` linked to the *Contact* model, "
"with the following :guilabel:`Domain`: `Share User is not set` to only allow"
" the selection of *Internal Users*. In addition, the "
":guilabel:`many2one_avatar_user` widget is used to display the user's "
"avatar. The :guilabel:`Responsible` field is also added to the :ref:`List "
"view <studio/views/multiple-records/list>`."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:0
msgid "User assignment feature on the Form view"
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:75
msgid "Date & Calendar"
msgstr "날짜 & 캘린더"

#: ../../content/applications/studio/models_modules_apps.rst:77
msgid ""
"Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view "
"<studio/views/general/form>` a :ref:`Date field <studio/fields/simple-"
"fields/date>` and activates the :ref:`Calendar view "
"<studio/views/timeline/calendar>`."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:84
msgid "Date range & Gantt"
msgstr "날짜 범위 & 간트"

#: ../../content/applications/studio/models_modules_apps.rst:86
msgid ""
"Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view "
"<studio/views/general/form>` two :ref:`Date fields <studio/fields/simple-"
"fields/date>` next to each other: one to set a start date, the other to set "
"an end date, using the :guilabel:`daterange` widget, and activates the "
":ref:`Gantt view <studio/views/timeline/gantt>`."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:94
msgid "Pipeline stages"
msgstr "파이프라인 단계"

#: ../../content/applications/studio/models_modules_apps.rst:96
msgid ""
"Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view "
"<studio/views/multiple-records/kanban>`, adds several fields such as "
":ref:`Priority <studio/fields/simple-fields/priority>` and :guilabel:`Kanban"
" State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and "
":guilabel:`Done`. The :guilabel:`Pipeline status bar` and the "
":guilabel:`Kanban State` field are added to the :ref:`Form view "
"<studio/views/general/form>`. The :guilabel:`Color` field is added to the "
":ref:`List view <studio/views/multiple-records/list>`."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:105
msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:110
msgid "Tags"
msgstr "태그"

#: ../../content/applications/studio/models_modules_apps.rst:112
msgid ""
"Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and "
":ref:`studio/views/multiple-records/list` views a :ref:`Tags field "
"<studio/fields/relational-fields/tags>`, creating a *Tag* model with "
"preconfigured access rights in the process."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:120
msgid "Picture"
msgstr "사진"

#: ../../content/applications/studio/models_modules_apps.rst:122
msgid ""
"Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view "
"<studio/views/general/form>` an :ref:`Image field <studio/fields/simple-"
"fields/image>`."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:126
msgid "The :guilabel:`Picture` feature can be added at a later stage."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:131
msgid "Lines"
msgstr "내용"

#: ../../content/applications/studio/models_modules_apps.rst:133
msgid ""
"Selecting :guilabel:`Lines`: adds to the :ref:`Form view "
"<studio/views/general/form>` a :ref:`Lines field <studio/fields/relational-"
"fields/lines>` inside a :guilabel:`Tab` component."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:139
msgid "Notes"
msgstr "메모"

#: ../../content/applications/studio/models_modules_apps.rst:141
msgid ""
"Selecting :guilabel:`Notes` adds to the :ref:`Form view "
"<studio/views/general/form>` an :ref:`Html field <studio/fields/simple-"
"fields/html>` using the full width of the form."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:147
msgid "Monetary value"
msgstr "통화 가치"

#: ../../content/applications/studio/models_modules_apps.rst:149
msgid ""
"Selecting :guilabel:`Monetary value` adds to the "
":ref:`studio/views/general/form` and :ref:`studio/views/multiple-"
"records/list` views a :ref:`Monetary field <studio/fields/simple-"
"fields/monetary>`. The :ref:`studio/views/reporting/graph` and "
":ref:`studio/views/reporting/pivot` views are also activated."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:155
msgid "A *Currency* field is added and hidden from the view."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:160
msgid "Company"
msgstr "회사"

#: ../../content/applications/studio/models_modules_apps.rst:162
msgid ""
"Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` "
"and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field "
"<studio/fields/relational-fields/many2one>` linked to the *Company* model."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:167
msgid "This is only useful if you work in a multi-company environment."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:172
msgid "Custom Sorting"
msgstr "사용자 지정 정렬"

#: ../../content/applications/studio/models_modules_apps.rst:174
msgid ""
"Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view "
"<studio/views/multiple-records/list>` a drag handle icon to manually reorder"
" records."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:0
msgid "Custom Sorting feature on the List view"
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:186
msgid "Chatter"
msgstr "대화 메시지"

#: ../../content/applications/studio/models_modules_apps.rst:188
msgid ""
"Selecting :guilabel:`Chatter` adds to the :ref:`Form view "
"<studio/views/general/form>` Chatter functionalities (sending messages, "
"logging notes, and scheduling activities)."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:192
msgid "The :guilabel:`Chatter` feature can be added at a later stage."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:0
msgid "Chatter feature on the Form view"
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:203
msgid "Archiving"
msgstr "보관"

#: ../../content/applications/studio/models_modules_apps.rst:205
msgid ""
"Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form`"
" and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive`"
" action and hides archived records from searches and views by default."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:212
msgid "Export and import customizations"
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:214
msgid ""
"When you do any customization with Studio, a new module named "
":guilabel:`Studio customizations` is added to your database."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:217
msgid ""
"To export these customizations, go to :menuselection:`Main dashboard --> "
"Studio --> Customizations --> Export` to download a ZIP file containing all "
"customizations."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:220
msgid ""
"To import and install these customizations in another database, connect to "
"the destination database and go to :menuselection:`Main dashboard --> Studio"
" --> Customizations --> Import`, then upload the exported ZIP file before "
"clicking on the :guilabel:`Import` button."
msgstr ""

#: ../../content/applications/studio/models_modules_apps.rst:225
msgid ""
"Before importing, make sure the destination database contains the same apps "
"and modules as the source database. Studio does not add the underlying "
"modules as dependencies of the exported module."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:3
msgid "PDF reports"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:5
msgid ""
"With Studio, you can :ref:`edit existing PDF reports <studio/pdf-"
"reports/edit>` (e.g., invoices, quotations, etc.) or :ref:`create new ones "
"<studio/pdf-reports/edit>`."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:11
msgid "Default layout"
msgstr "기본 레이아웃"

#: ../../content/applications/studio/pdf_reports.rst:13
msgid ""
"The default layout of reports is managed outside Studio. Go to "
":menuselection:`Settings`, then, in the :guilabel:`Companies` section, click"
" :guilabel:`Configure Document Layout`. Layout settings are company-specific"
" but apply to all reports."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:18
msgid ""
"You can see how the different settings affect the report layout in the "
"report preview on the right, or download  a sample invoice PDF by clicking "
":guilabel:`Download PDF Preview`."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:21
msgid "Use the following settings:"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:25
msgid ":guilabel:`Layout`: Four layouts are available:"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:29
msgid "Light"
msgstr "가볍게"

#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Light report layout sample"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:34
msgid "Boxed"
msgstr "박스형"

#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Boxed report layout sample"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:39
msgid "Bold"
msgstr "굵은 도형"

#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Bold report layout sample"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:44
msgid "Striped"
msgstr "줄무늬"

#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Striped report layout sample"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:51
msgid ""
":guilabel:`Font`: Seven fonts are available: Lato, Roboto, Open Sans, "
"Montserrat, Oswald, Raleway, and Tajawal (which supports Arabic and Latin "
"scripts). Go to the `Google Fonts website <https://fonts.google.com/>`_ to "
"preview them."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:57
msgid ""
":guilabel:`Company logo`: Click the :guilabel:`Edit` button to upload or "
"change the logo. This adds the logo to the company’s record on the *Company*"
" model, which you can access by going to :menuselection:`Settings` and then "
"clicking :guilabel:`Update Info` in the :guilabel:`Companies` section."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:64
msgid ""
":guilabel:`Colors`: Change the primary and secondary colors used to "
"structure reports. The default colors are automatically generated based on "
"the colors of the logo."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:69
msgid ""
":guilabel:`Layout background`: The following backgrounds are available:"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:71
msgid ":guilabel:`Blank`: nothing is displayed."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:72
msgid ""
":guilabel:`Geometric`: an image featuring geometric shapes is displayed in "
"the background."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:73
msgid ":guilabel:`Custom`: upload a custom background image."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:77
msgid ""
":guilabel:`Company tagline`: This is displayed in the header of "
":ref:`external reports <studio/pdf-reports/header-footer/external>`. You can"
" add multiple lines of text."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:82
msgid ""
":guilabel:`Company details`: These are displayed in the header of "
":ref:`external reports <studio/pdf-reports/header-footer/external>`. You can"
" add multiple lines of text."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:87
msgid ""
":guilabel:`Footer`: This text is used in the footer of :ref:`external "
"reports <studio/pdf-reports/header-footer/external>`. You can add multiple "
"lines of text. You can also edit the footer using the :ref:`report editor "
"<studio/pdf-reports/edit>`."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:93
msgid ""
":guilabel:`Paper format`: to define the default paper size of reports. You "
"can select :guilabel:`A4` (21 cm x 29.7 cm), :guilabel:`US Letter` (21.59 cm"
" x 27.54 cm), or :guilabel:`QR codes page`. This can also be defined for "
"individual reports in the :guilabel:`Paper format` field in :ref:`Studio "
"<studio/pdf-reports/create>`."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:101
msgid "Creating new PDF reports"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:103
msgid ""
"To create a new report for a model, access the model, click the **Toggle "
"Studio** button, then click :guilabel:`Reports`. Click :guilabel:`New` and, "
"in the popup window that opens, select the type of report. This is solely "
"used to determine what is displayed in the header and footer:"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:109
msgid ":guilabel:`External`:"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:111
msgid ""
"The header displays the company's :ref:`logo <studio/pdf-reports/default-"
"layout/logo>`, :ref:`tagline <studio/pdf-reports/default-layout/tagline>`, "
"and :ref:`details <studio/pdf-reports/default-layout/details>`."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:114
msgid ""
"The footer displays the values set in the :ref:`Footer <studio/pdf-"
"reports/default-layout/footer>` field and the page number."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:117
msgid ""
":guilabel:`Internal`: The header displays the user's current date and time, "
":guilabel:`Company Name`, and page number. There is no footer."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:120
msgid ""
":guilabel:`Blank`: There is neither a header nor a footer. Click in the "
"upper left corner of the page to edit the report."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:123
msgid ""
"Once you have created the report, you can start :ref:`editing it "
"<studio/pdf-reports/edit>`."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:128
msgid "Editing PDF reports"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:130
msgid ""
"To access the reports available for a model, access the model (e.g., sales "
"orders), click the **Toggle Studio** button, then click :guilabel:`Reports`."
" Select an existing report to open it or :ref:`create a new one <studio/pdf-"
"reports/create>`."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:135
msgid ""
"Alternatively, you can also open Studio, click :guilabel:`Reports`, and "
"search for a specific report or model."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:139
msgid ""
"It is strongly recommended to **duplicate** the standard report and perform "
"changes in the duplicated version. To duplicate a report, hover the mouse "
"pointer on the top right corner of the report, click the vertical ellipsis "
"icon (:guilabel:`⋮`), and then select :guilabel:`Duplicate`."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Duplicating a PDF report"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:148
msgid "Options"
msgstr "옵션"

#: ../../content/applications/studio/pdf_reports.rst:150
msgid ""
"Once you've selected or created a report, you can use the options in the "
"left part of the screen to:"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:152
msgid ""
"Change the :guilabel:`Report name`. The new name is applied everywhere (in "
"Studio, under the :guilabel:`Print` button, and in the PDF file name)."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:154
msgid ""
"Modify the :guilabel:`Paper format`. If no value is selected, the format "
"defined in the :ref:`default layout <studio/pdf-reports/default-"
"layout/paper>` is used."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:156
msgid ""
":guilabel:`Show in print menu`: to add the report in the :guilabel:`Print` "
"menu available from the record."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:158
msgid ""
":guilabel:`Reload from attachment`: to save the report as an attachment on "
"the record the first time it is generated and reload the original version of"
" the report any subsequent time. This is legally required for invoices and "
"is mainly used in this case."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:161
msgid ""
":guilabel:`Limit visibility to groups`: to limit the availability of the PDF"
" report to specific :doc:`user groups <../general/users/access_rights>`."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:163
msgid ""
":guilabel:`Edit sources`: to modify the report directly in the :ref:`XML "
"file <studio/pdf-reports/XML-editing>`."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:165
msgid ""
":guilabel:`Reset report`: to discard all changes made to the report and "
"reset it to its standard version."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:167
msgid ":guilabel:`Print preview`: to generate and download a report preview."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:170
msgid "Report editor"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:172
msgid ""
"The report editor allows you to modify the formatting and contents of the "
"report."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:175
msgid ""
"You can :guilabel:`Undo` or :guilabel:`Redo` changes using the related "
"buttons or the shortcuts `CTRL Z` and `CTRL Y`."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:178
msgid ""
"Changes are saved automatically when you leave the report or manually using "
"the :guilabel:`Save` button."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:181
msgid ""
"You can reset the report to its standard version by clicking the "
":guilabel:`Reset report` button in the left part of the screen."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:185
msgid ""
"Editing the header and footer of a report impacts all standard and custom "
"reports."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:188
msgid "Conditional blocks"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:190
msgid ""
"The dashed rectangles represent **conditional blocks** (*if/else* "
"statements). These are used to show/hide content based on specific "
"conditions. Click on the block to view the conditions."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst-1
msgid "View conditions applied to a block."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:196
msgid ""
"Select a value to preview its corresponding output and edit it if necessary."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst-1
msgid "Preview the output of another condition."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:202
msgid ""
"Conditions can only be edited in :ref:`XML <studio/pdf-reports/XML-"
"editing>`."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:205
msgid "Other content"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:207
msgid "There are two types of text content in reports:"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:209
msgid ""
"Static text, i.e., the text that's not highlighted in blue, which can be "
"modified directly in the editor."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:211
msgid ""
"Dynamic text, i.e., the text that's highlighted in blue, which is replaced "
"by field values when the report is generated, e.g., the SO number or the "
"quotation date."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:214
msgid ""
"You can add content (e.g., fields, lists, tables, images, banners, etc.) to "
"the report using commands. Type `/` to open the :ref:`powerbox "
"<knowledge/powerbox>`, then type the command's name or select it from the "
"list."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:218
msgid "To add static text to the report, type the text where you want it."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:220
msgid ""
"For more advanced changes, you can :ref:`edit the report in the XML directly"
" <studio/pdf-reports/XML-editing>`."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:226
msgid "Add a field"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:228
msgid ""
"To add a field, type `/` and select the :guilabel:`Field` command. In the "
"list that opens, select or search for the field; click the right arrow next "
"to the field name to access the list of related fields if needed. Then, "
"specify the default value and press `Enter`."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst-1
msgid "Select a related field."
msgstr "관련 필드를 선택하십시오."

#: ../../content/applications/studio/pdf_reports.rst:236
msgid "Add a data table"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:238
msgid ""
"Data tables are used to display :ref:`relational fields "
"<studio/fields/relational-fields>`. To add a data table, type `/`, select "
"the :guilabel:`Dynamic Table` command, and select the relation to be "
"displayed in the table."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:243
msgid ""
"Only relations of type `one2many` or `many2many` can be displayed as data "
"tables."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:245
msgid ""
"Once the table has been added, you can add columns using the table tools. "
"Position the cursor on top of the column, then click the purple rectangle "
"and select an option."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst-1
msgid "Add a column in a dynamic table."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:251
msgid ""
"You can then insert the :ref:`field of your choice <studio/pdf-reports/add-"
"field>` in the columns. The dialog box that opens shows the source object "
"for the field (e.g., the *Tag* model) and the list of available fields."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst-1
msgid "List of available fields for the Tag model."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:259
msgid ""
"The default row automatically iterates over the field's content, generating "
"a row on the report for each field value (e.g., one row per tag). You can "
"add static content rows above or below the generated rows using the table "
"tools."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:262
msgid ""
"You can also add data tables by :ref:`modifying the report's XML "
"<studio/pdf-reports/XML-editing>`."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:265
msgid "Formatting"
msgstr "서식"

#: ../../content/applications/studio/pdf_reports.rst:267
msgid ""
"To format text in the report, select it, then format it using the options in"
" the :ref:`knowledge/text-editor`."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Format text using the text editor."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:276
msgid "Editing the report's XML"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:279
msgid ""
"Modifying the XML directly may result in report issues during :doc:`upgrades"
" <../../../administration/upgrade>`. If this happens, simply copy your "
"changes from the old database into your upgraded database."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:283
msgid ""
"To edit the report's XML, click :guilabel:`Edit sources` in the left pane."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:286
msgid "Examples"
msgstr "예시"

#: ../../content/applications/studio/pdf_reports.rst:290
msgid ""
"Sometimes, tables are not properly recognized as such due to complex "
"structures. In those cases, you can still modify them manually in the report"
" XML. For example, with a sales order, you can find the following structure "
"in the XML (simplified for documentation purposes):"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:318
msgid ""
"To modify a table, you must ensure that each row has the same number of data"
" cells. For example, in the case above, you need to add a cell in the header"
" section (with e.g., the column title) and another one in the body section "
"with the field content (usually, with a `t-out` or `t-field` directive)."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:344
msgid ""
"Cells can span multiple rows or columns. For more information, go to the "
"`Mozilla Developer Network website <https://developer.mozilla.org/en-"
"US/docs/Learn/HTML/Tables/Basics>`_."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:347
msgid ""
"For example, you can modify the **Quotation/Order** report to add a column "
"to display the product category in the main table:"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Add a Product Category column in a SO."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:376
msgid ""
"To add a table in XML, you need to know the names of the fields and objects "
"you wish to access and display. As an example, let's add a table that "
"details the tags on a sales order:"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Add a data table in XML"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:407
msgid ""
"When adding tables manually, style them using `Bootstrap classes "
"<https://getbootstrap.com/docs/5.1/content/tables>`_, like the `table` class"
" included in the example above."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:413
msgid ""
"If you want to show/hide content based on specific conditions, you can "
"manually add `if/else` control statements in the report XML."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:416
msgid ""
"For example, if you want to hide a custom data table if there are no tags, "
"you can use the `t-if` attribute to define the condition, which is then "
"evaluated as `True` or `False`. The table will not be displayed if there are"
" no tags in the quotation."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:445
msgid ""
"If you want to display another block in case the `t-if` statement is "
"evaluated as `False`, you can specify it using the `t-else` statement. The "
"`t-else` block must directly follow the `t-if` block in the document "
"structure. There is no need to specify any condition in the `t-else` "
"attribute. As an example, let's show a quick message explaining that there "
"are no tags on the quotation:"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:477
msgid ""
"By using the `t-if/t-else` notation, the report editor recognizes that these"
" sections are mutually exclusive and should be displayed as conditional "
"blocks:"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Output preview if there are tags."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:483
msgid "You can switch conditions using the editor to preview their output:"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Output preview if there are no tags."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:488
msgid ""
"If you wish to have multiple options, you can also use `t-elif` directives "
"to add intermediary conditions. For example, this is how the title of sales "
"order reports changes based on the condition of the underlying document."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:501
msgid ""
"The title *Pro-Forma Invoice* is used depending on some contextual "
"conditions. If these conditions are not met and the state of the document is"
" either `draft` or `sent`, then *Quotation* is used. If none of those "
"conditions are met, the report's title is *Order*."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:507
msgid ""
"Working with images in a report can be challenging, as precise control over "
"image size and behavior is not always obvious. You can insert image fields "
"using the report editor (:ref:`by using the /Field command <studio/pdf-"
"reports/add-field>`), but inserting them in XML using the `t-field` "
"directive and accompanying `t-options` attributes provides better sizing and"
" positioning control."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:513
msgid ""
"For example, the following code outputs the field `image_128` of the line's "
"product as a 64px-wide image (with an automatic height based on the image's "
"aspect ratio)."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:520
msgid "The following options are available for image widgets:"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:522
msgid ""
"`width`: width of the image, usually in pixels or CSS length units (e.g., "
"`rem`) (leave empty for auto-width)."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:524
msgid ""
"`height`: height of the image, usually in pixels or CSS length units (e.g., "
"`rem`) (leave empty for auto-height)."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:526
msgid ""
"`class`: CSS classes applied on the `img` tag; `Bootstrap classes "
"<https://getbootstrap.com/docs/5.1/content/tables>`_ are available."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:528
msgid "`alt`: alternative text of the image"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:529
msgid ""
"`style`: style attribute; it allows you to override styles more freely than "
"with `Bootstrap classes "
"<https://getbootstrap.com/docs/5.1/content/tables>`_."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:532
msgid ""
"These attributes must contain strings, i.e., text enclosed within quotes "
"within quotes, e.g., `t-options-width=\"'64px'\"` (or, alternatively, a "
"valid Python expression)."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:536
msgid ""
"The image widget cannot be used on an `img` tag. Instead, set the `t-field` "
"directive on a `span` (for inline content) or `div` (for block content) "
"node."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:539
msgid ""
"For example, let's add a column with the product image in the quotation "
"table:"
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:567
msgid ""
"The `t-options-width` attribute restricts the image width to 64 pixels, and "
"the Bootstrap classes used in `t-options-class` create a thumbnail-like "
"border with rounded corners and a shadow."
msgstr ""

#: ../../content/applications/studio/pdf_reports.rst:0
msgid "Add a column with the product image in the quotation table."
msgstr ""

#: ../../content/applications/studio/views.rst:3
msgid "Views"
msgstr "화면"

#: ../../content/applications/studio/views.rst:5
msgid ""
"Views are the interface that allows displaying the data contained in a "
"model. One model can have several views, which are simply different ways to "
"show the same data. In Studio, views are organized into four categories: "
":ref:`general <studio/views/general>`, :ref:`multiple records "
"<studio/views/multiple-records>`, :ref:`timeline <studio/views/timeline>`, "
"and :ref:`reporting <studio/views/reporting>`."
msgstr ""
"화면은 모델에 있는 데이터를 표시할 수 있는 인터페이스입니다. 하나의 모델에는 여러 개의 화면이 있을 수 있는데, 동일한 데이터를 다르게"
" 표시한다는 점에서만 차이가 있습니다. 스튜디오에서 다음의 네 가지 카테고리로 화면을 설정합니다:ref:`일반 "
"<studio/views/general>`, :ref:`다중 레코드 <studio/views/multiple-records>`, "
":ref:`타임라인 <studio/views /timeline>` 및 :ref:`보고 <studio/views/reporting>`."

#: ../../content/applications/studio/views.rst:12
msgid ""
"To change the default view of a model, go to :menuselection:`Studio --> "
"Views --> Dropdown menu (⋮) --> Set as Default`."
msgstr ""

#: ../../content/applications/studio/views.rst:16
msgid ""
"You can modify views by using the built-in XML editor. To do so, activate "
":ref:`Developer mode <developer-mode>`, go to the view you want to edit, "
"select the :guilabel:`View` tab and then click on :guilabel:`</> XML`."
msgstr ""

#: ../../content/applications/studio/views.rst:21
msgid ""
"If you are editing a view using the XML editor, avoid making changes "
"directly to standard views and inherited views, as those would be reset and "
"would not be kept in case of an update or module upgrade. Always make sure "
"you select the right Studio inherited views. Indeed, when you modify a view "
"in Studio by drag-and-dropping a new field, a specific Studio inherited view"
" and its XPath, the latter which defines which part of the view is modified,"
" are automatically generated."
msgstr ""
"XML 편집기로 화면을 편집하는 경우, 업그레이드나 모듈 업그레이드를 할 때 초기화된 후 유지가 되지 않기 때문에 직접 표준 화면 및 "
"상속된 화면을 변경하지 마시기 바랍니다. 항상 스튜디오 상속 화면이 제대로 선택되어 있는지 확인합니다. 실제로 새로운 필드를 끌어다 "
"놓아서 스튜디오 화면을 수정하는 경우, 특정 스튜디오에서 상속된 화면 및 화면에서의 수정된 부분을 해당 XPath가 자동으로 생성되어 "
"정의합니다."

#: ../../content/applications/studio/views.rst:31
msgid "General views"
msgstr "일반 보기"

#: ../../content/applications/studio/views.rst:34
#: ../../content/applications/studio/views.rst:97
#: ../../content/applications/studio/views.rst:195
#: ../../content/applications/studio/views.rst:311
msgid ""
"The settings described below are found under the view's :guilabel:`View` tab"
" unless specified otherwise."
msgstr ""

#: ../../content/applications/studio/views.rst:40
msgid "Form"
msgstr "양식"

#: ../../content/applications/studio/views.rst:42
msgid ""
"The :guilabel:`Form` view is used when creating and editing records, such as"
" contacts, sales orders, products, etc."
msgstr ""

#: ../../content/applications/studio/views.rst:45
msgid ""
"To structure a form, drag-and-drop the :guilabel:`Tabs and Columns` element "
"found under the :guilabel:`+ Add` tab."
msgstr ""

#: ../../content/applications/studio/views.rst:47
#: ../../content/applications/studio/views.rst:132
msgid ""
"To prevent users from creating, editing, or deleting records, untick "
":guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`."
msgstr ""

#: ../../content/applications/studio/views.rst:0
msgid "Sales order model's Form view"
msgstr ""

#: ../../content/applications/studio/views.rst:59
msgid "Activity"
msgstr "활동"

#: ../../content/applications/studio/views.rst:61
msgid ""
"The :guilabel:`Activity` view is used to schedule and have an overview of "
"activities (emails, calls, etc.) linked to records."
msgstr ""

#: ../../content/applications/studio/views.rst:65
msgid "This view can only be modified within Studio by editing the XML code."
msgstr ""

#: ../../content/applications/studio/views.rst:0
msgid "Lead/Opportunity model's Activity view"
msgstr ""

#: ../../content/applications/studio/views.rst:76
msgid "Search"
msgstr "검색"

#: ../../content/applications/studio/views.rst:78
msgid ""
"The :guilabel:`Search` view is added on top of other views to filter, group,"
" and search records."
msgstr ""

#: ../../content/applications/studio/views.rst:80
msgid ""
"To add custom :guilabel:`Filters` and structure them using "
":guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop "
"them under :guilabel:`Filters`."
msgstr ""

#: ../../content/applications/studio/views.rst:82
msgid ""
"To add an existing field under the search dropdown menu, go to the "
":guilabel:`+ Add` tab and drag-and-drop it under :guilabel:`Autocompletion "
"Fields`."
msgstr ""

#: ../../content/applications/studio/views.rst:0
msgid "Project model's Search view on the Kanban view"
msgstr ""

#: ../../content/applications/studio/views.rst:94
msgid "Multiple records views"
msgstr "여러 레코드 보기"

#: ../../content/applications/studio/views.rst:103
msgid "Kanban"
msgstr "칸반"

#: ../../content/applications/studio/views.rst:105
msgid ""
"The :guilabel:`Kanban` view is often used to support business flows by "
"moving records across stages or as an alternative way to display records "
"inside *cards*."
msgstr ""

#: ../../content/applications/studio/views.rst:109
msgid ""
"If the :guilabel:`Kanban` view exists, it is used by default to display data"
" on mobile devices instead of the :ref:`List view <studio/views/multiple-"
"records/list>`."
msgstr ""

#: ../../content/applications/studio/views.rst:112
msgid ""
"To prevent users from creating new records, untick :guilabel:`Can Create`."
msgstr ""

#: ../../content/applications/studio/views.rst:113
msgid ""
"To create records directly within the view, in a minimalistic form, enable "
":guilabel:`Quick Create`."
msgstr ""

#: ../../content/applications/studio/views.rst:115
msgid ""
"To change the way records are grouped by default, select a new group under "
":guilabel:`Default Group by`."
msgstr ""

#: ../../content/applications/studio/views.rst:0
msgid "Project model's Kanban view"
msgstr ""

#: ../../content/applications/studio/views.rst:127
msgid "List"
msgstr "목록"

#: ../../content/applications/studio/views.rst:129
msgid ""
"The :guilabel:`List` view is used to overview many records at once, look for"
" records, and edit simple records."
msgstr ""

#: ../../content/applications/studio/views.rst:134
msgid ""
"To create and edit records directly within the view, select either "
":guilabel:`New record on top` or :guilabel:`New record at the bottom` under "
":guilabel:`Editable`."
msgstr ""

#: ../../content/applications/studio/views.rst:138
msgid ""
"This prevents users from opening records in :ref:`Form view "
"<studio/views/general/form>` from the :guilabel:`List` view."
msgstr ""

#: ../../content/applications/studio/views.rst:141
msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`."
msgstr ""

#: ../../content/applications/studio/views.rst:142
msgid ""
"To change the way records are sorted by default, select a field under "
":guilabel:`Sort By`."
msgstr ""

#: ../../content/applications/studio/views.rst:145
msgid ""
"To add a drag handle icon to reorder records manually, add an :ref:`Integer "
"field <studio/fields/simple-fields/integer>` with the :guilabel:`Handle` "
"widget."
msgstr ""

#: ../../content/applications/studio/views.rst:0
msgid "Drag handle icon enabling to sort records manually in List view"
msgstr ""

#: ../../content/applications/studio/views.rst:0
msgid "Sales order model's List view"
msgstr ""

#: ../../content/applications/studio/views.rst:161
msgid "Map"
msgstr "지도"

#: ../../content/applications/studio/views.rst:163
msgid ""
"The :guilabel:`Map` view is used to display records on a map. For example, "
"it is used in the Field Service app to plan an itinerary between different "
"tasks."
msgstr ""

#: ../../content/applications/studio/views.rst:167
msgid ""
"A :ref:`Many2One field <studio/fields/relational-fields/many2one>` linked to"
" the *Contact* model is required to activate the view, as the contact "
"address is used to position records on the map."
msgstr ""

#: ../../content/applications/studio/views.rst:170
msgid ""
"To select which kind of contact should be used on the map, select it under "
":guilabel:`Contact Field`."
msgstr ""

#: ../../content/applications/studio/views.rst:172
msgid ""
"To hide the name or the address of the record, tick :guilabel:`Hide name` or"
" :guilabel:`Hide Address`."
msgstr ""

#: ../../content/applications/studio/views.rst:174
msgid ""
"To add information from other fields, select them under "
":guilabel:`Additional Fields`."
msgstr ""

#: ../../content/applications/studio/views.rst:175
msgid ""
"To have a route suggested between the different records, tick "
":guilabel:`Enable Routing` and select which field should be used to sort "
"records for the routing."
msgstr ""

#: ../../content/applications/studio/views.rst:0
msgid "Task model's Map view"
msgstr ""

#: ../../content/applications/studio/views.rst:187
msgid "Timeline views"
msgstr "타임라인 보기"

#: ../../content/applications/studio/views.rst:190
msgid ""
"When you first activate one of the timeline views, you need to select which "
":ref:`Date <studio/fields/simple-fields/date>` or :ref:`Date & Time "
"<studio/fields/simple-fields/date-time>` fields on your model should be used"
" to define when the records start and stop in order to display them on the "
"view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop "
"Date Field` after activating the view."
msgstr ""
"타임라인 화면 중 하나를 처음 활성화할 경우, 레코드가 시작 및 중지되는 시점을 화면에 표시하기 위해 모델의 :ref:`날짜 "
"<studio/fields/simple-fields/date>` 또는 :ref:`날짜 및 시간 <studio/fields/simple-"
"fields/date-time>` 필드에서 선택해야 합니다. 화면 활성화 후 :guilabel:`시작 날짜 필드` 및 "
":guilabel:`중지 날짜 필드`를 수정할 수 있습니다."

#: ../../content/applications/studio/views.rst:201
msgid "Calendar"
msgstr "캘린더"

#: ../../content/applications/studio/views.rst:203
msgid ""
"The :guilabel:`Calendar` view is used to overview and manage records inside "
"a calendar."
msgstr ""

#: ../../content/applications/studio/views.rst:205
msgid ""
"To create records directly within the view instead of opening the :ref:`Form"
" view <studio/views/general/form>`, enable :guilabel:`Quick Create`."
msgstr ""

#: ../../content/applications/studio/views.rst:209
msgid ""
"This only works on specific models that can be *quick-created* using only a "
"*name*. However, most models do not support quick creation and open the "
":guilabel:`Form` view to fill in the required fields."
msgstr ""

#: ../../content/applications/studio/views.rst:213
msgid ""
"To color records on the calendar, select a field under :guilabel:`Color`. "
"All the records sharing the same value for that field are displayed using "
"the same color."
msgstr ""

#: ../../content/applications/studio/views.rst:217
msgid ""
"As the number of colors is limited, the same color can end up being assigned"
" to different values."
msgstr ""

#: ../../content/applications/studio/views.rst:220
msgid ""
"To display events lasting the whole day at the top of the calendar, select a"
" :ref:`Checkbox field <studio/fields/simple-fields/checkbox>` that specifies"
" if the event lasts the whole day."
msgstr ""

#: ../../content/applications/studio/views.rst:223
msgid ""
"To choose the default time scale used to display events, select "
":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` "
"under :guilabel:`Default Display Mode`."
msgstr ""

#: ../../content/applications/studio/views.rst:227
msgid ""
"You can also use :guilabel:`Delay Field` to display the duration of the "
"event in hours by selecting a :ref:`Decimal <studio/fields/simple-"
"fields/decimal>` or :ref:`Integer <studio/fields/simple-fields/integer>` "
"field on the model which specifies the duration of the event. However, if "
"you set an :guilabel:`End Date Field`, the :guilabel:`Delay Field` will not "
"be taken into account."
msgstr ""

#: ../../content/applications/studio/views.rst:0
msgid "Calendar Event model's Calendar view"
msgstr ""

#: ../../content/applications/studio/views.rst:242
msgid "Cohort"
msgstr "코호트"

#: ../../content/applications/studio/views.rst:244
msgid ""
"The :guilabel:`Cohort` view is used to examine the life cycle of records "
"over a time period. For example, it is used in the Subscriptions app to view"
" the subscriptions' retention rate."
msgstr ""

#: ../../content/applications/studio/views.rst:247
msgid ""
"To display a measure (i.e., the aggregated value of a given field) by "
"default on the view, select a :guilabel:`Measure Field`."
msgstr ""

#: ../../content/applications/studio/views.rst:249
msgid ""
"To choose which time interval is used by default to group results, select "
":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` "
"under :guilabel:`Interval`."
msgstr ""

#: ../../content/applications/studio/views.rst:251
msgid ""
"To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` "
":dfn:`the percentage of records staying over a period of time, it starts at "
"100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of "
"records moving out over a period of time - it starts at 0% and increases "
"with time`."
msgstr ""

#: ../../content/applications/studio/views.rst:255
msgid ""
"To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, "
"select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` "
"(from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is "
"used."
msgstr ""

#: ../../content/applications/studio/views.rst:0
msgid "Subscription model's Cohort view"
msgstr ""

#: ../../content/applications/studio/views.rst:268
msgid "Gantt"
msgstr "간트 차트"

#: ../../content/applications/studio/views.rst:270
msgid ""
"The :guilabel:`Gantt` view is used to forecast and examine the overall "
"progress of records. Records are represented by a bar under a time scale."
msgstr ""

#: ../../content/applications/studio/views.rst:273
msgid ""
"To prevent users from creating or editing records, untick :guilabel:`Can "
"Create` or :guilabel:`Can Edit`."
msgstr ""

#: ../../content/applications/studio/views.rst:275
msgid ""
"To fill cells in gray whenever a record should not be created there (e.g., "
"on weekends for employees), tick :guilabel:`Display Unavailability`."
msgstr ""

#: ../../content/applications/studio/views.rst:279
msgid ""
"The underlying model must support this feature, and support for it cannot be"
" added using Studio. It is supported for the Project, Time Off, Planning, "
"and Manufacturing apps."
msgstr ""

#: ../../content/applications/studio/views.rst:282
msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`."
msgstr ""

#: ../../content/applications/studio/views.rst:283
msgid ""
"To collapse multiple records in a single row, tick :guilabel:`Collapse First"
" Level`."
msgstr ""

#: ../../content/applications/studio/views.rst:284
msgid ""
"To choose which way records are grouped by default on rows (e.g., per "
"employee or project), select a field under :guilabel:`Default Group by`."
msgstr ""

#: ../../content/applications/studio/views.rst:286
msgid ""
"To define a default time scale to view records, select :guilabel:`Day`, "
":guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under "
":guilabel:`Default Scale`."
msgstr ""

#: ../../content/applications/studio/views.rst:288
msgid ""
"To color records on the view, select a field under :guilabel:`Color`. All "
"the records sharing the same value for that field are displayed using the "
"same color."
msgstr ""

#: ../../content/applications/studio/views.rst:292
msgid ""
"As the number of colors is limited, the same color can be assigned to "
"different values."
msgstr ""

#: ../../content/applications/studio/views.rst:294
msgid ""
"To specify with which degree of precision each time scale should be divided "
"by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or "
":guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or "
":guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month "
"Precision`."
msgstr ""

#: ../../content/applications/studio/views.rst:0
msgid "Planning Shift model's Gantt view"
msgstr ""

#: ../../content/applications/studio/views.rst:308
msgid "Reporting views"
msgstr "조회수 보고"

#: ../../content/applications/studio/views.rst:317
msgid "Pivot"
msgstr "피벗 테이블"

#: ../../content/applications/studio/views.rst:319
msgid ""
"The :guilabel:`Pivot` view is used to explore and analyze the data contained"
" in records in an interactive manner. It is especially useful to aggregate "
"numeric data, create categories, and drill down the data by expanding and "
"collapsing different levels of data."
msgstr ""

#: ../../content/applications/studio/views.rst:323
msgid ""
"To access all records whose data is aggregated under a cell, tick "
":guilabel:`Access records from cell`."
msgstr ""

#: ../../content/applications/studio/views.rst:325
msgid ""
"To divide the data into different categories, select field(s) under "
":guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or "
":guilabel:`Row grouping - Second level`."
msgstr ""

#: ../../content/applications/studio/views.rst:327
msgid ""
"To add different types of data to be measured using the view, select a field"
" under :guilabel:`Measures`."
msgstr ""

#: ../../content/applications/studio/views.rst:329
msgid ""
"To display a count of records that made up the aggregated data in a cell, "
"tick :guilabel:`Display count`."
msgstr ""

#: ../../content/applications/studio/views.rst:0
msgid "Purchase Report model's Pivot view"
msgstr ""

#: ../../content/applications/studio/views.rst:341
msgid "Graph"
msgstr "그래프"

#: ../../content/applications/studio/views.rst:343
msgid ""
"The :guilabel:`Graph` view is used to showcase data from records in a bar, "
"line, or pie chart."
msgstr ""

#: ../../content/applications/studio/views.rst:345
msgid ""
"To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or "
":guilabel:`Pie` under :guilabel:`Type`."
msgstr ""

#: ../../content/applications/studio/views.rst:347
msgid ""
"To choose a default data dimension (category), select a field under "
":guilabel:`First dimension` and, if needed, another under :guilabel:`Second "
"dimension`."
msgstr ""

#: ../../content/applications/studio/views.rst:349
msgid ""
"To select a default type of data to be measured using the view, select a "
"field under :guilabel:`Measure`."
msgstr ""

#: ../../content/applications/studio/views.rst:351
msgid ""
"*For Bar and Line charts only*: To sort the different data categories by "
"their value, select :guilabel:`Ascending` (from lowest to highest value) or "
":guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`."
msgstr ""

#: ../../content/applications/studio/views.rst:354
msgid ""
"*For Bar and Pie charts only*: To access all records whose data is "
"aggregated under a data category on the chart, tick :guilabel:`Access "
"records from graph`."
msgstr ""

#: ../../content/applications/studio/views.rst:356
msgid ""
"*For Bar charts only*: When using two data dimensions (categories), display "
"the two columns on top of each other by default by ticking "
":guilabel:`Stacked graph`."
msgstr ""

#: ../../content/applications/studio/views.rst:0
msgid "Sales Analysis Report model's Bar chart on Graph view"
msgstr ""

#: ../../content/applications/studio/views.rst:368
msgid "Dashboard"
msgstr "현황판"

#: ../../content/applications/studio/views.rst:370
msgid ""
"The :guilabel:`Dashboard` view is used to display multiple reporting views "
"and key performance indicators. Which elements are displayed on the view "
"depends on the configuration of the other reporting views."
msgstr ""

#: ../../content/applications/studio/views.rst:0
msgid "Sales Analysis Report model's Dashboard view"
msgstr ""