From nobody@digitalkingdom.org Fri Jun 20 02:38:09 2008 Received: with ECARTIS (v1.0.0; list lojban-list); Fri, 20 Jun 2008 02:38:09 -0700 (PDT) Received: from nobody by chain.digitalkingdom.org with local (Exim 4.69) (envelope-from ) id 1K9d4L-0008Lm-CY for lojban-list-real@lojban.org; Fri, 20 Jun 2008 02:38:09 -0700 Received: from wf-out-1314.google.com ([209.85.200.168]) by chain.digitalkingdom.org with esmtp (Exim 4.69) (envelope-from ) id 1K9d4G-0008LX-Pb for lojban-list@lojban.org; Fri, 20 Jun 2008 02:38:09 -0700 Received: by wf-out-1314.google.com with SMTP id 23so907295wfg.25 for ; Fri, 20 Jun 2008 02:38:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=mac6AprEhySnw8U86K2BykKVmjHu9dopiS52NTqcJHA=; b=LbBEZsZOWGvLyIkVy5W2jxLWQaqUs9R9eGoa5c5fMljGa/bJ95z4/NMtCYMOIUy8UN P77YVootE1fzF3lGQuTgdMuQe9rJ7PGWH8P35yfBHRWXlHtWhrYa/9/Yg+VTzMcx2oLE iyGUYmhB2NrCkDwQhL+aRt19Be2+0YfzW96Aw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=QTfR8sAhvy84FSgRpzr7lOcQIQo1Oyyp8BlGVuD1g8VbcWp1EASTu3SJbekKlfr0CV TAL6WbsNxCZ5GQI1wn1yjApLPhet83GK4orMNlVCJi4kotCRa0b+d7MOhau4bjrYaMj0 3VBTGvlNQSRcRBNC5Cmo4n3GWpCaXFmNojjvQ= Received: by 10.142.186.9 with SMTP id j9mr1094680wff.348.1213954680748; Fri, 20 Jun 2008 02:38:00 -0700 (PDT) Received: by 10.143.1.3 with HTTP; Fri, 20 Jun 2008 02:38:00 -0700 (PDT) Message-ID: <8900cc410806200238q46b0d461g2aecb14242fbecd2@mail.gmail.com> Date: Fri, 20 Jun 2008 13:38:00 +0400 From: "Dmitry Shintyakov" To: lojban-list@lojban.org Subject: [lojban] Re: lojgloss and linebreaks In-Reply-To: <737b61f30806192246u28840568pfb92f4a0728c123e@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <737b61f30806192246u28840568pfb92f4a0728c123e@mail.gmail.com> X-Spam-Score: -0.0 X-Spam-Score-Int: 0 X-Spam-Bar: / X-archive-position: 14523 X-ecartis-version: Ecartis v1.0.0 Sender: lojban-list-bounce@lojban.org Errors-to: lojban-list-bounce@lojban.org X-original-sender: shintyakov@gmail.com Precedence: bulk Reply-to: lojban-list@lojban.org X-list: lojban-list Hello Chris. 2008/6/20 Chris Capel : > Conventionally, casually, I think a paragraph break in text (or a > double-linebreak in plain text) does imply a new paragraph, and I'll > probably treat it as such whether or not it's technically accurate. > But I was wondering if the convention had any formal backing. Well, though casually paragraph break in text can sometimes really imply new paragraph, personally I do not like the idea of embedding such behavior in parser. I believe that programs must be simple and predictable. They should what they was told to do. Embedding different special cases, exceptions of rules and other things is just an easy way to mess things up a lot. If you really like the idea of implementing such features, maybe it would be better to make them optional? After all, paragraph in text may be just element of formatting, and it is not exactly the same as {ni'o} Dmitry. To unsubscribe from this list, send mail to lojban-list-request@lojban.org with the subject unsubscribe, or go to http://www.lojban.org/lsg2/, or if you're really stuck, send mail to secretary@lojban.org for help.