5,389
edits
(→Non-translated US-ASCII: this is getting out of control...) |
(→Over-long text: oh my) |
||
Line 1,268: | Line 1,268: | ||
===Over-long text=== | ===Over-long text=== | ||
====Screen resolutions in Chinese Oni==== | |||
Although Chinese text strings typically have a much smaller number of glyphs than English originals, this is not always the case. The Chinese glyphs are also much wider on average, with each glyph taking up 16x16 pixels, and so there are situations where the rendered Chinese line is much wider than the English original, no longer fitting on one line as intended by the context. | Although Chinese text strings typically have a much smaller number of glyphs than English originals, this is not always the case. The Chinese glyphs are also much wider on average, with each glyph taking up 16x16 pixels, and so there are situations where the rendered Chinese line is much wider than the English original, no longer fitting on one line as intended by the context. | ||
This is only known to cause a problem for the "resolution" item in the Options menu (a WMM_ generated at runtime). The actual dropdown list is wide enough to accommodate even the longest resolution strings, but the currently selected resolution appears in a small window that is only 150 pixels wide, too narrow even for the shortest resolution string "640×480×16位" (which needs 176 pixels). As a result the active resolution is always displayed on two lines, no longer fitting into the frame vertically and thus unreadable. | This is only known to cause a problem for the "resolution" item in the Options menu (a WMM_ generated at runtime). The actual dropdown list is wide enough to accommodate even the longest resolution strings, but the currently selected resolution appears in a small window that is only 150 pixels wide, too narrow even for the shortest resolution string "640×480×16位" (which needs 176 pixels). As a result the active resolution is always displayed on two lines, no longer fitting into the frame vertically and thus unreadable. | ||
====Long subtitles in Asian Oni==== | |||
Another "over-long" issue is for Japanese or Chinese subtitles that are too long to fit on the screen horizontally. In such situations the engine displays the subtitle on multiple lines, placing line breaks at arbitrary positions instead of at ideographic spaces or after punctuation (if any), and aligning the ''end'' of the over-long string to the right of the screen, rather than vice-versa. This looks especially awkward when a subtitle is only slightly over-long and the automatic line break occurs near the ''start'' of the string, in the middle of a speaker's name (subtitles practically always have a colon ''and'' space after the speaker's name, and an arbitrary word break intuitively makes no sense in the vicinity of a space). For Western languages, the space character is registered as a line-breaking character in [[TSFL]]Roman, and allows for sensible display of long text, seeing as spaces occur both between words and after punctuation. Asian languages should supposedly do the same by specifying the ideographic space (a two-byte code point) as a line-breaking character, and possibly by setting up some rules for ideographic punctuation as well. In practice there is no such thing, hence the over-long subtitle issue. | |||
(For the Japanese Oni, a possible workaround would be to insert an ASCII space character, or a narrow variant thereof, after punctuation. Chinese Oni doesn't support ASCII characters in text at all.) | |||
===Chinese SUBT issues=== | ===Chinese SUBT issues=== |