Code

Opened 4 years ago

Closed 4 years ago

Last modified 3 years ago

#12673 closed (fixed)

Start requiring GNU gettext 0.15 or newer

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

Description

This way we will be able to use translation contexts (see #10004, django-i18n thread) in a future release.

It will also allow us to drop some workarounds for bugs in old gettext versions (#9212, r9155) and would help with #9753.

GNU gettext 0.15 was released on July 2006 and current version is 0.17 (released on Nov. 2007). All sane OS platforms already comply with this requirement, there are also binaries for Windows available.

Attachments (1)

12673-require-getetx-015.diff (3.2 KB) - added by ramiro 4 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 Changed 4 years ago by ramiro

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Summary changed from Start requiron GNU getext 0.15 or newer to Start requiring GNU gettext 0.15 or newer

Changed 4 years ago by ramiro

comment:2 Changed 4 years ago by jezdez

  • Owner changed from nobody to jezdez
  • Status changed from new to assigned
  • Triage Stage changed from Unreviewed to Accepted

comment:3 Changed 4 years ago by lukeplant

FWIW, webfaction.com, a favorite Django web host with some, is still using gettext 0.14. It uses "Red Hat Enterprise Linux ES release 4 (Nahant Update 8)". Web hosts are often not "sane" OSes.

comment:4 Changed 4 years ago by anonymous

In the case of Webfaction (and other hosting platforms?): We don't need GNU gettext at runtime because we use Python's gettext module for that. It is expected that developers extract translatable literals to .po files, translates and converts them to .mo in their local own workstation before deploying it to the hosting system and hopefully the workstation they use for Django development are running newer environments.

Otherwise, if we want to support developers using workstations running pristine RHES 4 until its end of life, and according to:

we will be stuck with gettext 1.4 until May 2012.

Jannis Leidel also points via IRC that, for example, we are already dropping support for RHES 4 default Python (2.3).

comment:5 Changed 4 years ago by jezdez

Indeed, it's not common to create/update translation files on an already deployed Django project. I will make an announcement about the requirement bump on the django-i18n mailing list.

comment:6 Changed 4 years ago by jezdez

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [12296]) Fixed #12673 - Require a version of GNU gettext of 0.1.5 and above.

comment:7 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.