Xenthos2009-05-17 18:15:54
Please let reading letters / books / help files / other hard-coded things be affected by wrapwidth-- I get the feeling that this will be difficult given the way that writing them is set up, but copying / pasting from these things is a massive pain when it inserts a newline after every 80 characters. Have to go through and delete every single newline in the middle of each paragraph.
Everiine2009-05-17 18:51:11
I use Notepad to write everything and use the wrapwidth there. Then when I go to paste it into a letter/post/book, I turn the wrapwidth off in Notepad putting every paragraph on one line. That usually helps for me.
Xenthos2009-05-17 18:52:38
QUOTE (Everiine @ May 17 2009, 02:51 PM) <{POST_SNAPBACK}>
I use Notepad to write everything and use the wrapwidth there. Then when I go to paste it into a letter/post/book, I turn the wrapwidth off in Notepad putting every paragraph on one line. That usually helps for me.
You've got the suggestion backwards.
This is for getting it back from Lusternia, not putting it in (putting it in is just fine without using wrapwidth since it will autowrap). But reading things back from Lusternia has a forced-80 wrap.
Everiine2009-05-17 19:59:41
Ooooooooooh, whoops.
Fain2009-05-18 07:16:59
The downside would be the destruction of pretty borders, ascii art, etc for anyone who doesn't use the default wrapwidth.
Esano2009-05-18 07:24:11
QUOTE (Fain @ May 18 2009, 05:16 PM) <{POST_SNAPBACK}>
The downside would be the destruction of pretty borders, ascii art, etc for anyone who doesn't use the default wrapwidth.
I considered this, but when you're making pretty borders and ascii art you add in your own newlines there anyway. I don't know of anyone who does it with whole paragraphs, relying on the ingame wrapwidth.
There would be problems with people who use -under- the wrapwidth the author does, though (presumably people would stick to the current for ascii/borders/etc.).
Fain2009-05-18 07:26:29
QUOTE (Esano @ May 18 2009, 03:24 AM) <{POST_SNAPBACK}>
I considered this, but when you're making pretty borders and ascii art you add in your own newlines there anyway..
That's a very good point. Although there's still an issue with people publishing books at a higher wrapwidth than their audience.
Edit:
QUOTE
There would be problems with people who use -under- the wrapwidth the author does, though (presumably people would stick to the current for ascii/borders/etc.).
Did you just ninja-edit this in, or did I not read your whole post?
Xenthos2009-05-18 11:25:45
QUOTE (Fain @ May 18 2009, 03:26 AM) <{POST_SNAPBACK}>
That's a very good point. Although there's still an issue with people publishing books at a higher wrapwidth than their audience.
Edit:
Did you just ninja-edit this in, or did I not read your whole post?
Edit:
Did you just ninja-edit this in, or did I not read your whole post?
It might be possible to still keep the writing itself at WW80, just so there's always the exact same underlying format behind each published work (of course, if someone goes to less than WW80 they'd start having issues, but how many people do that? Excepting for WW0, which is actually no wrap-width.) I don't know how the code itself works and perhaps both writing and reading would have to change for this to even be possible, but I was hoping it could just be done for the reading end of things.
Edit: Having given a little further thought to how the writing ends works, that's probably an unlikely hope. Ah well. It would still be nice if we weren't stuck with WW80 for reading from these things, even if writing has to change a bit as well.