openstack team mailing list archive

[Eric Windisch <eric@xxxxxxxxxxxxxxxx>]

Error codes are also searchable, but I agree that text is even more search-aware. However, also as a Yankee, I often find search results for an error string leading me to a site in, say, Russian or Korean.  This is a direct result of log messages NOT being i18n'ed.  I suppose it swings both ways...  

--  
Eric Windisch


On Monday, February 13, 2012 at 2:41 PM, Joshua Harlow wrote:

> Re: [Openstack] Question on i8ln? Agreed, I do that as well.
>  
> But I’m also a biased yankee, now a californian (not hippie/ster yet, haha).
>  
> On 2/13/12 2:37 PM, "Andrew Bogott" <abogott@xxxxxxxxxxxxx> wrote:
>  
> >   On 2/13/12 3:58 PM, Eric Windisch wrote:  
> > >  
> > >   
> > > I'm guessing that you're looking at this from a developer's perspective rather than a support and operations perspective. Developers will understand English, but the operations and especially the support team may not. Having native language log messages has the potential to significantly decrease support costs for users both domestic and abroad (where domestic users might outsource support).
> > >  
> > >  
> > >   
> > >  
> > The one thing I consistently use log messages for is googling.  If everyone in the world gets the same log message for a given error, that drastically increases the chances that I'll find that log message in a forum post someplace.  Doesn't localizing log messages fragment the world of support forums into a zillion language-specific shards?  (Full disclosure:  I speak English, so this argument may be an unconscious front for Yankee Imperialism.)
> >   
> >   
> >