Hi!

There are some strings that are not translated although they seem to be translated on localize.drupal.org.
For example, this string is translated in localize server, however, in admin/config/regional/translate/translate I can see:

Built-in interface "View products" es

So that string hasn't been fetched or it isn't being used. Any idea of what is going wrong? Not sure if this is a bug, if not, I'm sorry.

Thanks for your help!

Note: That string is used in ubercart. The translation file of that module was automatically updated. It says: Spanish: 7.x-3.2 (2012-Oct-13)

Comments

Diego Herranz’s picture

Diego Herranz commented

Still not working. No idea of what is going wrong.

I can translate locally the missing strings on admin/config/regional/translate/translate but I find it a waste of time to work on something that it's already done.

Any idea of what the problem is? Has anybody gone through this?

Thank you very much!

edvanleeuwen’s picture

edvanleeuwen
Primary language Dutch
Location Waalwijk
commented

Have you tried (in a test environment) the latest dev version?

sutharsan’s picture

sutharsan commented
Category: bug » support

@Diego Herranz: First check if the string is translated in the translation file (ubercart-7.x-3.2.es.po) that is stored in your translation directory. If this is the case your problem may be caused by the string being modified (saved at admin/config/regional/translate/translate) with an empty value. To check this follow these steps:

  1. make a backup of your database
  2. edit and save the translation file (ubercart-7.x-3.2.es.po) without making a change (this will update the last modified time stamp of the file).
  3. At admin/config/regional/translate/update: 'Refresh information' and then 'Update translations'.
  4. Check at admin/config/regional/translate/translate that the string is *not* translated.
  5. Repeat step 1
  6. Repeat step 2 but before 'Update translations' select 'Translation updates replace existing ones, new ones are added'
  7. Check at admin/config/regional/translate/translate that the string *is* translated.
  8. Restore the database backup

Let me know the results.

Diego Herranz’s picture

Diego Herranz commented

Sorry for answering late.

It seems that somehow some strings were not included in localize.drupal.org in the version 7.x-3.2.
I don't know where the problem came from but the strings seem to be back in 7.x-3.3 so I guess it's not a Localization update problem at all.

Thank you all for your answers!

sutharsan’s picture

sutharsan commented
Status: Active » Closed (works as designed)