RE: [gui-dev] MessagesBundle, russian translation

The website is now updated with the more recent translate page.  We'll
likely add something to automatically update it every night (as well as
synch the resource bundles of other languages).

The Russian translation has jumped from 1.10% translated to 91.74%
translated.  Thank you Eugene and Philippe!

Thanks,
 Sam

> -----Original Message-----
> From: [email protected] [mailto:gui-dev-
> [email protected]] On Behalf Of Philippe Verdy
> Sent: Sunday, December 05, 2004 1:05 PM
> To: [email protected]
> Subject: Re: [gui-dev] MessagesBundle, russian translation
> 
> Hi Evgenii,
> 
> My access to the LimeWire repository has been repaired. I have committed
> your translation.
> It is already available through the "Russian" link on the translate page.
> 
> (Note: the translate page at http://www.limewire.org/translate.shtml is
> generated from a script, which is run from time to time, but it has still
> not been refreshed. I can run this script, but I can't store its result on
> the website.)
> 
> Thanks,
> Philippe.
> 
> Note: don't change the "force local IP" option for now. The English option
> is correct because in fact it is related to the setting of the local
> end-point that your running host is listening. There's a separate setting
> for the public end-point accessible from the internet, in the
> Advanced->Firewall settings.
> 
> Trust the English message as it is, notably when the message is there
> since
> long. If it makes sense of modifying an English message, the LimeWire team
> will do it properly in time with its developments, but you can still
> discuss
> about these messages on the LimeWire development list or on support
> forums.
> 
> At the origin, the local IP could be set in addition to the local port.
> Now
> only thr local port needs to be set, but if you want to have a convenient
> translation, translate it as "force local address" (the address designates
> both the IP addres of a host interface and a demultiplexing port number on
> that interface, associated to the service running on that host and
> listening
> for this interface).
> 
> There has been several changes in these options (one of the most complex
> to
> manage in LimeWire), notably because now LimeWire can work more
> transparently through proxies, and NAT-routers. In most cases now, such
> advanced setting is rarely needed, and LimeWire prefers determining the
> correct settings itself, using tests through echoing hosts on the network,
> and autoadaptive behavior to change this setting on the fly (notably when
> the internet connection uses dynamic and temporarily assigned addresses,
> or
> when the user can't figure out precisely how its external gateway or
> router
> or FAI is configured, or has no easy and understandable way of figuring
> out
> himself those options).
> 
> 
> _______________________________________________
> gui-dev mailing list
> [email protected]
> http://www.limewire.org/mailman/listinfo/gui-dev

_______________________________________________
gui-dev mailing list
[email protected]
http://www.limewire.org/mailman/listinfo/gui-dev