Misplaced Pages

This is an old revision of this page, as edited by Seefooddiet (talk | contribs) at 06:52, 3 October 2024 (→Date format: Clarify). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

This idea is in the brainstorming stage. Feel free to add new ideas; improve, clarify and classify the ideas already here; and discuss the merits of these ideas on the talk page.

Shortcuts MOS:KO WP:MOS-KO WP:MOSKOREA

The following is a draft working towards a proposal for adoption as a Misplaced Pages policy, guideline, or process. The proposal must not be taken to represent consensus, but is still in development and under discussion, and has not yet reached the process of gathering consensus for adoption. Thus references or links to this page should not describe it as policy, guideline, nor yet even as a proposal.

This page in a nutshell: Attempt to unify MOS:KO and WP:NCKO and establish clear guidelines for romanization and referencing Korean sources.

The Manual of Style/Korea (MOS:KO) is a style guideline for Misplaced Pages articles that are significantly related to Korea.

This guideline should be considered subordinate and complimentary to the overall Misplaced Pages:Manual of Style. It is intended to provide extra guidance for Korea topics that the main MOS does not cover. MOS:KO should ideally not contradict the main MOS; if you believe it does, please post on the talk page. It should also ideally harmonize with other relevant manuals of style, particularly MOS:JA and MOS:ZH.

English spelling variety

• MOS:KO-ENGVAR

For South Korea–related articles, in general prefer the use of American English. Exception is if the article is significantly related to a country that uses a different variety of English; then consider using that variety.

English words of Korean origin

Some Korean-language terms have been adopted into the English language. If such a term can be found in at least one major reliable English-language dictionary (e.g. the famous traditional dictionaries) from a primarily English-speaking country, we consider it an English-language word. For example, "kimchi" and "chaebol".

Sometimes these terms have a WP:COMMONNAME spelling that differs from the output of typical romanization systems. As we are on the English Misplaced Pages, spell these terms using the most common spellings used in English sources. For instance, "chaebol" and not jaebeol (Revised Romanization) or chaebŏl (McCune–Reischauer). Also, do not italicize these words per MOS:FOREIGNITALIC. For how to pluralize such words, check what English dictionaries recommend. These words are often not pluralized; e.g. "kimchis" is uncommon.

Romanization

• MOS:KO-ROMAN
• MOS:KO-RR
• MOS:KO-MR
• MOS:KO-YALE

Many of the romanization decisions below are explained on the companion essay Misplaced Pages:WikiProject Korea/Romanization of Korean on Misplaced Pages.

When to romanize

Per MOS:NOTLATIN and WP:ACCESSIBILITY, you must romanize if a Korean term does not have a clear WP:COMMONNAME spelling or translation in English (see § Translating non-people names to English).

In general, per MOS:NON-ENG, you should use non-English terms sparingly. Korean terms can be used if they significantly add to understanding. E.g. don't write "maekju" when "beer" is sufficiently descriptive.

What Korean romanization to use

When romanizing a term:

1. Check to see if/how it is covered in § Naming conventions. That section may prescribe modifications to the strict romanizations dictated here.
2. Refer to the table below, and select the most appropriate romanization system based on when or where the term is primarily notable. If notable in multiple categories, prioritize recency.

Italicization of romanized terms

• MOS:KO-ITALICS

For the first time you use a romanized term, you should wrap it in the {{transliteration}} template, with parameters set to indicate which romanization system is being used. This will automatically italicize the term. Subsequent mentions of the term should not be wrapped, and just be italicized. Examples:

• RR: {{transliteration|ko|rr|tteokbokki}}
• MR: {{transliteration|ko|mr|ttŏkpokki}}
• Yale: {{transliteration|ko|yaleko|ttekpokki}}

If the term is a proper noun, you should not italicize. In the transliteration template, you can disable italicization by setting italic=no.

Capitalization of romanized terms

Except for romanized titles of § Works, which should be in sentence case, capitalization should generally follow MOS:CAPS. Notably for us, if a romanized term is not a proper noun, you should not capitalize it; there may be exceptions based on what is commonly done in reliable sources, however.

Hangul

• MOS:HANGUL
• WP:HANGUL
• WP:KOREANCHARS

When to use Hangul

The inclusion of Hangul in Korea-related articles is encouraged, provided that it follows the guidelines in this MOS. It can be helpful in clarifying what Korean concepts are being discussed in the Latin script. Romanizations can sometimes be identical for different Hangul, be irreversible, or be unorthodox. Furthermore, for English-language terms that are translations or official names for Korean terms, it can be difficult to understand what the original Korean name was, which possibly hinders researching or linking the concept being discussed.

Korean term as main subject of article

When the main subject of an article is a Korean-language term, you should display Hangul in the first sentence of the lead per § First parentheses. You can also display Hangul in § Infobox Korean name.

Gloss

• MOS:KO-GLOSS
• MOS:NOHANGUL

For any term that isn't the main term of the article, when a romanized or translated Korean term is used for the first time and if the term doesn't already have its own article, you should display Korean text for it in parentheses or a footnote using {{Korean}}. If the term already has its own article, link it.

YDol hareubang are also called janggunseok (장군석).

NDol hareubang (돌하르방) are also called janggunseok (장군석). (Dol hareubang has its own article already, doesn't need a gloss.)

Sometimes, even if a term has its own article, the original Hangul may be worth including anyway. In particular, if discussing etymology:

YBulgogi is compounded of the Korean words bul (불; lit. fire) and gogi (고기; lit. meat).

NBulgogi is compounded of the Korean words bul, which means "fire", and gogi, which means "meat".

Formatting Hangul

• MOS:HANGULFORMAT
• MOS:KO-LABELS

Hangul should be wrapped in preferably the {{Korean}} template. There are multiple reasons why Hangul should be wrapped like this. Labels can be hidden by setting labels=no. It is recommended to disable labels after the first use if Korean is the only non-Latin text present on the article. Repeated identical labels introduce visual clutter with little additional understanding. Translations can also be included using the |lit= parameter.

If you don't need to put Hanja, romanization, or translation right next to Hangul, you can alternatively use {{Lang|ko|...}}.

Example:

{{transliterate|ko|rr|]}} is compounded of the words {{transliterate|ko|rr|bibim}} ({{korean|비빔|lit=mixed}}) and {{transliterate|ko|rr|bap}} ({{korean|밥|lit=rice|labels=no}}).

Italics and bolding for Hangul

• MOS:HANGULITALICS
• MOS:HANGULBOLD

Do not use italics or bold for Hangul, per MOS:BADITALICS. The templates {{nobold}}, {{noitalic}}, and {{normal}} can be used to remove this formatting in places where it is the default, such as within infoboxes.

Hanja

• MOS:HANJA

When to use Hanja

In contemporary North and South Korea, Hanja is rarely used. However, it has a number of uses on Misplaced Pages, especially for historical topics.

Hanja for main topics

For the main topic of an article, you should display the Hanja for the topic generally only once or twice. For a concept with significance before the division of Korea in 1945, display the Hanja in both the first sentence of the lead per § First sentence and in the {{Infobox Korean name}}. For concepts mostly significant after the division, display the Hanja only in the Infobox Korean name; Hanja tends to be less important after that time, and we wish to minimize the amount of less important information in the first sentence.

Examples:

Y Goguryeo (Korean: 고구려; Hanja: 高句麗) was one of the Three Kingdoms of Korea.

Goguryeo is a pre-division concept and Hanja is frequently used for studies on it.

N Park Chung Hee (Korean: 박정희; Hanja: 朴正熙; November 14, 1917 – October 26, 1979) was the third President of South Korea.

Park Chung Hee is a person whose notability is mostly after the division, and Hanja is otherwise not particularly important for understanding who he was. Do not provide his name's Hanja in the first sentence, only provide it in the infobox.

Hanja for other terms

For terms that aren't the main subject of the article, follow similar principles to those used for Hangul in § Gloss. Additionally, if the topic is mostly relevant after the division, consider not displaying the Hanja at all if the Hangul is sufficient for grasping what is being discussed.

Providing Hanja alongside Hangul is helpful for disambiguation, explaining etymology, and for topics relating to time periods where the use of Hanja was widespread.

Formatting Hanja

In general, you should display Hanja and a corresponding Hangul reading together using the {{Korean}} template. If you wish to display only Hanja, use {{lang|ko|put Hanja here}}. We recommend against the use of the parameters ko-Hani and ko-Hant; dealing with them adds complication for little practical gain.

Partial Hanja

In some cases, only parts of Korean terms and names have corresponding Hanja. For example, a person's name with a native Korean given name: "Kim Da-som". In such cases, you can display Korean mixed script as Hanja: Korean: 김다솜; Hanja: 金다솜.

Spaces for Hanja

• MOS:HANJASPACES

While Hangul and Korean mixed script (Hangul and Hanja together) use spaces between words, text written only in Hanja is usually written without spaces. E.g. Korean: 고속화 도로; Hanja: 高速化道路; RR: gosokhwa doro; lit. freeway; the Hangul has a space while the Hanja does not.

Hanja vs. other Chinese characters

• MOS:HANJAHANZI
• MOS:HANJAKANJI

There are differences between Hanja and the Chinese characters used elsewhere in the Sinosphere that should be reflected on Misplaced Pages.

The following should not be considered Hanja:

• In some cases, Chinese-language sources transcribe Korean words into Chinese. For example, transcribing the native Korean name Da-som (다솜) as Duoshun (Chinese: 多順).
  • Furthermore, some sources (particularly those from mainland China) use simplified Chinese characters, which often do not overlap with contemporary Hanja.
• Japanese sources use kanji, another set of Chinese characters that also sometimes differs from those used in Korea. For example, the Hanja name for South Korea, 大韓民國, is rendered as 大韓民国 in Japanese.
  • However, Japan tends not to invent kanji for people when unknown; it tends to rely on phonetic spellings in katakana instead.
• South Korea has also developed its own Chinese-language transcriptions for Korean terms; for example xinqi (Chinese: 辛奇) for kimchi (originally a native Korean word without Hanja). Unless explicitly accepted as such in dictionaries, such words should also not be considered Hanja.

Due to these issues, in general, prefer Korean-language sources (especially reliable dictionaries) for determining appropriate Hanja.

Unless particularly relevant (e.g. a person is significantly linked to both China and Korea), there is generally no need to mention Chinese transcriptions for Korean terms on articles primarily about Korea, for the same reason that listing a Chinese transcription of U.S. President Jimmy Carter's name is not particularly helpful.

Also, unless particularly relevant, do not include Chinese romanizations (e.g. pinyin) applied to Hanja. For example, do not write: Kim Ku (Korean: 김구; Hanja: 金九; RR: Gim Gu; pinyin: Jīn Jiǔ).

Article layout

First sentence

• MOS:KO-FIRSTSENTENCE
• MOS:KO-LEAD

Family name footnote or hatnote

For articles about people, if the article title displays family name before given name (as is common in Korean names), you should provide either a {{Family name footnote}} or {{Family name hatnote}}, but not both. The family name footnote should be placed just after the bolded mention of the person's name, with no space in between. If the family name comes after (i.e. the Western ordering), neither templates are needed.

Whether to use a footnote or hatnote is debated; footnotes offer several benefits.

First parentheses

In the first sentence of an article primarily about Korea, if there is a notable Korean-language equivalent for the term, display it in parentheses just after the bolded mention of the article's title. This is often only Hangul, but sometimes includes Hanja, per § Hanja for main topics. Make sure the displayed text abides by § Italics and bolding for Hangul and § Spaces for Hanja. Wrap the Korean text using {{Korean}}. You can display romanization(s) in the template if they are useful and not already the article title.

If showing Korean text does not add significant understanding, or if there is no bolded mention of the title in the first sentence (which is permissible, per MOS:AVOIDBOLD), parenthetical Korean text should be omitted. For example, for Healthcare in South Korea, putting "(Korean: 대한민국의 의료)" isn't particularly useful, as the title is a generic phrase and not a name or proper noun, and because the title is in English and is sufficiently descriptive.

You can also provide the following information in the same parentheses, separated by semicolon:

• An English-language abbreviation, if the article title is in English.
  • This should generally be placed first (to emphasize its relationship with the English term) and be bolded. For example, "The National Institute of Korean Language (NIKL; Korean: 국립국어원) is a..."
• IPA representations for Korean and sometimes English (if the word falls under § English words of Korean origin).
  • Place the IPA(s) within the parentheses ideally just after their relevant terms, and wrap them in {{IPA}} (with lang=ko) for Korean and {{IPAc-en}} for English. For example, "Kimchi (/ˈkɪmtʃiː/; Korean: 김치, IPA: )". The English IPA was first, following the English word "kimchi" (§ English words of Korean origin). The Korean IPA followed the Hangul.
• Dates of birth and death, per MOS:BIOFIRSTSENTENCE. This should usually go last in the parentheses.

As parentheses can become lengthy and difficult to read, they should not include:

• Birthplace, per MOS:BIRTHPLACE
• Alternate names
  • Our goal is to keep the first sentence easy to parse at a quick glance. Too many synonyms, especially before a definition is even given, make the sentence hard to read.

If the parentheses become too crowded, consider putting less important information in one or more explanatory footnotes, preferrably variations of {{efn}} or {{NoteTag}}. We recommend you do not use normal reference tags (<ref></ref>) for explanatory footnotes. We would like to keep those reserved for citations.

Example:

'''Lee Myung-bak''' ({{IPAc-en|ˌ|l|iː|_|ˌ|m|j|ʌ|ŋ|_|ˈ|b|ɑː|k}}; {{Korean|hangul=이명박}}; {{IPA|ko|i mjʌŋbak|lang}}; born 19 December 1941)

Infobox Korean name

If the first sentence is cluttered, {{Infobox Korean name}} can be used in place of {{Korean}} or footnotes. For North Korean topics, the parameter |context=north should be set. If the article topic significantly involves other countries from the Sinosphere, consider using {{Infobox Chinese}} instead, which has parameters for Korean and other Sinosphere languages.

If there is another infobox in the article (e.g. {{Infobox person}}), we recommend you merge the name infobox into the other infobox. This is usually accomplished by adding the |child=yes parameter to the name infobox, then adding the name infobox code to a |module= (or sometimes |embedded=) parameter of the other infobox. For the parameter name, check the documentation for the main infobox (e.g. Template:Infobox person#Parameters).

Naming guidelines

Unless if stated otherwise in each subsection of § Naming conventions, assume that these principles apply to all Korea-related terms.

Strict romanization vs. naming conventions

• MOS:KO-STRICT
• MOS:KO-TEMPLATEROMAN

Do not mistake the guidelines in WP:NCKO for strict applications of romanization; some of our guidelines differ from official romanization standards.

When strictly romanized text is needed, namely within templates like {{Infobox Korean name}} and {{Korean}}, do not apply the rules of WP:NCKO. Instead, strictly apply the rules of the respective romanization systems.

For example, the spelling "Lee Ha-na" should be used everywhere (e.g. article title, in body of any article, in infobox titles) except for when templates like {{Infobox Korean name}} or {{Korean}} ask for RR or MR. Then you should provide "I Hana" ("I" instead of "Lee" or "Yi"; no hyphen).

Same terms for article titles and in the body

Per WP:CONSISTENT and MOS:CONSISTENT, generally, if a concept has an article, you should refer to that concept in the bodies of other articles using the article title verbatim. E.g. in an article primarily about North Korea, do not write "Sŏul" (McCune–Reischauer), write "Seoul".

Translating non-people names to English

• MOS:KO-TRANSLATENAME

Per WP:TRANSLITERATE, when there are non-people names (e.g. organization names, titles of works, objects, etc.) that have an established English-language name, that name is used. For example: N Yukjo → Y Six Ministries of Joseon.

When there aren't enough sources to constitute an established English name, as a last resort you may translate the names to English if there is no loss in accuracy. If you are not sure of or satisfied with the quality of your translation, do not translate; romanize per § Romanization and other relevant guidelines in the naming conventions section. If you do translate the term, you must also record the original Korean name somewhere. If an invented translated name is the main topic of an article, create redirects for the romanizations and conceivable alternate translations per WP:RPURPOSE.

Ideally, our terminology should be unified within and across articles, meaningful to non-Korean speakers, and traceable to the original Korean for verification. Inventing English names can aid understanding, but missing any of the steps in this guidance can work against our goals.

Create alternate title redirects

Per WP:RPURPOSE, create redirects for conceivable alternate romanizations, translations, and spellings.

Naming conventions

People names

In order to determine the Latin spelling of a Korean person's name, follow these steps in order and stop when you reach a step that adequately gives a spelling for your situation.

1. Use common name

Per WP:COMMONNAME, use whichever spelling and name for the person is widely used in English-language sources. This may be a name in some other language and not their Korean name. If there is no clear consensus on spelling in the sources, consider moving onto step 2.

2. Follow personal preference

If the person's preferred English name or Latin spelling is known, use that.

3. Romanize

Following the table below, romanize the person's name depending on when and where they are primarily notable. If significantly notable in multiple categories below, prioritize recency.

Royalty

Generally, if there is no established common name for a monarch, their article titles should use the format "Name of Kingdom". For example: Taejo of Joseon and Gojong of Korea. There are currently some exceptions to this pattern, due to either common name (e.g. Sejong the Great) or disambiguation (Queen Seondeok of Silla and King Seondeok of Silla).

Article titles on princes should follow the "(Grand) Prince title" format. For example: Grand Prince Yeongchang and Prince Yangpyeong. Common names can also be an exception to this rule, such as Yeonsangun of Joseon.

Appropriate infobox templates should be used.

Administrative divisions

Provinces

Use the following spellings for both article titles and in the body of any article (you can truncate the disambiguation for Gangwon/Kangwon Province).

Note that many of these provinces have official English names that differ from these spellings; see Provinces of South Korea for examples. These titles represent the status quo, and are possibly due to a mix of WP:COMMONNAME, WP:USEENGLISH, and WP:TITLECON.

North Korean

• Chagang Province
• North Hamgyong Province
• South Hamgyong Province
• North Hwanghae Province
• South Hwanghae Province
• Kangwon Province, North Korea
• North Pyongan Province
• South Pyongan Province
• Ryanggang Province

South Korean

• North Chungcheong Province
• South Chungcheong Province
• Gangwon Province, South Korea
• Gyeonggi Province
• North Gyeongsang Province
• South Gyeongsang Province
• North Jeolla Province
• South Jeolla Province
• Jeju Province

Cities

Use the Misplaced Pages:COMMONNAME for the city, without "-si" (시) nor English-language terms such as "Metropolitan City" or "Special Self-Governing City".

An exception to the above is for disambiguating Sejong City vs. the person Sejong the Great. Most other disambiguations can be handled by adding a comma and upper-level administrative division, e.g. Anyang, Gyeonggi (vs. Anyang in China).

For pre-modern cities that still exist and go by the same name, use the modern spelling. E.g. use "Gyeongju" for the city during the Joseon period. For pre-modern cities that no longer exist, follow § Romanization.

Counties

Romanize per § Romanization, replace "-gun" and "-kun" with "County", e.g. Jindo County.

Districts

Romanize per § Romanization. Replace "-gu", "-ku", and "-chigu" with "District". Keep "-guyok" for North Korean locations.

Towns, neighborhoods, and villages

Romanize per § Romanization. Unless there is a clear WP:COMMONNAME, keep "-myeon", "-dong", and "-ri" and do not translate them. "-eup" is optional.

Visual guide

Below is a visual guide for administrative divisions in both North and South Korea, with examples of how to handle each level.

Geographic features

Mountains and hills

Unless there is a clear WP:COMMONNAME, romanize the full Korean name using § Romanization. Then apply the following:

• For names with the terms "san" (산) or "bong" (봉), use their full unhyphenated Korean names. E.g. Seoraksan and Moranbong.
• For names with "oreum" (오름), split the name. E.g. Yongnuni Oreum and not Yongnunioreum.
  • Splitting appears to be the general common name convention for oreum. Splitting also results in fewer spelling ambiguities and more segmented names that are easier to quickly parse.

For disambiguation, put the administrative district(s) the mountain is located in parentheses, e.g. Maehwasan (Gangwon). If the mountain is located in multiple districts, format them like so: Maebongsan (Wonju and Yeongwol) or Gayasan (North and South Gyeongsang). We disambiguate like this by default because Korea has very few distinct mountain ranges, so disambiguating by mountain range often does not work.

Rivers

Unless there is a clear WP:COMMONNAME, romanize the full Korean name using § Romanization. Then replace "gang"/"kang" with "River". For example, Nakdong River and Taedong River.

Islands

Unless there is a clear WP:COMMONNAME, romanize the full Korean name using § Romanization. Keep and do not hyphenate "do" or "seom", e.g. Baengnyeongdo and Ryŏdo.

Controversial place names

• MOS:KO-CPN
• MOS:SoJ
• MOS:SEAOFJAPAN
• MOS:EASTSEA
• MOS:LIANCOURT
• MOS:DOKDO
• MOS:TAKESHIMA

For places with disputed English names, namely the Sea of Japan/East Sea and the Liancourt Rocks/Dokdo/Takeshima, use whichever terms match the respective current article title. In most cases, there is no need to mention the alternate name(s). Do not use a WP:PIPELINK. Generally, alternate names should only be mentioned if the naming dispute is relevant to the article itself.

As of August 2024:

N The ] is between Japan and Korea.

N The ] is between Japan and Korea.

N The ] (East Sea) is between Japan and Korea.

N The ], or East Sea, is between Japan and Korea.

Y The ] is between Japan and Korea.

Y (in an article about Japan–Korea disputes) There is currently a naming dispute over whether the ] should be called the "East Sea".

This guideline is not an expression of preference for any particular name; it is simply following Misplaced Pages policy.

These titles have changed in the past, and may change again. If you have a strong understanding of the previous move proposals and Misplaced Pages's policies, and you think you have a good case to propose renaming such contested articles, you are welcome to do so. Do not make move requests lightly; poorly reasoned move requests will likely be WP:SNOWCLOSED.

Temples

Unless there is a clear WP:COMMONNAME, romanize the full Korean name using § Romanization. E.g. Bulguksa and not "Bulguk Temple".

Works

If there is no clear WP:COMMONNAME or WP:ENGLISHTITLE, romanize the full Korean name using § Romanization.

If the title of the work did not have spaces in it (e.g. if it was in Hanja, which does not have spaces), you may optionally consider inserting them into the romanized title. Try to follow common spacing conventions: use spaces to separate ideas or phrases and avoid inserting them indiscriminately between every character.

Titles of works that have been romanized should be presented in italicized sentence case. This generally means just capitalizing the first word and any proper nouns.

YKing Sejong wrote Worin cheongang jigok.

NKing Sejong wrote Worin Cheongang Jigok.

Alternatively, the romanization can be presented with a parenthetical gloss with the original Hangul and/or Hanja, if relevant. If an English translation is provided (as opposed to a romanization) it should also be italicized but using title case:

YKing Sejong wrote a poem called Songs of the Moon Shining on a Thousand Rivers (월인천강지곡; 月印千江之曲; Worin cheongang jigok).

NKing Sejong wrote a poem called Songs of the Moon Shining on a Thousand Rivers (월인천강지곡; 月印千江之曲; Worin Cheongang Jigok).

Dates and numbers

• MOS:KO-DATE
• MOS:KO-NUMBER

Date format

We recommend the use of the month-day-year (March 1, 1919) date format in prose; this format seems to be widely used by both Koreas in English-language publications. The day–month–year (1 March 1919) format is permissible if the article has strong national ties with another English-speaking country that uses that format. Year–month–day (1919-03-01) can be used in tables, infoboxes, and references—if brevity is helpful—but should otherwise be avoided. The date format used in an article should be consistent and should not be changed without consensus.

Calendars

• MOS:KO-CALENDAR

Prior to the 20th century, Korea used a lunisolar calendar: the Korean calendar. Per MOS:OSNS, while you're allowed to reference dates using this calendar, you must also provide an equivalent Julian calendar date for dates before October 15, 1582 or a Gregorian calendar date for dates on and after October 15, 1582. We encourage, for consistency with most of the rest of Misplaced Pages, that dates in the Julian or the Gregorian calendar be the primary dates given, with Korean calendar dates optionally given as side notes. If you do use the Korean calendar, you must clearly indicate which dates use which calendar.

Units of measurement

• MOS:KO-UNIT
• MOS:PYEONG

Per MOS:UNIT, prefer the use of SI units. If other Korea-related units are used in your sources, such as the li (ri) or pyeong, it is permissible but less preferred to use such units on Misplaced Pages. If you do use such units, you should link to relevant articles about the units and then provide conversions of them to SI units. Currently, {{Convert}} supports conversion from pyeong to other SI units for area.

Number ranges

• MOS:KO-TILDE

To express ranges between numbers, use an en dash (1950–1953 Korean War). Do not use tildes (1950~1953 Korean War), as is done in South Korea.

Links

No direct links to the Korean Misplaced Pages

• MOS:KO-WIKILINK

Per MOS:INTERWIKI, do not directly link to the Korean Misplaced Pages in articles. If the topic doesn't have an article on the English Misplaced Pages, use {{Interlanguage link}}s instead.

Y{{Interlanguage link|Hyeon Sun|ko|현순}} → Hyeon Sun 

N] → Hyeon Sun (misleading blue link; gives impression English Misplaced Pages has article)

If the topic already has an article on the English Misplaced Pages, do not link to the Korean Misplaced Pages version at all. If you think the Korean version has information that would be useful on the English version, put the {{Expand Korean}} banner at the top of the article being linked.

Wiktionary links

• MOS:KO-WIKT

It is possible to link to the Wiktionary definitions of Korean words and phrases. This typically involves the use of {{linktext}} or an external wikilink, e.g. ].

Use Wiktionary links for Korean text sparingly. They should generally only be used in the following circumstances:

• If the link offers significant understanding of the main topic of the article that cannot be easily communicated within the article
• Linguistic contexts (e.g. when the topic is about lexical items)

Do not do the following:

• Link each character without regard for where word divisions actually are.
  • E.g. {{linktext|기|다|리|다}} → 기다리다. The individual definitions of the characters cannot be used to tell you what the overall word means.
• Segment text incorrectly.
  • E.g. {{linktext|대학|생선|교회}} is incorrect; {{linktext|대학생|선교회}} is correct.
• Add Wiktionary links to
  • personal names (including art names, stage names, etc.). The meaning of a name does not describe a person, and the definition of a personal name is usually nothing more than "a personal name".
  • terms that are not suitable for dictionary entries (e.g. 새터데이 – merely a transcription of English "Saturday" and is not used as a word in Korean).

Two or more links in a row are discouraged per WP:SEAOFBLUE.

Referencing Korean-language sources

For Korean-language sources, the following practices are encouraged:

• if you're using some variant of {{Citation}}, providing the original Hangul title in the script-title parameter (not the title parameter) with ko: just before the title
• providing a translated title of the work, e.g. in the trans-title parameter
• preferring the use of English for parameters if unambiguous (e.g. for place names or publishers with known English names, use the English names). If you translate or romanize text yourself, provide the original Korean text in the reference.
• not squeezing the entire Hangul name into the last parameter. If you'd like to avoid the comma appearing in the name, consider using the author-mask parameter as well.

{{cite book |last = 이 |first = 성주 |author-mask = 이성주 |script-title = ko:청동기·철기 시대 사회 변동론 |trans-title = Social Transformation from the Bronze to Iron Ages |publisher = 학연문화사 |year = 2007 |location = Seoul}}

See also

• Category:Korean multilingual support templates

Notes

1. Make sure to use the breve (ŏ ŭ Ŏ Ŭ), not the caron (ǒ ǔ Ǒ Ǔ).
2. Doing either of these practices is like writing "colo(u)r" or "color (colour)"; these clarifications rarely add significant understanding and just add clutter.
3. E.g. for 독립 it produces doglib instead of our preferred dongnip. Consider using this website instead.
4. You can alternatively use {{Lang-ko}}, but this is less preferred. It does not have separate parameters for Hangul and Hanja, and for RR and MR.
5. Using just ko is sufficient for rendering Korean text appropriately, and there are nuances and exceptions to the subvariants. Hani only should be applied when there's purely Hanja. If anything in the Hanja parameter is not Hanja, including Hangul (§ Partial Hanja) or Latin text, the parameter is inappropriate. Hant is for the Chinese language written in traditional characters (as opposed to Hans for simplified characters), not for Korean. In some environments, ko-Hani displays the text as simplified Chinese and ko-Hant as traditional Chinese, not as Korean.
6. We recommend this because of cases like the "Chairman Un Incident".
7. It is optional but recommended to have language labels displayed for the first usage of {{Korean}}. Follow § Formatting Hangul for how to manage subsequent labels.
8. E.g. if an article is about a person whose common name has an unusual romanization, like "Syngman Rhee (Korean: 이승만; RR: I Seungman; 26 March 1875 – 19 July 1965)...".
9. Make sure to abide by MOS:ABBR, particularly MOS:SOURCEABBR.
10. One place you can put one alternate name is outside of and after the first set of parentheses, for example "Gimbap (Korean: 김밥), also spelled kimbap, ...". If there are more than one alternate names, place them elsewhere in the lead.
11. If inline, in parentheses or in a footnote. If the main article topic, in the {{Infobox Korean name}} and in the lead first parentheses.
12. No hyphen if more or less than two characters.

References

1. "kimchi meaning". OneLook. Retrieved 2024-09-01.
2. "chaebol". OneLook. Retrieved 2024-09-01.

• Misplaced Pages draft proposals