Code

Opened 4 years ago

Closed 4 years ago

Last modified 3 years ago

#12592 closed (wontfix)

language code for brazilian portuguese should be case insensitive.

Reported by: italomaia Owned by: nobody
Component: Internationalization Version: master
Severity: Keywords: pycamp2010
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

In i18nguy, as advised in settings.py it says one should use pt-BR, but django-settings only understand pt-br. Maybe i18nguy should update, or
django settings should advise another website.

Attachments (0)

Change History (6)

comment:1 Changed 4 years ago by jezdez

  • milestone set to 1.2
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted
  • Version changed from 1.1 to SVN

To clarify, this is about the global_settings.py having a comment linking to http://www.i18nguy.com/unicode/language-identifiers.html.

comment:2 Changed 4 years ago by i18nguy

  • Component changed from Uncategorized to Internationalization
  • Summary changed from i18nguy language code for brazilian portuguese is wrong to language code for brazilian portuguese should be case insensitive.

The recommendation of pt-BR is correct. Standards for language identifiers recommend lowercase for language, uppercase for region or country code as prefered, but the identifier should be case-insensitive.

tex texin (i18nguy.com)

comment:3 Changed 4 years ago by jjconti

I tried:

LANGUAGE_CODE = 'pt-BR'

in my settings.py file and when browsing the admin site all in written in Portuguese.

comment:4 Changed 4 years ago by jjconti

I ran all the tests with a settings file having

LANGUAGE_CODE = 'es-AR'

And all ran ok.

I also ran them with

LANGUAGE_CODE = 'es-AR'
USE_I18N = True

And all ran ok too.

comment:5 Changed 4 years ago by jjconti

  • Keywords pycamp2010 added
  • Resolution set to wontfix
  • Status changed from new to closed

comment:6 Changed 3 years ago by jacob

  • milestone 1.2 deleted

Milestone 1.2 deleted

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.