lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otis Gospodnetic <>
Subject Re: Separating translatable strings
Date Tue, 27 Nov 2001 05:11:56 GMT
Hm, nobody is responding to this generous offer, so here are my two

No, I do not think that there are any plans for doing this, nor is
there any work related to this that is underway.
I think it would be nice to 'internationalize' Lucene.  It may help its
popularity among non-English speaking users and it would make Lucene
more a complete, a more polished product.

This sounds like a relatively big change and I would imagine that Doug
would want to release version 1.2 and then you could work with that
version of Lucene and contribute back your changes.



--- wrote:
> We are actively pursuing the use of Lucene within the Eclipse
> platform 
> (, 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:
> <>

Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message