text-orientation mixed/upright Lookup
Supported vertical text-orientation token semantics, not glyph/font support inference. Explicit supplied computed/layout context only; not a browser cascade/layout engine or cross-browser guarantee.
Description
Text orientation determines how characters are presented within vertical writing.
Text orientation determines how characters are presented within vertical writing.1
It is a separate concept from the block and inline axes of writing-mode. Use text-orientation mixed/upright Lookup to look up a supported term.
When to use text-orientation mixed/upright Lookup
Use text-orientation mixed/upright Lookup to look up a supported term. Choose the exact supported token from the table; preserve its punctuation and capitalization.
How to use text-orientation mixed/upright Lookup and understand its results
- Choose the exact supported token from the table; preserve its punctuation and capitalization.
- Enter Text orientation using the field table and validation rules below, then run the tool.
- Read Meaning and interpret units, signs, ordering and placeholders as explained below.
- If the tool reports an input error, correct that field and rerun. A successful false result, empty match list or unknown-evidence placeholder has the specific meaning described here; check the limitations before applying the result.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| textOrientation | Text orientation | string | Required; constraints below |
Enter one of the exact supported textOrientation tokens in the table below. The implementation performs a case-sensitive lookup and returns the stored meaning without interpreting a stylesheet, audio recording or performance. Unsupported tokens, added whitespace and alternate capitalization are input errors. The entries describe a bounded vocabulary rather than every valid value in the wider topic.
meaning = storedTable[exactSupportedToken] Field order, units and branch conditions follow the implementation explanation above.
| Exact supported token | Stored meaning |
|---|---|
| mixed | in vertical writing, orientation follows Unicode vertical-orientation behavior |
| upright | in vertical writing, characters upright and used direction is ltr |
| sideways | typographic characters laid out horizontally and line rotated |
| Output field | Meaning | Value type |
|---|---|---|
| meaning | Stored explanation for the exact supported token. | string |
{
"input": {
"textOrientation": "upright"
},
"output": {
"meaning": "in vertical writing, characters upright and used direction is ltr"
}
}Limitations and assumptions
It is a separate concept from the block and inline axes of writing-mode. Apply the exact scope and assumptions described above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are stated above; extremely large inputs or outputs can also be rejected. These errors differ from successful results such as false, no matches or unknown evidence.
Alternative or Complementary methods
Use writing-mode vertical-rl Orientation Lookup for a related task: Writing mode separates inline progression from block progression.
Use word-break vs overflow-wrap Compare for a related task: Word-breaking policies affect where text may wrap and how intrinsic width is calculated.
References
-
text-orientation mixed/upright Lookup — tool.io
Similar or alternative tools
- writing-mode vertical-rl Orientation Lookup
Writing mode separates inline progression from block progression.
- word-break vs overflow-wrap Compare
Word-breaking policies affect where text may wrap and how intrinsic width is calculated.