Changes between Initial Version and Version 1 of Ticket #11915


Ignore:
Timestamp:
02/01/2010 06:38:32 PM (5 years ago)
Author:
ramiro
Comment:

This takes us to the following possible scenario: What if the LANGUAGES setting has, in addition to 'pt-br', 'pt-cv' (Portuguese as spoken in Cape Verde)? How and why should Django choose 'pt-br' in preference to 'pt-cv' (or vice versa) if a translation to 'pt' is missing?

(The fact I'm using pt, pt-br and pt-cv in this example is just incidental, the real issue is what matters)

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11915

    • Property Patch needs improvement unset
    • Property Needs tests unset
    • Property Version changed from 1.0 to SVN
    • Property Needs documentation unset
    • Property Triage Stage changed from Unreviewed to Design decision needed
  • Ticket #11915 – Description

    initial v1  
    22
    33For example, if a user's browser sends a header
     4{{{
    45Accept-Language: pt
    5 
     6}}}
    67And my site has
     8{{{
    79LANGUAGES = (
    810#...
     
    1012#...
    1113)
    12 
     14}}}
    1315Then the pt_BR locale files I have should be used. (RFC 2616: 'A language-range matches a language-tag if it exactly equals the tag, or if it exactly equals a prefix of the tag such that the first tag character following the prefix is "-".')
    1416
Back to Top