Re: In search of a more-vanilla vanilla TXT

i said:
a web-browser won't wrap the lines on a .txt file, so if the hard-returns were removed from p.g. .txt files, the lines would run off the screen of a web-browser.
i'm sorry. i was wrong. safari (at least) does wrap the lines. i'm not sure where i got that idea... at any rate, my apologies for the misinformation. -bowerbird

"Bowerbird" == Bowerbird <Bowerbird@aol.com> writes:
Bowerbird> i said: >> a web-browser won't wrap the lines on a .txt file, so if the >> hard-returns were removed from p.g. .txt files, the lines would >> run off the screen of a web-browser. Bowerbird> i'm sorry. i was wrong. safari (at least) does wrap Bowerbird> the lines. Bowerbird> i'm not sure where i got that idea... Bowerbird> at any rate, my apologies for the misinformation. Most browsers (IE, firefox, opera, konqueror) don't wrap, at least in the default configuration. Which makes sense, since wrapping may destroy information. I agree that PG should provide several custom TXT file formats. One might convert on the fly from one format to the other. Who cares to tune manually lines that are shorter than 55 characters? Still, this is one of the requirements, and one that often requires some time to achieve. One txt file in a sufficently rich encoding to allow correct representation is sufficient, everything else might be generated on the fly. And the best would be the format that carries most information: unicode, with the original line breaks as much as possible. Consider also that many HTML files are now provided with the original line breaks, and having the storage TXT file with the same lines would greatly simplify maintenance. Especially if one derives the txt file from the HTML automatically (or even better both from a common master). Carlo Traverso
participants (2)
-
Bowerbird@aol.com
-
traverso@posso.dm.unipi.it