From pnewton@gmx.de Tue Jul 01 03:09:43 2003 Received: with ECARTIS (v1.0.0; list lojban-list); Tue, 01 Jul 2003 03:10:00 -0700 (PDT) Received: from postman1.arcor-online.net ([151.189.0.187] helo=postman.arcor.de) by digitalkingdom.org with esmtp (Exim 4.12) id 19XI4Y-0006XN-00 for lojban-list@lojban.org; Tue, 01 Jul 2003 03:09:15 -0700 Received: from hamwpne1 ([212.13.198.90]) (authenticated bits=0) by postman.arcor.de (8.12.9/8.12.9) with ESMTP id h61A9A2I006458 for ; Tue, 1 Jul 2003 12:09:11 +0200 (MEST) From: "Philip Newton" Organization: datenrevision GmbH & Co. OHG To: lojban-list@lojban.org Date: Tue, 01 Jul 2003 12:09:09 +0200 MIME-Version: 1.0 Subject: [lojban] Re: {WebMaster} Site Update: New translatable files. Message-ID: <3F0179E5.6039.D81E5A@localhost> Priority: normal In-reply-to: <20030630171640.GT16610@digitalkingdom.org> References: <3F000370.14141.360ECE@localhost> X-mailer: Pegasus Mail for Windows (v4.02a) Content-Type: text/plain; charset=US-ASCII Content-description: Mail message body X-archive-position: 5790 X-ecartis-version: Ecartis v1.0.0 Sender: lojban-list-bounce@lojban.org Errors-to: lojban-list-bounce@lojban.org X-original-sender: pnewton@gmx.de Precedence: bulk Reply-to: lojban-list@lojban.org X-list: lojban-list On 30 Jun 2003 at 10:16, Robin Lee Powell wrote: > I love how you're all telling me this *after* Gary has already > marked up ~20 files, rather than in the month or so preceding. More translating strings means more opportunity for problems (such as reusing strings on a different page in a different context). The strings that were available previously weren't as inconvenient, so I didn't think of it too much. Still, my apologies. (By the way, what if there are typos in the English? I spotted one or two but did not make note of them. Presumably, if they are fixed, the translation for that chunk will be invalidated since it won't match exactly any more.) > So who of the people who want this new style is offering to fix all > of the already marked up files? What is involved? Fixing only the English, causing translations to revert to English as well because the source doesn't match, so that translators will have to iteratively fix them at their convenience? Or fixing the English *and* all the existing translations? At any rate, I'll offer to help marking up the files; I assume this is a task that can be distributed. Cheers, Philip -- filip.niutyn.