Received: from localhost ([::1]:33253 helo=stodi.digitalkingdom.org) by stodi.digitalkingdom.org with esmtp (Exim 4.80.1) (envelope-from ) id 1YIBfq-0000y5-AB; Sun, 01 Feb 2015 23:43:58 -0800 Received: from mail-we0-f169.google.com ([74.125.82.169]:49302) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1YIBfn-0000xu-9R for llg-members@lojban.org; Sun, 01 Feb 2015 23:43:55 -0800 Received: by mail-we0-f169.google.com with SMTP id u56so37352353wes.0 for ; Sun, 01 Feb 2015 23:43:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=8nZEqZNDolWKmROBJTUH14HwWWxDX/Y1tTzhhSPMmYk=; b=RycYqIoGaFhz1tqU7SO7X9pVD8CDGOmeAhWys1NNADGc5cjN10qwrSZoDhYWF4jd3Y BZpQYBy8rtQGOCNBYP1T1ULv6UX/VJiBOd+Sie0b0nmt4PxIggv5F/gFIHsS9bsiujsB BE3zNTMuATdYoaNjjz/kDR5XPYbS4PE868tCZirqYYqJW2X8XGAXiOnM2YPN/nhc9bnZ +lJJ2QkzPEO6TaZ7UsSwG2lsbW7QVi/jPvsJcKb8Lo/nFQKw9Rc9AU8uPM29htgIvSKY 9nzIk+9b5rLR3MDiQ2NNVyPn9mXr/Nom/T3tj/keY5y6HZz4mtCXg9YTgv1Vf2fJhM6M 1lOw== X-Received: by 10.194.234.2 with SMTP id ua2mr39274445wjc.40.1422863028295; Sun, 01 Feb 2015 23:43:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.86.200 with HTTP; Sun, 1 Feb 2015 23:43:28 -0800 (PST) In-Reply-To: <20150201181937.GQ3433@stodi.digitalkingdom.org> References: <20150201181937.GQ3433@stodi.digitalkingdom.org> From: Gleki Arxokuna Date: Mon, 2 Feb 2015 10:43:28 +0300 Message-ID: To: llg-members@lojban.org X-Spam-Score: 0.7 (/) X-Spam_score: 0.7 X-Spam_score_int: 7 X-Spam_bar: / X-Spam-Report: Spam detection software, running on the system "stodi.digitalkingdom.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: 2015-02-01 21:19 GMT+03:00 Robin Lee Powell : > The general process here would be to include the changes into the > CLL build process in such a way that changes are marked in red/green > or whatever (i.e. something like a colorized diff, but at the > paragraph level). This should not be hard *at all*. Bob calls > these "change pages", although what I have in mind isn't exactly the > same thing > [...] Content analysis details: (0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 2.7 DNS_FROM_AHBL_RHSBL RBL: Envelope sender listed in dnsbl.ahbl.org [listed in gmail.com.rhsbl.ahbl.org. IN] [A] 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: digitalkingdom.org] -0.0 RCVD_IN_MSPIKE_H3 RBL: Good reputation (+3) [74.125.82.169 listed in wl.mailspike.net] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gleki.is.my.name[at]gmail.com) 0.0 HTML_MESSAGE BODY: HTML included in message -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.0 RCVD_IN_MSPIKE_WL Mailspike good senders Subject: Re: [Llg-members] My past plans for future versions of the CLL. X-BeenThere: llg-members@lojban.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: llg-members@lojban.org Content-Type: multipart/mixed; boundary="===============4742414507361202150==" Errors-To: llg-members-bounces@lojban.org --===============4742414507361202150== Content-Type: multipart/alternative; boundary=089e0141a1605d9e06050e161d1e --089e0141a1605d9e06050e161d1e Content-Type: text/plain; charset=UTF-8 2015-02-01 21:19 GMT+03:00 Robin Lee Powell : > The general process here would be to include the changes into the > CLL build process in such a way that changes are marked in red/green > or whatever (i.e. something like a colorized diff, but at the > paragraph level). This should not be hard *at all*. Bob calls > these "change pages", although what I have in mind isn't exactly the > same thing > For updating partial Russian translation of CLL github diffs would be enough imo. --089e0141a1605d9e06050e161d1e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= 2015-02-01 21:19 GMT+03:00 Robin Lee Powell <rlpowell@digitalk= ingdom.org>:
The general process here would be= to include the changes into the
CLL build process in such a way that changes are marked in red/green
or whatever (i.e. something like a colorized diff, but at the
paragraph level).=C2=A0 This should not be hard *at all*.=C2=A0 Bob calls these "change pages", although what I have in mind isn't exac= tly the
same thing

For updating partial Russian transla= tion of CLL github diffs would be enough imo.
--089e0141a1605d9e06050e161d1e-- --===============4742414507361202150== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Llg-members mailing list Llg-members@lojban.org http://mail.lojban.org/mailman/listinfo/llg-members --===============4742414507361202150==--