Return-Path: Delivered-To: apmail-jakarta-lucene-dev-archive@apache.org Received: (qmail 5353 invoked from network); 22 Nov 2001 18:19:14 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 22 Nov 2001 18:19:14 -0000 Received: (qmail 11789 invoked by uid 97); 22 Nov 2001 18:19:16 -0000 Delivered-To: qmlist-jakarta-archive-lucene-dev@jakarta.apache.org Received: (qmail 11727 invoked by uid 97); 22 Nov 2001 18:19:15 -0000 Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Developers List" Reply-To: "Lucene Developers List" Delivered-To: mailing list lucene-dev@jakarta.apache.org Received: (qmail 11716 invoked from network); 22 Nov 2001 18:19:14 -0000 From: klicnik@ca.ibm.com Importance: Normal MIME-Version: 1.0 To: lucene-dev@jakarta.apache.org Subject: Separating translatable strings X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: Date: Thu, 22 Nov 2001 13:19:04 -0500 X-MIMETrack: Serialize by Router on D25ML01/25/M/IBM(Release 5.0.8 |June 18, 2001) at 11/22/2001 01:19:06 PM, Serialize complete at 11/22/2001 01:19:06 PM Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N We are actively pursuing the use of Lucene within the Eclipse platform (http://www.eclipse.org), initially as the search mechanism for online help. One of the things we noticed is that Lucene does not separate its strings for translation, and in several places writes to the console. In all cases we've seen, this involves error situations (throwing of exceptions with message, System.err.println logging) so the user will not typically see these if all is well. However, in Eclipse, we have generally translated all strings (error and otherwise) so we were wondering if there was any work under way/ planned to do the same in Lucene. We'd be willing to assist/ do the string separation pass and contribute the changes, but because it is a change that would span the entire Lucene codebase we are not sure how to contribute something like this. We use an Eclipse based tool to do string separation in our own code, so we could take a specific Lucene build through this and contribute it back. Or we could possibly make the tool available to the Lucene team to make this change. In terms of the System.out/ System.err output, Lucene should not be writing to the console. For example, Eclipse runs without a console so any such output is lost. It would be nice if the Lucene toolkit allowed the caller to set a "log handler" that Lucene writes to. The default implementation (supplied with the Lucene toolkit) could simply write to System.err. We could replace it to write to our Eclipse platform log instead. Any direction you can give us on this would be greatly appreciated ... -- To unsubscribe, e-mail: For additional commands, e-mail: