Code

Opened 5 years ago

Closed 5 years ago

#10965 closed (invalid)

Django should use an online translation system.

Reported by: stavros Owned by: nobody
Component: Translations Version: master
Severity: Keywords:
Cc: Triage Stage: Someday/Maybe
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

An online translation system would greatly lower the barrier of submitting translations. The current system of submitting SVN diffs is a bit cumbersome, and as a result the translations are not very complete.

Attachments (0)

Change History (5)

comment:1 Changed 5 years ago by telenieko

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Version changed from 1.0 to SVN

That's already been raised before. But it's not a priority atleast for current translators; Neither for core developers.

So unless you want to step in to develop such a tool, or set something up to show case I doubt it will go much further from being an open ticket susceptible of being closed 'wontfix' or 'works-for-me'.

comment:2 Changed 5 years ago by stavros

There already are such systems (e.g. http://transifex.org/, which is OSS and actually written on Django), and I don't think it would be that hard to set up... Its developers can frequently be found in #django, so one could ask there for any information...

comment:3 Changed 5 years ago by stavros

It might also be possible to just upload the .po files to Launchpad and let users translate them there, its translation interface is very easy and effective.

comment:4 Changed 5 years ago by Alex

  • Triage Stage changed from Unreviewed to Someday/Maybe

comment:5 Changed 5 years ago by mtredinnick

  • Resolution set to invalid
  • Status changed from new to closed

Integrating with an existing online system is certainly a possibility. A requirement for any choice is that it won't *require* people to use it, since a web browser is a horrible text editor, so we shouldn't force people down that path if they're already comfortable with their existing tools and editors. There would also need to be ways to have staging and validation of changes, because we don't want automatic commits of essentially rubbish translations going on.

I've looked at transifex in the past and it's a possibility, certainly, since it is possible to make it worth as an addition to existing processes. Launchpad's system certainly used to be much clunkier than transifex (I would consider the latter to be the leading candidate for something like this, by the way -- it's very well designed).

In any case, though, this isn't really a good ticket, since it's a huge item with no single resolution. Broad feature additions and process enhancements like this are more "TODO list" items than bug reports. Closing as invalid for that reason. After 1.1 is out, feel free to start a discussion on the django-i18n list about this, bearing in mind the above requirements and thinking about any extra things that might be appropriate. A good post that lays out some possibilities and the trade-offs (something that only says "Django should do this" isn't useful, as there's clearly multiple sides and compromises in anything like this) will be interesting to read and discuss. Right now isn't the right time, though, since it really can't get the full attention it needs with Django 1.1 coming up (it won't just be the translators themselves that are involved in the discussion and decisions).

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.