Re: Re: [dict-beta] Wrapping

[Rik F. <fa...@di...>]

On Sat  5 May 2001 20:26:02 -0700,
   Navdeep Bains <pop...@jp...> wrote:
> This is my reply to "Re: [dict-beta] Wrapping" from "Navdeep Bains"
> <pop...@jp...>:
> 
> Wait, Elements is wrapped when it doesn't need to be, and so is Jargon
> File. I noticed that some databases use spaces at the beginning of
> each line, forcing the database to be wrapped, but Elements & Jargon
> File don't follow this trend, why are they wrapped?

Elements has some simple formatting, e.g.:
  copper
  Symbol: Cu
  Atomic number: 29
  Atomic weight: 63.54
  Red-brown transition element. Known by the Romans as 'cuprum.' Extracted
  and used for thousands of years. Malleable, ductile and an excellent
  conductor of heat and electricity. When in moist conditions, a greenish
  layer forms on the outside.

This would be less useful (and arguably unreadable) if you wrapped it
without any formatting information:
  copper Symbol: Cu Atomic number: 29 Atomic weight: 63.54 Red-brown
  transition element. Known by the Romans as 'cuprum.' Extracted and
  used for thousands of years. Malleable, ductile and an excellent
  conductor of heat and electricity. When in moist conditions, a
  greenish layer forms on the outside.

There are entries in jargon that have similar requirements (e.g.,
"indent style").  Unfortunately the current jargon databases are being
formatted incorrectly and are failing to preserve the necessary
indentation (so, the examples for Allman style and Whitesmiths style in
this entry are wrong).

The bottom line is that you can't expect the client to wrap for you
unless you provide enough formatting information such that the client
can wrap correctly.