Daniel Rall wrote: >Santiago Gala <[EMAIL PROTECTED]> writes: > > > >>with my standard settings: >> >> >> Ejemplo de Cabecera de Request >> >>Host hisitech.com:8080 >>Accept >>text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 >>User-Agent Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9+) >>Gecko/20020425 >>Keep-Alive 300 >>Accept-Language es-es, en-us;q=0.80, es;q=0.60, en;q=0.40, ja;q=0.20 >>Accept-Encoding gzip, deflate, compress;q=0.9 >>Accept-Charset ISO-8859-1, utf-8;q=0.66, *;q=0.66 >>Referer http://hisitech.com:8080/examples/servlets/index.html >>Connection keep-alive >> >> > >I taught Eyebrowse to behave more politely to our international >friends and have installed the updates on nagoya. > >
The Profiler in Jetspeed picks up the first supported locale in the accepted list, as your current code seems to do. This is an awfully complex problem. Yesterday I was seeing lots of $i18n.title strings. Today I think I see it consistenty in english. The best approach would be to populate the $i18n tool first with the "preferred" locale, and then fill only the missing entries with other available locales (even more ideally, in the order chosen by the user), or the default one. This is very robust, since typically as programs evolve you don't have all strings translated at the same time. I see it every day with gnome apps, where I see mixtures of spanish an english strings that change as I get new versions. But still is friendlier that returning english when i.e., default is english, I specified spanish/french, and available translations are french/english. Very tricky problem, as all i18n related ones. BTW, thanks for your effort. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
