How to type Capital OE Ligature
To type Capital OE Ligature (Œ), press Alt + 0140 on Windows, holding Alt while typing the digits on the numeric keypad, or press Option + Shift + Q on Mac, or write Œ in HTML. On any system you can copy it from this page, or enter its codepoint U+0152 directly: Ctrl+Shift+U then 0152 on Linux, or 0152 then Alt+X in Microsoft Word.
Latin Capital Ligature Oe
- Copy it
- Unicode
- U+0152
- Windows
- Alt + 0140
| Where | Shortcut | How |
|---|---|---|
| Windows | Alt + 0140 | Hold Alt and type the number on the numeric keypad. |
| Mac | Option + Shift + Q | Press the keys together. |
| HTML | Π| Paste this into HTML source. |
| Unicode | U+0152 | LATIN CAPITAL LIGATURE OE |
Other accents symbols
Πlives in the Latin Extended-A block (U+0100-U+017F), further accented letters for Central and Eastern European languages. Within Unicode it is classified as Lu, an uppercase letter. It has a lowercase counterpart and changes under case conversion. Its bidirectional class makes it left-to-right.
Its lowercase counterpart is œ (U+0153). They are separate codepoints, so a byte comparison treats them as different characters even though a case-insensitive search does not.
How Capital OE Ligature behaves in software
Πis East Asian Ambiguous: one column in a Western locale and two in a CJK one. That is why a table that lines up on your machine can break on somebody else's, with no change to the text at all. It is a left-to-right character, so it holds that direction even inside a right-to-left paragraph.
Every way to write Capital OE Ligature
| Form | Value |
|---|---|
| Codepoint | U+0152 |
| Decimal | 338 |
| UTF-8 bytes | C5 92 |
| UTF-16 bytes | 01 52 |
| HTML entity | Π|
| HTML numeric | Πor Π|
| CSS | \0152 |
| JavaScript | \u0152 |
| Python | \u0152 |
| URL-encoded | %C5%92 |
| SVG | 0152.svg · (SIL Open Font License) |
If Œ arrives as Å’
That is this exact character, undamaged: its two UTF-8 bytes C5 92 are being read one at a time as Windows-1252. The Latin-1 range is where this happens most, because it is the range every legacy system thought it already handled. Nothing is lost, and retyping will not help: the fix is at the reading end, which has to be told the text is UTF-8. An empty rectangle is the opposite complaint, and means the encoding is right and the font has no glyph for U+0152.