View source for CJK Compatibility

{{distinguish|CJK Compatibility Forms|CJK Compatibility Ideographs}}
{{for|a list of all CJK characters encoded in Unicode|CJK Unified Ideographs}}
{{Infobox Unicode block
|rangestart = 3300
|rangeend   = 33FF
|script1 = {{nowrap|Katakana (88 char.)}}
|script2 = {{nowrap|[[Script (Unicode)#Special script property values|Common]] (168 char.)}}
|1_0_0      = 187
|1_1        = 62
|4_0        = 7
|note = <ref>{{Cite web|url=https://www.unicode.org/ucd/|title=Unicode character database|work=The Unicode Standard|accessdate=2023-07-26}}</ref><ref>{{Cite web|url=https://www.unicode.org/versions/enumeratedversions.html|title=Enumerated Versions of The Unicode Standard|work=The Unicode Standard|accessdate=2023-07-26}}</ref>
}}

[[File:UCB_CJK_Compatibility.png|thumb|Graphical representation of the CJK Compatibility Unicode block]]
'''CJK Compatibility''' is a [[Unicode block]] containing square symbols (both CJK and Latin alphanumeric) encoded for compatibility with East Asian character sets. In Unicode 1.0, it was divided into two blocks, named '''CJK Squared Words''' (U+3300–U+337F) and '''CJK Squared Abbreviations''' (U+3380–U+33FF).<ref>{{cite web |url=https://www.unicode.org/versions/Unicode1.0.0/CodeCharts2.pdf |work=The Unicode Standard |version=version 1.0 |title=3.8: Block-by-Block Charts |publisher=[[Organization:Unicode Consortium|Unicode Consortium]]}}</ref>
The square forms can have different presentations when they are used in horizontal or vertical text. 
For example, the characters {{unichar|333E}} (from {{lang|ja|ボルト}}) and {{unichar|3327}} (from {{lang|ja|トン}}) should look different in horizontal and in vertical right-to-left:<ref name="UAX50">{{cite web |last1=Lunde |first1=Ken |last2=Ishi |first2=Koji |title=UAX #50: Unicode Vertical Text Layout |url=https://www.unicode.org/reports/tr50/ |website=www.unicode.org |access-date=13 June 2024 |language=en |date=2023-07-17}}</ref> {{Vertical text|style=writing-mode: vertical-rl; |㌧㌾}}

Characters U+337B through U+337E are the [[History:Japanese era name|Japanese era calendar scheme]] symbols Heisei (㍻), Shōwa (㍼), Taishō (㍽) and Meiji (㍾) (also available in certain legacy sets, such as the "[[JIS X 0208#0x2D|NEC special characters]]" extension for [[JIS X 0208]], as included in [[Code page 932 (Microsoft Windows)|Microsoft's version]] and later JIS X 0213).<ref name="lundenec13">{{cite web |url=https://blogs.adobe.com/CCJKType/2019/03/era-name-ligature-history.html |title=A Brief History of Japan's Era Name Ligatures |last=Lunde |first=Ken |work=CJK Type Blog |date=2019-03-21 |publisher=Adobe Inc}}</ref> The Reiwa era symbol ({{unichar|32FF}}) is in [[Enclosed CJK Letters and Months]] (the CJK Compatibility block having been fully allocated by the time of its commencement).

==Block==
{{Unicode chart CJK Compatibility}}

==History==
The following Unicode-related documents record the purpose and process of defining specific characters in the CJK Compatibility block:

{{sticky header}}
{| class="wikitable sticky-header"
|-
! [[Unicode#Versions|Version]] !! {{nobr|Final code points<ref group=lower-alpha name=final/>}} !! Count !! [[Organization:International Committee for Information Technology Standards|L2]]&nbsp;ID !! WG2&nbsp;ID !! Document
|-
| rowspan="3" | 1.0.0 || rowspan="3" | U+3300..3357, 337B..33DD || rowspan="3" | 187 || || || (to be determined)
|-
| || [https://www.unicode.org/wg2/docs/n2956.doc N2956] || {{Citation|title=Unicode Consortium Liaison Report for WG2 Meeting #47|date=2005-08-12|first=Asmus|last=Freytag|section=Representative Glyph for U+33AC SQUARE GPA}}
|-
| || {{nobr|[https://www.unicode.org/wg2/docs/n2953.pdf N2953 (pdf],}} [https://www.unicode.org/wg2/docs/n2953.doc doc]) || {{Citation|title=Unconfirmed minutes of WG 2 meeting 47, Sophia Antipolis, France; 2005-09-12/15|date=2006-02-16|first=V. S.|last=Umamaheswaran|section=M47.16 (Miscellaneous glyph defects)}}
|-
| 1.1 || U+3358..3376, 33E0..33FE || 62 || || || (to be determined)
|-
| rowspan="15" | 4.0 || rowspan="15" | U+3377..337A, 33DE..33DF, 33FF || rowspan="15" | 7 || {{nobr|[https://www.unicode.org/L2/L1999/99353-n2056.pdf L2/99-353]}} || [https://www.unicode.org/wg2/docs/n2056.pdf N2056] || {{Citation|title=Amendment of the part concerning the Korean characters in ISO/IEC 10646-1:1998 amendment 5|date=1999-07-29|section=3}}
|-
| {{nobr|[https://www.unicode.org/L2/L1999/99380.htm L2/99-380]}} || || {{Citation|title=Proposal for a New Work item (NP) to amend the Korean part in ISO/IEC 10646-1:1993|date=1999-12-07}}
|-
| {{nobr|[https://www.unicode.org/L2/L1999/J1n599903.pdf L2/99-380.3]}} || || {{Citation|title=Annex B, Special characters compatible with KPS 9566-97 (To be extended)|date=1999-12-07}}
|-
| {{nobr|[https://www.unicode.org/L2/L2000/00084-n2182.pdf L2/00-084]}} || [https://www.unicode.org/wg2/docs/n2182.pdf N2182] || {{Citation|title=Amendment of the part concerning the Korean characters in ISO/IEC 10646-1:1998 amendment 5 (Cover page and outline of proposal L2/99-380)|date=1999-12-07|section=3}}
|-
| {{nobr|[https://www.unicode.org/L2/L1999/99382-korea.htm L2/99-382]}} || || {{Citation|title=Comments to accompany a U.S. NO vote on JTC1 N5999, SC2 N3393, New Work item proposal (NP) for an amendment of the Korean part of ISO/IEC 10646-1:1993|date=1999-12-09|first=Ken|last=Whistler|section=2.3}}
|-
| {{nobr|[https://www.unicode.org/L2/L2000/00066-n2170.pdf L2/00-066]}} || {{nobr|[https://www.unicode.org/wg2/docs/n2170-scan.pdf N2170 (pdf],}} [https://www.unicode.org/wg2/docs/n2170.doc doc]) || {{Citation|title=The technical justification of the proposal to amend the Korean character part of ISO/IEC 10646-1 (proposed addition of 79 symbolic characters)|date=2000-02-10|section=3}}
|-
| {{nobr|[https://www.unicode.org/L2/L2000/00073-n2167.pdf L2/00-073]}} || [https://www.unicode.org/wg2/docs/n2167.doc N2167] || {{Citation|title=Comments on DPRK New Work Item proposal on Korean characters|date=2000-03-02|first=Kent|last=Karlsson}}
|-
| {{nobr|[https://www.unicode.org/L2/L2000/00285-n2244.pdf L2/00-285]}} || [https://www.unicode.org/wg2/docs/n2244.pdf N2244] || {{Citation|title=Proposal for the Addition of 82 Symbols to ISO/IEC 10646-1:2000|date=2000-08-10}}
|-
|-
| || [https://www.unicode.org/wg2/docs/n2282.doc N2282] || {{Citation|title=Report of the meeting of the Korean script ad hoc group|date=2000-09-21}}
|-
| {{nobr|[https://www.unicode.org/L2/L2001/01349-N2374-DPRK-AddSymbols.pdf L2/01-349]}} || [https://www.unicode.org/wg2/docs/n2374r.pdf N2374R] || {{Citation|title=Proposal to add of 70 symbols to ISO/IEC 10646-1:2000|date=2001-09-03}}
|-
| {{nobr|[https://www.unicode.org/L2/L2001/01387-n2390.pdf L2/01-387]}} || [https://www.unicode.org/wg2/docs/n2390.pdf N2390] || {{Citation|title=ROK's Comments about DPRK's proposal, WG2 N 2374, to add 70 symbols to ISO/IEC 10646-1:2000|date=2001-10-13|first=Kyongsok|last=Kim}}
|-
| {{nobr|[https://www.unicode.org/L2/L2001/01388-n2392.pdf L2/01-388]}} || [https://www.unicode.org/wg2/docs/n2392.pdf N2392] || {{Citation|title=A Report of Korean Script ad hoc group meeting on Oct. 15, 2001|date=2001-10-16|first=Kyongsok|last=Kim}}
|-
| {{nobr|[https://www.unicode.org/L2/L2001/01420-consent-docket.txt L2/01-420]}} || || {{Citation|title=WG2 (Singapore) Resolution Consent Docket for UTC|date=2001-10-30|first=Ken|last=Whistler|section=f. Miscellaneous symbol additions from DPRK standard}}
|-
| {{nobr|[https://www.unicode.org/L2/L2001/01458-n2407-KoreanMapReq.pdf L2/01-458]}} || [https://www.unicode.org/wg2/docs/n2407.doc N2407] || {{Citation|title=Request to Korean ad hoc group to generate mapping tables between ROK and DPRK national standards|date=2001-11-16|first=V. S.|last=Umamaheswaran}}
|- class="sortbottom"
| colspan="6" | {{reflist|group=lower-alpha|refs=<ref name=final>Proposed code points and characters names may differ from final code points and names</ref>}}
|}

== See also ==
*[[Unicode compatibility characters]]
*[[CJK Unified Ideographs]]
*[[Katakana (Unicode block)]]
*[[Letterlike Symbols]]

== References ==
{{reflist}}
{{CJK ideographs in Unicode}}

[[Category:Unicode blocks]]

{{Sourceattribution|CJK Compatibility}}