[rt-users] How is language determined in RT?

[Christian Gilmore]

Jesse,

I'm sending in a header that looks like:

en-us, ja;q=0.8

Instead of getting en back (as matching the en-us tag prefix), I'm getting 
ja. The specification isn't written in clearly understandable way, but I 
believe the key element is the following quoted sentence with my 
interpretations in brackets from RFC 2616, section 14.4:

A language-range matches a language-tag if it exactly equals the tag [ie, 
en-us = en-us or ja = ja], or if it exactly equals a prefix of the tag 
[ie, en = en-us] such that the first tag character following the prefix is 
"-".

FWIW, I put the I18N::AcceptLanguage module on CPAN a long while ago that 
did this determination properly per my understanding of the RFC.

Thanks,
Christian

----------------------
Christian Gilmore
Technology Leader
GeT Support Application Development
IBM Software Group





Jesse Vincent <jesse at bestpractical.com>
Sent by: rt-users-admin at lists.fsck.com
08/05/03 01:38 PM

 
        To:     Christian Gilmore/Austin/IBM at IBMUS
        cc:     rt-users at lists.fsck.com
        Subject:        Re: [rt-users] How is language determined in RT?






On Tue, Aug 05, 2003 at 01:34:47PM -0500, Christian Gilmore wrote:
> Where within/underneath RT is the language to send to the client browser 

> determined? I don't believe it is properly implementing the RFC.

It actually hands off that determination to Locale::Maketext, which
processes the browser's Accpet-language: header.  What behaviour are you
seeing that's suspect?

> Thanks,
> Christian
> 
> ----------------------
> Christian Gilmore
> Technology Leader
> GeT Support Application Development
> IBM Software Group

-- 
http://www.bestpractical.com/rt  -- Trouble Ticketing. Free.
_______________________________________________
rt-users mailing list
rt-users at lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20030805/47f19c1f/attachment.htm>