Closed (won't fix)
Project:
Localization update
Version:
7.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
13 Jan 2011 at 22:58 UTC
Updated:
3 Aug 2015 at 06:31 UTC
Jump to comment: Most recent
Comments
Comment #1
gábor hojtsyAgreed.
Comment #2
gábor hojtsyThere is in fact a po-reimporter module that apparently supported this for .po files shipping with modules. Although it does not do much else that l10n_update does, so I've submitted a request for that to be deprecated in favor of l10n_update (#1133198: Phase out this module in favor of l10n_update?). Introducing per-module updates would be great.
Comment #3
berkas1 commentedWhat is the status? I realy look forward to this feature:)
Comment #4
MathFreak.be commentedsubscribing
Comment #5
dgastudio commentedany update on this?
Comment #6
liquidcms commentedyes, would be very nice to pick and choose. one module in particular, the i10n_client module would be nice to not have translation installed
Comment #7
MHLut commented+1
Comment #8
chaugi commented+ subscribe. For e.g. you want to make sure that only certain parts for website/admin site are stranslated not all of them, as I am used that Views, Panels modules are in English. Plus it is easier to find contentent for translation when there are no translations imported.
Comment #9
sutharsan commentedComment #10
sutharsan commentedI'd like to keep the common tasks of this module simple. Adding module selection will make the 7.x-2.x user interface significantly more complex. Therefore I will not accept this feature request. I do recognise the requirement of translation per module, and propose to use drush instead. Please collaborate on #1982580: drush command l10n-update - specify modules to update translations to get that functionality added.
Comment #11
sutharsan commentedComment #12
kopeboyCould you please reconsider this?
This would be very very useful.
Example use case:
I just need the translations for the Date module, I don't want to load my database (and slow down my site) with translations for 150 modules (and very big ones like Commerce) just because I need the months and weekdays in my language.
Everything else is translated manually because I want the backend interface to stay in english for consistency.
Comment #13
sutharsan commentedWhat about using Drush to update a single module translation? Or you can update the translation manually.
I still don't see enough arguments to reconsider my point of view.