diff options
author | Haru <haru@dotalux.com> | 2015-12-31 14:48:00 +0100 |
---|---|---|
committer | Haru <haru@dotalux.com> | 2016-06-25 17:29:48 +0200 |
commit | 89d43a060f924e565650e7a8ed85c199c6f0db36 (patch) | |
tree | 476cf5efbe856eae366e699310bc16df59eee8ca /3rdparty/pcre | |
parent | be570dd88f744efcf837a69901ad60bb1c78fffe (diff) | |
download | hercules-89d43a060f924e565650e7a8ed85c199c6f0db36.tar.gz hercules-89d43a060f924e565650e7a8ed85c199c6f0db36.tar.bz2 hercules-89d43a060f924e565650e7a8ed85c199c6f0db36.tar.xz hercules-89d43a060f924e565650e7a8ed85c199c6f0db36.zip |
Added option to strip hard line-breaks from `mes` dialogs
- The `\r` character, in a `mes` dialog, is normally represented by the
client as a hard line-break.
- Since a client may have different requirements in line lengths (for
example using a font with different size or metrics), an user might
wish to ignore hard-wraps and let the client automatically soft-wrap
instead.
- If you want to hard-wrap (official default), keep the
SCRIPT_MES_STRIP_LINEBREAK define commented out.
- If you want to let the client soft-wrap automatically (may work better
for custom clients), uncomment it.
- Imprved HULD handling of `\r` (to avoid control characters in the
generated file)
- Please note that this requires cooperation by script writers:
* Each `mes` should contain one and only one sentence, possibly
without using the '+' concatenation (but, rather, sprintf).
* Two separate sentences (where a hard-wrap is required even for
soft-wrapped text) should always go into separate `mes` commands.
* Following the above two recommendations, also produces a better
quality translations .pot file.
Signed-off-by: Haru <haru@dotalux.com>
Diffstat (limited to '3rdparty/pcre')
0 files changed, 0 insertions, 0 deletions