I'd like to see two small but important features from auto locale import module. The most important is the "automatic import" and the second the cleanup feature. I'd like this automatic import tab very much and it saved me much time. Now if we have a DEV language package update or a translation team releases a new major version i must click every .po file an upload this file into my site :-(((. In past it was only one big file... no big thing todo, but know we have 40 files...

This is really a very heavy job! I'm sure more and more people will complain about this not in core after some weeks!

Comments

keith.smith’s picture

keith.smith commented
Title: Automatically whipe translations and re-import language files » Automatically wipe translations and re-import language files
gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

I intend to phase out autolocale and built this into l10n_client instead. This was not implemented in core to protect people changing translations to wipe their own work with a click of a button. It is too late to get something like this into Drupal 6 which is days away from being released.

hass’s picture

hass commented

But how should people update their translations quickly? For e.g. you apply a version hu-1.0 to your box and then on a release of hu-1.1 or hu-2.0 - today i'm made to upload 40 files by hand!? I know it is very late and i'm not happy i haven't been able to see this much earlier, but it is something you might start to think about if you are going to translate and must re-import a dev versions or CVS versions of translations every day for testing... i feel totally stressed!

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

hass: don't be stressed. I am in the hopes that the contrib modules available for handling translations grow even stronger with Drupal 6, and I explained already above that this functionality will be provided by contrib.

hass’s picture

hass commented

Couldn't we keep the truncate table outside of this issue and only add an re-import feature!? If we overwrite all or add only non existing strings could be a user choice, like today. It's only *one* checkbox or re-import button we need on the normal import page...

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Fixed

hass, it is not only one checkbox, users need to be explained what happens there, they don't need to upload files, etc. I just released a 6.x-1.1 version of l10n_client which includes such reimport functionality. This will be suggested in the 6.0 release announcement for upgraders.

hass’s picture

hass commented

THX, but not so good that http://drupal.org/node/217884 hasn't been fixed before this release :-(

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.