Good point. Actually, since we release new client software much more often than most projects update their server software, maybe we're better off keeping the current scheme -- David
On 16-Jul-2010 12:32 PM, Michael Tughan wrote: > That limits users from making their own translations of BOINC and testing > them beforehand without having to set up their own server though. It also > means that if an error is found in the translation, the user has to wait for > all his projects to update their server code before it is fixed. As we've in > security fixes, that can take a while for some projects. > > Michael Tughan > > On 2010-07-16, at 2:49 PM, David Anderson<[email protected]> wrote: > >> Yes, server-side translation has advantages; eventually we'll probably >> switch to doing it that way. -- David >> >> On 16-Jul-2010 4:17 AM, [email protected] wrote: >>> Would it make sense to have the client send the server a language code >>> so that the server could send the translated strings to the client? >>> This would mean that the client would not have to know about new strings >>> that a server version added. >> _______________________________________________ boinc_dev mailing list >> [email protected] >> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, >> visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
