Cheers Graham, I realised this after a closer look last night - I don't think the "consistency" problem was as big as I first suspected, either. Patch should be up soon.
> -----Original Message----- > From: Graham Triggs [mailto:grahamtri...@gmail.com] > Sent: Friday, 29 January 2010 4:43 a.m. > To: Kim Shepherd > Cc: dspace-tech@lists.sourceforge.net; dspace- > de...@lists.sourceforge.net > Subject: Re: [Dspace-devel] JSPUI language detection - request for > comment > > BTW, 1 + 2 are technically the same thing... the EPerson's default > locale is stored in the current session when they log in - overriding > what is currently there. > > The UI selection will update the Locale in the current session - > overriding whatever is there currently (either a previous choice, or > the EPerson's default that has been inserted in the session). > > So priority of choosing a message to display is: > > 1. Session locale setting > 2. Browser default locale > 3. DSpace default locale > > G > > On 24 Jan 2010, at 20:07, Kim Shepherd wrote: > > > Hi all, > > > > JSPUI's i18n settings are currently a bit broken in trunk (future > 1.6). When an EPerson is logged in and has configured a language in > their profile which doesn't match the locale requested by their web > browser, they will end up seeing both languages used on some pages. > > This is basically due to inconsistent i18n key lookup methods used > throughout JSPUI. > > > > Now's a good time to go through and make everything consistent, so > right now the idea is to go back to the order that locales were applied > before 1.5: > > > > (1 is top priority, 5 is bottom, so the first successful match will > be selected) > > > > 1. UI selection (eg. manually selecting 'English' or 'German' from > the JSPUI or XMLUI frontend while browsing) > > 2. Eperson default locale (configured via Edit Profile in JSPUI or > XMLUI) > > 3. Browser default locale (first locale requested by end user's web > browser) > > 4. Dspace default locale (from dspace.cfg) > > > > Any feedback, concerns or ideas are welcomed: email replies > (preferably onlist) or JIRA comments. > > > > The full JIRA issue is here: http://jira.dspace.org/jira/browse/DS- > 418 > > > > If no objections are raised in the next few days, I'll just go ahead > with a patch based on the order given above. > > > > Cheers, > > > > Kim > > -- > > Kim Shepherd > > IRR Technical Specialist > > ITS Systems & Development > > The University of Waikato > > New Zealand > > > > DDI +64 7 838 4025 > > > > > > --------------------------------------------------------------------- > --------- > > Throughout its 18-year history, RSA Conference consistently attracts > the > > world's best and brightest in the field, creating opportunities for > Conference > > attendees to learn about information security's most important issues > through > > interactions with peers, luminaries and emerging and established > companies. > > http://p.sf.net/sfu/rsaconf-dev2dev > > _______________________________________________ > > Dspace-devel mailing list > > dspace-de...@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/dspace-devel ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
