Code

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#14739 closed (fixed)

Move contrib app translations out of core

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

Description

In this way we could have, in a sense, more useful/realistic translation coverage stats. If we have N localflavors, every translator needs to take care of translating city, zone, district, tax IDs, etc. of these N countries to his/her own language. I suspect it is rarely used, if at all.

As a translator, I'd like to know that I can get a Django core translation to/near 100% even if I don't get to or don't want to translate all literal of some recently added localflavor and I'm ok with the original strings added by the localflavor author being used instead. It would be useful to know that if I have 20% of missing translation on my 'main' django.pofile, they aren't localflavor translations but rather core, forms, or admin ones.

One data point: Currently localflavor strings represent 48% of the French django.po, for example.

Attachments (0)

Change History (6)

comment:1 Changed 3 years ago by claudep

  • Cc claudep added
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

comment:2 Changed 3 years ago by jezdez

  • milestone set to 1.3
  • Owner changed from nobody to jezdez
  • Status changed from new to assigned
  • Summary changed from Segregate contrib.localflavor translations to their ownPO file/gettext domain? to Move contrib app translations out of core
  • Triage Stage changed from Unreviewed to Accepted

Accepting after having talked to Russ about this.

comment:3 Changed 3 years ago by jezdez

  • Has patch set

Latest working version can be found here: https://github.com/jezdez/django/compare/master...move-translations (not attached as a patch due to size)

comment:4 Changed 3 years ago by jezdez

Updated work in https://github.com/jezdez/django/compare/master...move-translations-split that splits the changes nicely per app.

comment:5 Changed 3 years ago by jezdez

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

Fixed in [15258-15276].

comment:6 Changed 3 years ago by jacob

  • milestone 1.3 deleted

Milestone 1.3 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.