Just a minor annoyance but ca
n't text be split on word bound
aries or even hyphenated?
Text Splits in the Wrong Place
Moderator: Board moderators
-
Leaf
- Forum Aficionado
- Posts: 1994
- Joined: Tue Apr 29, 2003 5:55 pm
- Location: Minnesota, USA
- Contact:
There have been a few map updates to correct this.
What would be more helpful is an actual listing of maps (prefer with full map path) and NPC or "object" (sign, book, et al.) that was the line breaks in mid sentence.
What would be more helpful is an actual listing of maps (prefer with full map path) and NPC or "object" (sign, book, et al.) that was the line breaks in mid sentence.
"Put another, more succinct way: don't complain, contribute. It's more satisfying in the long run, and it's more constructive."
Eric Meyer
Eric Meyer
Which client is this observed on?
Proper wrapping is really the responsibility of the client, but there are two pieces. If the data sent from the server has line breaks, the client will honor those. This can result in choppy text for the older formatted messages and the width of the text view is smaller than that width (the formatting was for 40 chars IIRC, so if you window is 30 chars wide, you would get 30 characters, line break, 10 chars, line break, 30 chars, etc)
The second piece is that the client should properly wrap text that is properly formatted. But each client has its own logic - so depending on what client is used may result in different behavior, and there isn't a single place to fix it - all the clients need changes.
Proper wrapping is really the responsibility of the client, but there are two pieces. If the data sent from the server has line breaks, the client will honor those. This can result in choppy text for the older formatted messages and the width of the text view is smaller than that width (the formatting was for 40 chars IIRC, so if you window is 30 chars wide, you would get 30 characters, line break, 10 chars, line break, 30 chars, etc)
The second piece is that the client should properly wrap text that is properly formatted. But each client has its own logic - so depending on what client is used may result in different behavior, and there isn't a single place to fix it - all the clients need changes.