What ¦ means
Use your editor’s Unicode input for U+FFE4.
A Japanese legacy conversion can also produce ¦ from the double-byte value FA55; conversion tables do not all map related bytes the same way.
Why was a wide broken bar encoded?
It keeps the broken bar in a wide character cell.
Older mixed-width East Asian text systems placed characters in one-cell or two-cell spaces so lines could align. Unicode 1.1 lists ¦ as a wide form of ¦, with its earliest clear record in 1993.
The Japanese JIS X 0213 character set, documented in 2000, places the related broken-bar entry at row 9, cell 5. Windows CP932 uses the extended double-byte value FA55 for ¦, while other Japanese conversion tables can map related bytes to ¦. These are encoding differences, not separate bar meanings.
Technical and archival: it preserves width in legacy text where character-cell alignment matters.
Do not substitute it for the solid programming pipe |.
Don't confuse it with
2Questions people ask
2Why does ¦ become ¦?
Compatibility normalization NFKC or NFKD folds the width distinction and produces ¦. Preserve the original text or use NFC when that distinction matters.
Why does ¦ look different in different fonts?
Fullwidth describes its character-cell behavior, not one fixed outline. Fonts can draw the break at different heights or proportions while showing the same character.
How to type ¦
¦\FFE4Codes and encoding1 code points
A visible symbol can contain several code points. JS .length counts UTF-16 units; UTF-8 counts bytes.
