![[Unicode]](https://www.unicode.org/webscripts/logo60s2.gif){kind=small}
Technical Reports| Technical Reports |
| Version | Unicode 15.0.0 |
| Editors |
Ken Lunde 小林劍󠄁 Koji Ishii 石井宏治 |
| Date | 2022-05-09 |
| This Version | https://www.unicode.org/reports/tr50/tr50-27.html |
| Previous Version | https://www.unicode.org/reports/tr50/tr50-26.html |
| Latest Version | https://www.unicode.org/reports/tr50/ |
| Latest Proposed Update | https://www.unicode.org/reports/tr50/proposed.html |
| Revision | 27 |
The Unicode code charts generally show characters oriented for horizontal presentation. However, some of the glyphs are actually oriented for vertical presentation. A few characters change shape or orientation when the text is rotated from horizontal to vertical.
When text is presented, there are various conventions for the orientation of the characters with respect to the line. In most cases, characters are oriented in an upright manner similar to their presentation in the Unicode code charts. In a few cases, when presented in vertical lines, the characters will appear rotated or transformed in various ways. For example, in East Asia, Han ideographs, Kana syllables, Hangul syllables, and Latin letters in acronyms are upright, while words and sentences in the Latin script are typically sideways. This report describes a Unicode character property which can serve as a stable default orientation of characters for reliable document interchange.
This is a draft document which may be updated, replaced, or superseded by other documents at any time. Publication does not imply endorsement by the Unicode Consortium. This is not a stable document; it is inappropriate to cite this document as other than a work in progress.
A Unicode Standard Annex (UAX) forms an integral part of the Unicode Standard, but is published online as a separate document. The Unicode Standard may require conformance to normative content in a Unicode Standard Annex, if so specified in the Conformance chapter of that version of the Unicode Standard. The version number of a UAX document corresponds to the version of the Unicode Standard of which it forms a part.
Please submit corrigenda and other comments with the online reporting form [Feedback]. Related information that is useful in understanding this annex is found in Unicode Standard Annex #41, “Common References for Unicode Standard Annexes.” For the latest version of the Unicode Standard, see [Unicode]. For a list of current Unicode Technical Reports, see [Reports]. For more information about versions of the Unicode Standard, see [Versions]. For any errata which may apply to this annex, see [Errata].
When text is displayed in vertical lines, there are various conventions for the orientation of the characters with respect to the line. In East Asia, Han ideographs, Kana syllables, and Hangul syllables, along with Latin letters of acronyms, remain upright, meaning that they appear with the same orientation as in the code charts, but words and sentences that are composed of characters of the Latin script are typically oriented sideways, as can be seen in Figure 1.
Figure 1. Japanese Vertical Text
In many parts of the world, most characters are upright, as can be seen in Figure 2.
Figure 2. Western Vertical Text
Most languages and scripts are written horizontally and vertical presentation is a special case, usually used for short runs of text (as in Figure 2). Some languages, however, have publishing traditions that provide for long-format vertical text presentation, notably East Asian languages such as Japanese. In those languages, the orientation in which characters are laid out can vary, depending on the scripts, the style, and sometimes the context. The preferred or desired orientation may also change over time.
While the choice of orientation for a character can vary across documents, it is important that the choice made by an author for a specific document be clearly established, so that a rendering system can display what the author intended. It is also important that this choice be established independently of the font resources, as the rendering systems may have to use other fonts than those intended or specified in the document. Finally, the expression of the author’s choice should be relatively concise, to facilitate document authoring and minimize document size.
This report describes a Unicode character property which can serve as a stable default character orientation for the purpose of reliable document interchange.
For the purpose of reliable document interchange, this property defines an unambiguous default value, so that implementations could reliably render a character stream based solely on the property values, without depending on other information such as provided in the tables of the selected font.
The intent is that document formats should offer to the author the possibility of specifying the desired orientation of a given character (either all occurrences or a particular occurrence), and that in the absence of an explicit specification, the orientation is implicitly that defined by the property presented in this report.
In plain text, which by definition does not allow the recording of any data beyond the characters, the orientations are by necessity those specified by the property.
The actual choice for the property values should result in a reasonable or legible default, but it may not be publishing-material quality, and it may not be a good choice if used in a specific style or context.
The property values are chosen first to match existing practice in Japanese context in Japan and then in other East Asian contexts in their respective environments. For characters that are not generally used in such environments, similarity to existing characters has been taken into consideration. Commonly used characters of Latin and other scripts that appear in Japanese and other East Asian environments are also taken into account, but with the lower priority.
The property defined in this report is informative. The intent of this report is to provide, in the absence of other information, a reasonable way to determine the correct orientation of characters, but this behavior can be overridden by a higher-level protocol, such as through markup or by the preferences of a layout application. This default determination is defined in the accompanying data file [Data50], but in no way implies that the character is used only in that orientation.
For more information on the conformance implications, see [Unicode], Section 3.5, Properties, in particular the definition (D35) of an informative property.
The possible property values are given in Table 1.
Table 1. Property Values
| U | Characters which are displayed upright, with the same orientation that appears in the code charts. |
| R | Characters which are displayed sideways, rotated 90 degrees clockwise compared to the code charts. |
| Tu | Characters which are not just upright or sideways, but generally require a different glyph than in the code charts when used in vertical texts. In addition, as a fallback, the character can be displayed with the code chart glyph upright. |
| Tr | Same as Tu except that, as a fallback, the character can be displayed with the code chart glyph rotated 90 degrees clockwise. |
Note that the orientation is described with respect to the appearance in the code charts.
As in all matters of typography, the interesting unit of text is not the character, but a grapheme cluster: it does not make sense to use a base character upright and a combining mark attached to it sideways. Implementations should apply the orientation to each grapheme cluster.
A possible choice for the notion of grapheme cluster is either that of legacy grapheme cluster or that of extended grapheme cluster, as defined in [UAX29].
The orientation for a grapheme cluster as a whole is then determined by taking the orientation of the first character in the cluster, with the following exception:
If the cluster contains an enclosing combining mark (general category Me), then the whole cluster has the Vertical_Orientation property value U.
There are special typographic conventions to consider, for Japanese text layout in particular. It is common practice to represent particular katakana words and ideographic sequences as a single precomposed glyph whose components are arranged within the confines of the em-box, and are therefore the same size as a conventional ideograph. Such characters are referred to as a squared word. Furthermore, the arrangement of the components in the em-box differs depending on whether the layout is horizontal or vertical.
There are a significant number of such compatibility characters encoded in the Unicode Standard that were inherited from legacy Japanese character encoding standards. As a result of the required layout rules, these characters must be supported in East Asian fonts using separate glyphs for horizontal and vertical layout. Accordingly, one of the primary motivations for the Vertical_Orientation property value Tu is to identify the compatibility characters that exhibit such behavior.The same layout rules apply in cases where a katakana word or ideographic sequence is displayed as a squared word, but no single, encoded compatibility character exists for that sequence in the Unicode Standard. For example, 有限会社 (yūgen gaisha “limited liability company”) and 財団法人 (zaidan hōjin “foundation”) are commonly displayed the same way in text as U+337F ㍿ SQUARE CORPORATION whose horizontal and vertical glyphs are shown in Table 2.
The individual katakana characters or CJK unified ideographs that comprise these squared words are assigned the Vertical_Orientation property value U, Tu, or Tr, and therefore remain upright in vertical layout or have their own vertical form. For example, U+3312 ㌒ SQUARE KYURII, whose horizontal and vertical glyphs are shown in Table 2, is composed of U+30AD キ KATAKANA LETTER KI, U+30E5 ュ KATAKANA LETTER SMALL YU, U+30EA リ KATAKANA LETTER RI, and U+30FC ー KATAKANA-HIRAGANA PROLONGED SOUND MARK. U+30AD and U+30EA are assigned the Vertical_Orientation property value U, U+30E5 is assigned Tu, and U+30FC is assigned Tr.
This property has a current limitation in that the handling of right-to-left scripts is not specified. This includes scripts that are predominantly written right to left, such as Arabic, along with right-to-left scripts that are meant to be written vertically, such as Chorasmian.
The Unicode code charts generally show characters in the orientation they take when used in horizontal lines. However, prior to Unicode 7.0, there were a few exceptions, mostly for characters or scripts which are normally written in vertical lines; in those cases, the code charts used to show the characters in the same orientation as in vertical lines. Furthermore, such characters are often rotated when displayed in horizontal lines; Figure 3 shows an example of Mongolian text in horizontal lines in which the Mongolian characters are rotated 90 degrees counterclockwise with respect to the code charts prior to Unicode 7.0.
Figure 3. Mongolian Text on Horizontal Lines
The Unicode 7.0 code charts changed the orientation of characters for Mongolian and Phags-pa by rotating counterclockwise so that they match the orientation in horizontal lines. This change makes the code charts more consistent with other scripts in terms of the orientation of characters. It also aligns the code charts with many recent rendering systems such as OpenType, and therefore it is expected to make implementations of the property easier. However, implementations should be aware that underlying rendering systems may not have exactly the same orientation of characters as the code charts.
While this property defines only default orientations compared to the code charts, high-level protocols or applications could combine information provided in a font’s tables with the property values to more reliably calculate in which orientation they should render such glyphs, in order to achieve the desired visual result.
Table 2 provides representative glyphs for the horizontal and vertical appearance of characters with the Vertical_Orientation property values Tu and Tr.
The vertical glyphs that are shown in the table are exemplary, and their presence does not imply that font implementations should necessarily support them. Font developers should instead research the vertical glyph conventions for the intended regions to determine whether a vertical glyph is necessary for a particular character, and what the appropriate vertical glyph should be.
The Horizontal column may also specify more than one glyph when regional or other differences exist. Font developers should adhere to regional conventions when determining the appearance of horizontal glyphs.
Table 2. Glyph Changes for Vertical Orientation
| Character | Horizontal | Vertical |
|---|---|---|
| U+2329 LEFT-POINTING ANGLE BRACKET |  |
 |
| U+232A RIGHT-POINTING ANGLE BRACKET |  |
 |
| U+3001 IDEOGRAPHIC COMMA |  |
  |
| U+3002 IDEOGRAPHIC FULL STOP |  |
  |
| U+3008 LEFT ANGLE BRACKET | |
|
| U+3009 RIGHT ANGLE BRACKET | |
|
| U+300A LEFT DOUBLE ANGLE BRACKET |  |
 |
| U+300B RIGHT DOUBLE ANGLE BRACKET |  |
 |
| U+300C LEFT CORNER BRACKET |  |
 |
| U+300D RIGHT CORNER BRACKET |  |
 |
| U+300E LEFT WHITE CORNER BRACKET |  |
 |
| U+300F RIGHT WHITE CORNER BRACKET |  |
 |
| U+3010 LEFT BLACK LENTICULAR BRACKET |  |
 |
| U+3011 RIGHT BLACK LENTICULAR BRACKET |  |
 |
| U+3014 LEFT TORTOISE SHELL BRACKET |  |
 |
| U+3015 RIGHT TORTOISE SHELL BRACKET |  |
 |
| U+3016 LEFT WHITE LENTICULAR BRACKET |  |
 |
| U+3017 RIGHT WHITE LENTICULAR BRACKET |  |
 |
| U+3018 LEFT WHITE TORTOISE SHELL BRACKET |  |
 |
| U+3019 RIGHT WHITE TORTOISE SHELL BRACKET |  |
 |
| U+301A LEFT WHITE SQUARE BRACKET |  |
 |
| U+301B RIGHT WHITE SQUARE BRACKET |  |
 |
| U+301C WAVE DASH |  |
 |
| U+301D REVERSED DOUBLE PRIME QUOTATION MARK |  |
 |
| U+301E DOUBLE PRIME QUOTATION MARK |  |
 |
| U+301F LOW DOUBLE PRIME QUOTATION MARK |  |
|
| U+3030 WAVY DASH |  |
 |
| U+3041 HIRAGANA LETTER SMALL A |  |
 |
| U+3043 HIRAGANA LETTER SMALL I |  |
 |
| U+3045 HIRAGANA LETTER SMALL U |  |
 |
| U+3047 HIRAGANA LETTER SMALL E |  |
 |
| U+3049 HIRAGANA LETTER SMALL O |  |
 |
| U+3063 HIRAGANA LETTER SMALL TU |  |
 |
| U+3083 HIRAGANA LETTER SMALL YA |  |
 |
| U+3085 HIRAGANA LETTER SMALL YU |  |
 |
| U+3087 HIRAGANA LETTER SMALL YO |  |
 |
| U+308E HIRAGANA LETTER SMALL WA |  |
 |
| U+3095 HIRAGANA LETTER SMALL KA |  |
 |
| U+3096 HIRAGANA LETTER SMALL KE |  |
 |
| U+309B KATAKANA-HIRAGANA VOICED SOUND MARK |  |
 |
| U+309C KATAKANA-HIRAGANA SEMI-VOICED SOUND MARK |  |
 |
| U+30A0 KATAKANA-HIRAGANA DOUBLE HYPHEN |  |
 |
| U+30A1 KATAKANA LETTER SMALL A |  |
 |
| U+30A3 KATAKANA LETTER SMALL I |  |
 |
| U+30A5 KATAKANA LETTER SMALL U |  |
 |
| U+30A7 KATAKANA LETTER SMALL E |  |
 |
| U+30A9 KATAKANA LETTER SMALL O |  |
 |
| U+30C3 KATAKANA LETTER SMALL TU |  |
 |
| U+30E3 KATAKANA LETTER SMALL YA |  |
 |
| U+30E5 KATAKANA LETTER SMALL YU |  |
 |
| U+30E7 KATAKANA LETTER SMALL YO |  |
 |
| U+30EE KATAKANA LETTER SMALL WA |  |
 |
| U+30F5 KATAKANA LETTER SMALL KA |  |
 |
| U+30F6 KATAKANA LETTER SMALL KE |  |
 |
| U+30FC KATAKANA-HIRAGANA PROLONGED SOUND MARK |  |
 |
| U+3127 BOPOMOFO LETTER I |   |
|
| U+31F0 KATAKANA LETTER SMALL KU |  |
 |
| U+31F1 KATAKANA LETTER SMALL SI |  |
 |
| U+31F2 KATAKANA LETTER SMALL SU |  |
 |
| U+31F3 KATAKANA LETTER SMALL TO |  |
 |
| U+31F4 KATAKANA LETTER SMALL NU |  |
 |
| U+31F5 KATAKANA LETTER SMALL HA |  |
 |
| U+31F6 KATAKANA LETTER SMALL HI |  |
 |
| U+31F7 KATAKANA LETTER SMALL HU |  |
 |
| U+31F8 KATAKANA LETTER SMALL HE |  |
 |
| U+31F9 KATAKANA LETTER SMALL HO |  |
 |
| U+31FA KATAKANA LETTER SMALL MU |  |
 |
| U+31FB KATAKANA LETTER SMALL RA |  |
 |
| U+31FC KATAKANA LETTER SMALL RI |  |
 |
| U+31FD KATAKANA LETTER SMALL RU |  |
 |
| U+31FE KATAKANA LETTER SMALL RE |  |
 |
| U+31FF KATAKANA LETTER SMALL RO |  |
 |
| U+32FF SQUARE ERA NAME REIWA |  |
 |
| U+3300 SQUARE APAATO |  |
 |
| U+3301 SQUARE ARUHUA |  |
 |
| U+3302 SQUARE ANPEA |  |
 |
| U+3303 SQUARE AARU |  |
 |
| U+3304 SQUARE ININGU |  |
 |
| U+3305 SQUARE INTI |  |
 |
| U+3306 SQUARE UON |  |
 |
| U+3307 SQUARE ESUKUUDO |  |
 |
| U+3308 SQUARE EEKAA |  |
 |
| U+3309 SQUARE ONSU |  |
 |
| U+330A SQUARE OOMU |  |
 |
| U+330B SQUARE KAIRI |  |
 |
| U+330C SQUARE KARATTO |  |
 |
| U+330D SQUARE KARORII |  |
 |
| U+330E SQUARE GARON |  |
 |
| U+330F SQUARE GANMA |  |
 |
| U+3310 SQUARE GIGA |  |
 |
| U+3311 SQUARE GINII |  |
 |
| U+3312 SQUARE KYURII |  |
 |
| U+3313 SQUARE GIRUDAA |  |
 |
| U+3314 SQUARE KIRO |  |
 |
| U+3315 SQUARE KIROGURAMU |  |
 |
| U+3316 SQUARE KIROMEETORU |  |
 |
| U+3317 SQUARE KIROWATTO |  |
 |
| U+3318 SQUARE GURAMU |  |
 |
| U+3319 SQUARE GURAMUTON |  |
 |
| U+331A SQUARE KURUZEIRO |  |
 |
| U+331B SQUARE KUROONE |  |
 |
| U+331C SQUARE KEESU |  |
 |
| U+331D SQUARE KORUNA |  |
 |
| U+331E SQUARE KOOPO |  |
 |
| U+331F SQUARE SAIKURU |  |
 |
| U+3320 SQUARE SANTIIMU |  |
 |
| U+3321 SQUARE SIRINGU |  |
 |
| U+3322 SQUARE SENTI |  |
 |
| U+3323 SQUARE SENTO |  |
 |
| U+3324 SQUARE DAASU |  |
 |
| U+3325 SQUARE DESI |  |
 |
| U+3326 SQUARE DORU |  |
 |
| U+3327 SQUARE TON |  |
 |
| U+3328 SQUARE NANO |  |
 |
| U+3329 SQUARE NOTTO |  |
 |
| U+332A SQUARE HAITU |  |
 |
| U+332B SQUARE PAASENTO |  |
 |
| U+332C SQUARE PAATU |  |
 |
| U+332D SQUARE BAARERU |  |
 |
| U+332E SQUARE PIASUTORU |  |
 |
| U+332F SQUARE PIKURU |  |
 |
| U+3330 SQUARE PIKO |  |
 |
| U+3331 SQUARE BIRU |  |
 |
| U+3332 SQUARE HUARADDO |  |
 |
| U+3333 SQUARE HUIITO |  |
 |
| U+3334 SQUARE BUSSYERU |  |
 |
| U+3335 SQUARE HURAN |  |
 |
| U+3336 SQUARE HEKUTAARU |  |
 |
| U+3337 SQUARE PESO |  |
 |
| U+3338 SQUARE PENIHI |  |
 |
| U+3339 SQUARE HERUTU |  |
 |
| U+333A SQUARE PENSU |  |
 |
| U+333B SQUARE PEEZI |  |
 |
| U+333C SQUARE BEETA |  |
 |
| U+333D SQUARE POINTO |  |
 |
| U+333E SQUARE BORUTO |  |
 |
| U+333F SQUARE HON |  |
 |
| U+3340 SQUARE PONDO |  |
 |
| U+3341 SQUARE HOORU |  |
 |
| U+3342 SQUARE HOON |  |
 |
| U+3343 SQUARE MAIKURO |  |
 |
| U+3344 SQUARE MAIRU |  |
 |
| U+3345 SQUARE MAHHA |  |
 |
| U+3346 SQUARE MARUKU |  |
 |
| U+3347 SQUARE MANSYON |  |
 |
| U+3348 SQUARE MIKURON |  |
 |
| U+3349 SQUARE MIRI |  |
 |
| U+334A SQUARE MIRIBAARU |  |
 |
| U+334B SQUARE MEGA |  |
 |
| U+334C SQUARE MEGATON |  |
 |
| U+334D SQUARE MEETORU |  |
 |
| U+334E SQUARE YAADO |  |
 |
| U+334F SQUARE YAARU |  |
 |
| U+3350 SQUARE YUAN |  |
 |
| U+3351 SQUARE RITTORU |  |
 |
| U+3352 SQUARE RIRA |  |
 |
| U+3353 SQUARE RUPII |  |
 |
| U+3354 SQUARE RUUBURU |  |
 |
| U+3355 SQUARE REMU |  |
 |
| U+3356 SQUARE RENTOGEN |  |
 |
| U+3357 SQUARE WATTO |  |
 |
| U+337B SQUARE ERA NAME HEISEI |  |
  |
| U+337C SQUARE ERA NAME SYOUWA |  |
  |
| U+337D SQUARE ERA NAME TAISYOU |  |
  |
| U+337E SQUARE ERA NAME MEIZI |  |
  |
| U+337F SQUARE CORPORATION |  |
  |
| U+FE50 SMALL COMMA |  |
  |
| U+FE51 SMALL IDEOGRAPHIC COMMA | |
 |
| U+FE52 SMALL FULL STOP |  |
  |
| U+FE59 SMALL LEFT PARENTHESIS |  |
 |
| U+FE5A SMALL RIGHT PARENTHESIS |  |
 |
| U+FE5B SMALL LEFT CURLY BRACKET |  |
 |
| U+FE5C SMALL RIGHT CURLY BRACKET |  |
 |
| U+FE5D SMALL LEFT TORTOISE SHELL BRACKET | |
|
| U+FE5E SMALL RIGHT TORTOISE SHELL BRACKET | |
|
| U+FF01 FULLWIDTH EXCLAMATION MARK |  |
  |
| U+FF08 FULLWIDTH LEFT PARENTHESIS | |
|
| U+FF09 FULLWIDTH RIGHT PARENTHESIS | |
|
| U+FF0C FULLWIDTH COMMA | |
 |
| U+FF0E FULLWIDTH FULL STOP | |
 |
| U+FF1A FULLWIDTH COLON |  |
  |
| U+FF1B FULLWIDTH SEMICOLON |  |
  |
| U+FF1F FULLWIDTH QUESTION MARK |  |
  |
| U+FF3B FULLWIDTH LEFT SQUARE BRACKET |  |
 |
| U+FF3D FULLWIDTH RIGHT SQUARE BRACKET |  |
 |
| U+FF3F FULLWIDTH LOW LINE |  |
 |
| U+FF5B FULLWIDTH LEFT CURLY BRACKET | |
|
| U+FF5C FULLWIDTH VERTICAL LINE |  |
 |
| U+FF5D FULLWIDTH RIGHT CURLY BRACKET | |
|
| U+FF5E FULLWIDTH TILDE |  |
 |
| U+FF5F FULLWIDTH LEFT WHITE PARENTHESIS |  |
 |
| U+FF60 FULLWIDTH RIGHT WHITE PARENTHESIS |  |
 |
| U+FFE3 FULLWIDTH MACRON |  |
 |
| U+1F200 SQUARE HIRAGANA HOKA |  |
 |
| U+1F201 SQUARED KATAKANA KOKO |  |
 |
Starting with Version 10.0.0 of the Unicode Standard, the data file listing the Vertical_Orientation property value assignments [Data50] is formally included in the Unicode Character Database [UCD]. In Revisions 17 and prior of this specification, the data file was provided in versioned directories under the following stable URL:
https://www.unicode.org/Public/vertical/
Thanks to the original editor Eric Muller, to the subsequent co-editor Laurențiu Iancu who drove the status change of the specification and the incorporation of its data into the UCD for Version 10.0, and reviewers: Julie Allen, Van Anderson, John Cowan, John Daggett, Mark Davis, Martin Dürst, Elika J. Etemad, Michael Everson, Asmus Freytag, Soji Ikeda, Norikazu Ishizu, Nozomu Katō, Yasuo Kida, Nat McCully, Shinyu Murakami, Addison Phillips, Roozbeh Pournader, Dwayne Robinson, Kyoko Sato, Hiroshi Takenaka, Bobby Tung, Philippe Verdy, Ken Whistler, Taro Yamamoto, the W3C CSS Working Group, the W3C I18N Interest Group, and the W3C Internationalization Working Group.
For references for this annex, see Unicode Standard Annex #41, “Common References for Unicode Standard Annexes.”
The following summarizes modifications from the previous published version of this annex.
Revision 27Revision 25 being a proposed update, only changes between revisions 24 and 26 are noted here.
Previous revisions can be accessed with the “Previous Version” link in the header.
© 2022 Unicode, Inc. All Rights Reserved. The Unicode Consortium makes no expressed or implied warranty of any kind, and assumes no liability for errors or omissions. No liability is assumed for incidental and consequential damages in connection with or arising out of the use of the information or programs contained or accompanying this technical report. The Unicode Terms of Use apply.
Unicode and the Unicode logo are trademarks of Unicode, Inc., and are registered in some jurisdictions.