{"title":"국제화와 현지화","version":"2.2","locale":"ko","docname":"topics/i18n/index","url":"/ko/2.2/topics/i18n/","canonical":"https://djangodocs.dev/ko/2.2/topics/i18n/","summary":"개요 Link to this heading # 국제화와 현지화의 목표는 단일 웹 애플리케이션이 그 컨텐츠를 방문자의 언어와 포맷에 맞추어 제공하도록 하는 것입니다. Django는 텍스트 번역 , 날짜, 시간 및 숫자 형식 지정 , 그리고 시간대 에 대하여 완전히 지원합니다.…","html":"<h1>국제화와 현지화<a class=\"heading-anchor\" href=\"#internationalization-and-localization\"><span class=\"visually-hidden\">Link to this heading</span><span aria-hidden=\"true\">#</span></a></h1>\n<div class=\"toctree-wrapper compound\">\n</div>\n<section id=\"overview\">\n<h2>개요<a class=\"heading-anchor\" href=\"#overview\"><span class=\"visually-hidden\">Link to this heading</span><span aria-hidden=\"true\">#</span></a></h2>\n<p>국제화와 현지화의 목표는 단일 웹 애플리케이션이 그 컨텐츠를 방문자의 언어와 포맷에 맞추어 제공하도록 하는 것입니다.</p>\n<p>Django는 <a class=\"reference internal\" href=\"/ko/2.2/topics/i18n/translation/\"><span class=\"doc\">텍스트 번역</span></a>, <a class=\"reference internal\" href=\"/ko/2.2/topics/i18n/formatting/\"><span class=\"doc\">날짜, 시간 및 숫자 형식 지정</span></a>, 그리고 <a class=\"reference internal\" href=\"/ko/2.2/topics/i18n/timezones/\"><span class=\"doc\">시간대</span></a> 에 대하여 완전히 지원합니다.</p>\n<p>Essentially, Django does two things:</p>\n<ul class=\"simple\">\n<li><p>It allows developers and template authors to specify which parts of their apps\nshould be translated or formatted for local languages and cultures.</p></li>\n<li><p>It uses these hooks to localize Web apps for particular users according to\ntheir preferences.</p></li>\n</ul>\n<p>Obviously, translation depends on the target language, and formatting usually\ndepends on the target country. This information is provided by browsers in\nthe <code class=\"docutils literal notranslate\"><span class=\"pre\">Accept-Language</span></code> header. However, the time zone isn’t readily available.</p>\n</section>\n<section id=\"definitions\">\n<h2>정의<a class=\"heading-anchor\" href=\"#definitions\"><span class=\"visually-hidden\">Link to this heading</span><span aria-hidden=\"true\">#</span></a></h2>\n<p>“국제화” 와 “현지화”라는 단어는 종종 혼란을 일으킵니다; 여기에 간단한 정의가 있습니다:</p>\n<dl class=\"simple glossary\">\n<dt id=\"term-internationalization\">internationalization<a class=\"heading-anchor\" href=\"#term-internationalization\"><span class=\"visually-hidden\">Link to this term</span><span aria-hidden=\"true\">#</span></a></dt><dd><p>현지화 할 소프트웨어를 준비하는것. 보통 개발자가 완료하게 됩니다.</p>\n</dd>\n<dt id=\"term-localization\">localization<a class=\"heading-anchor\" href=\"#term-localization\"><span class=\"visually-hidden\">Link to this term</span><span aria-hidden=\"true\">#</span></a></dt><dd><p>번역과 현지의 형식을 작성하는 것. 보통 번역가가 완료하게 됩니다.</p>\n</dd>\n</dl>\n<p>더 자세한 것은 <a class=\"reference external\" href=\"https://en.wikipedia.org/wiki/Internationalization_and_localization\">W3C 국제화 자주 묻는 질문</a>, the <a class=\"reference external\" href=\"https://www.w3.org/International/questions/qa-i18n\">위키피디아의 글</a> or the <a href=\"#id1\"><span class=\"problematic\" id=\"id2\">`</span></a>GNU gettext 문서`_에서 찾아보실 수 있습니다.</p>\n<aside class=\"admonition admonition-warning\" role=\"note\">\n<p class=\"admonition-title\">경고</p>\n<p>번역과 형식 지정은 각각 <a class=\"reference internal\" href=\"/ko/2.2/ref/settings/#std-setting-USE_I18N\"><code class=\"xref std std-setting docutils literal notranslate\"><span class=\"pre\">USE_I18N</span></code></a> 와 <a class=\"reference internal\" href=\"/ko/2.2/ref/settings/#std-setting-USE_L10N\"><code class=\"xref std std-setting docutils literal notranslate\"><span class=\"pre\">USE_L10N</span></code></a> 의 설정에 의해서 제어됩니다. 그러나, 둘다 국제화와 현지화랑 관련이 있습니다. 설정의 이름은 장고 역사의 유감스러운 결과입니다.</p>\n</aside>\n<p>Here are some other terms that will help us to handle a common language:</p>\n<dl class=\"simple glossary\">\n<dt id=\"term-locale-name\">locale name<a class=\"heading-anchor\" href=\"#term-locale-name\"><span class=\"visually-hidden\">Link to this term</span><span aria-hidden=\"true\">#</span></a></dt><dd><p>A locale name, either a language specification of the form <code class=\"docutils literal notranslate\"><span class=\"pre\">ll</span></code> or a\ncombined language and country specification of the form <code class=\"docutils literal notranslate\"><span class=\"pre\">ll_CC</span></code>.\nExamples: <code class=\"docutils literal notranslate\"><span class=\"pre\">it</span></code>, <code class=\"docutils literal notranslate\"><span class=\"pre\">de_AT</span></code>, <code class=\"docutils literal notranslate\"><span class=\"pre\">es</span></code>, <code class=\"docutils literal notranslate\"><span class=\"pre\">pt_BR</span></code>. The language part is\nalways in lowercase and the country part in upper case. The separator is\nan underscore.</p>\n</dd>\n<dt id=\"term-language-code\">language code<a class=\"heading-anchor\" href=\"#term-language-code\"><span class=\"visually-hidden\">Link to this term</span><span aria-hidden=\"true\">#</span></a></dt><dd><p>Represents the name of a language. Browsers send the names of the\nlanguages they accept in the <code class=\"docutils literal notranslate\"><span class=\"pre\">Accept-Language</span></code> HTTP header using this\nformat. Examples: <code class=\"docutils literal notranslate\"><span class=\"pre\">it</span></code>, <code class=\"docutils literal notranslate\"><span class=\"pre\">de-at</span></code>, <code class=\"docutils literal notranslate\"><span class=\"pre\">es</span></code>, <code class=\"docutils literal notranslate\"><span class=\"pre\">pt-br</span></code>. Language codes\nare generally represented in lowercase, but the HTTP <code class=\"docutils literal notranslate\"><span class=\"pre\">Accept-Language</span></code>\nheader is case-insensitive. The separator is a dash.</p>\n</dd>\n<dt id=\"term-message-file\">message file<a class=\"heading-anchor\" href=\"#term-message-file\"><span class=\"visually-hidden\">Link to this term</span><span aria-hidden=\"true\">#</span></a></dt><dd><p>A message file is a plain-text file, representing a single language,\nthat contains all available <a class=\"reference internal\" href=\"#term-translation-string\"><span class=\"xref std std-term\">translation strings</span></a> and how they should be represented in the given\nlanguage. Message files have a <code class=\"docutils literal notranslate\"><span class=\"pre\">.po</span></code> file extension.</p>\n</dd>\n<dt id=\"term-translation-string\">translation string<a class=\"heading-anchor\" href=\"#term-translation-string\"><span class=\"visually-hidden\">Link to this term</span><span aria-hidden=\"true\">#</span></a></dt><dd><p>번역될 수 있는 것</p>\n</dd>\n<dt id=\"term-format-file\">format file<a class=\"heading-anchor\" href=\"#term-format-file\"><span class=\"visually-hidden\">Link to this term</span><span aria-hidden=\"true\">#</span></a></dt><dd><p>A format file is a Python module that defines the data formats for a given\nlocale.</p>\n</dd>\n</dl>\n</section>","rootId":"internationalization-and-localization","toc":[{"title":"개요","anchor":"overview","children":[]},{"title":"정의","anchor":"definitions","children":[]}],"breadcrumbs":[{"docname":"topics/index","title":"Django 사용하기","url":"/ko/2.2/topics/"}],"prev":{"docname":"topics/email","title":"이메일 보내기","url":"/ko/2.2/topics/email/"},"next":{"docname":"topics/i18n/translation","title":"번역","url":"/ko/2.2/topics/i18n/translation/"},"formats":{"html":"/ko/2.2/topics/i18n/","markdown":"/ko/2.2/topics/i18n.md","json":"/ko/2.2/topics/i18n.json"},"source":"https://github.com/django/django/blob/stable/2.2.x/docs/topics/i18n/index.txt","official":"https://docs.djangoproject.com/ko/2.2/topics/i18n/","inVersions":["6.1","6.0","5.2","5.1","5.0","4.2","4.1","4.0","3.2","3.1","3.0","2.2","2.1","2.0","1.11"],"inLocales":["en","zh-hans","fr","ja","id","pt-br","ko","es","el","pl"]}