Hangul Jungseong Filler (U+1160)

The Hangul Jungseong Filler is a blank Korean jamo that stands in for a missing vowel. NFKC turns the Hangul Filler into it.

Updated By Milind Sahu How we test

Copy tool
U+1160, 3 bytes

U+1160Lo · letterhas width

Need the code?HTML, CSS, JS escapesFind it in text

How we test

An app result is shown only after a hand test on a named app version, with the date. Results older than 120 days are hidden until re-tested.

Read the method →

What is the Hangul Jungseong Filler used for?

The Hangul Jungseong Filler (U+1160) is used in Korean text to stand in for a missing vowel, so the syllable stays well formed. It is also what NFKC normalization turns the Hangul Filler into, which makes it the blank that normalized text stores. It draws nothing and is not whitespace.

Jungseong means the vowel of a Korean syllable. The Unicode Standard says the jungseong filler stands in for a missing jungseong to make a well-formed syllable. It is in the Hangul Jamo block, from Unicode 1.1.

The Unicode data lists it as the compatibility decomposition of U+3164. So when text is normalized with NFKC, every Hangul Filler becomes this character, and this is the form normalized text stores.

It is a letter (Lo), Alphabetic and Default Ignorable, and it is not whitespace. Line breaking treats it as a vowel jamo (class JV), and no break is allowed between a leading jamo and it.

Its East Asian Width is Neutral, while the Hangul Filler's is Wide. East Asian and fixed-width layouts use that property to decide how much room a character gets.

Watch out for

  • Right after a leading jamo it becomes part of that syllable, so don't place it directly after Korean letters.
  • It is a different code point from U+3164, so it is worth trying where the Hangul Filler fails. This site has no tested app results for it yet.
  • In UTF-8 it takes 3 bytes (E1 85 A0).

Sources: Unicode Standard 3.12: Conjoining Jamo Behavior · Unicode normalization (UAX #15) · Unicode character data (UnicodeData.txt) · Unicode derived properties (DerivedCoreProperties.txt) · Unicode properties (PropList.txt) · Unicode blocks (Blocks.txt) · Unicode version each character arrived (DerivedAge.txt) · Unicode line breaking (UAX #14) · East Asian Width (UAX #11) · Computed from the character itself (see Codes and escapes)

Codes and escapes

FormatValueCopy
HTML entity ᅠ · ᅠ
CSS \1160
JavaScript / Java \u1160
Python \u1160
URL-encoded %E1%85%A0
UTF-8 bytes E1 85 A0

Properties

Unicode category
Lo (Letter, other)
Treated as whitespace
No
Width
Takes up space
Unicode name
HANGUL JUNGSEONG FILLER

Where it works

Not tested yet. Results appear here with the app version and date once each app is tested by hand.

Similar characters

Back to all 13 invisible characters

FAQ

How do I type the Hangul Jungseong Filler?

To type the Hangul Jungseong Filler, copy it from the tool above, since keyboards have no key for it. In JavaScript it is \u1160, and in HTML ᅠ. Keep it away from Korean letters: right after a leading jamo, it becomes part of that syllable instead of a separate blank.

Why does my Hangul Filler turn into U+1160?

Your Hangul Filler turns into U+1160 when the text goes through NFKC normalization. The Unicode data lists the Hangul Jungseong Filler as the compatibility form of U+3164, so NFKC swaps one for the other. It stays a blank letter, so the result still looks empty and still isn't whitespace.

How do I remove the Hangul Jungseong Filler from text?

To remove the Hangul Jungseong Filler, paste the text into the detector and delete every U+1160 it marks, or use text.replace(/\u1160/g, '') in JavaScript. If you also want Hangul Fillers gone, remove U+3164 as well, because normalized and unnormalized text can hold either one.