In order to make interface text user friendlier we created a Custom Language labeled as en-intra. Strings that were too complicated or too much Drupal jargon were rephrased in en-intra and it was set as the default language and the original en was disabled. Now the users see our interface language and if there are questions related to explanation text, we can adapt just any interface text to our needs. We thought this was indeed a cool thing in Drupal, but......

I cannot tell with what upgrade (of core supposedly) it was, but something went wrong. When do a search, our custom text appears as the original language and the default Drupal English has disappeared. At some point "en" got overwritten by "en-intra". In some update somebody must have forgotten that the original language is not always activated, nor the default.

I am wondering now how to fix this? I would not like to loose our customisation work but it is now totally mixed up with the Original Text. When I do a search on a string that I know only appears in the custom text, then it turns up in the original text and all appear as untranslated!

I'm thinking of:

  • exporting the en-intra, which will contain the original language strings mixed up with my modifications.
  • restore the original text
  • delete en-intra
  • creating en-intra
  • exporting en-intra
  • usding diff to compare the two exports to recover my tranlations
  • creating manually a .po file with my translations
  • importing the resulting .po file in en-intra

The question is how to restore the original text? Anybody knows a better solution as my suggested procedure?

Comments

ñull’s picture

Title: Custom language became (swapped) with Original Language » Foreign and English original language swapped
Version: 6.20 » 7.9
Priority: Normal » Major

Nobody took this bug serious, by the looks of this large list of reactions I got. :-(

Now it happened again. Problem was never fixed in D6 and got carried to D7? I have this D7 with Commerce and all the field translations are swapped (see screenshot).

Example of foreign original swap

Spanish became the original language, but the field labels are still in English, cannot be edited because they are locked (they have become original now!). Translating the English to the foreign language is useless, because it will never appear when switched to the foreign language. I cannot translate labels any more.

As far as I know, English should always be the original language, nomatter how Drupal was installed or what modules are installed.

gábor hojtsy’s picture

Project: Drupal core » Internationalization
Version: 7.9 » 7.x-1.x-dev
Component: language system » Strings
Category: bug » support

English is only ever the default language for the built-in software interface text. For user provided data, the site default language is assumed to be the language you enter data in. Ie. if you site is set to be Spanish, what other language would you specify your site name in?

Looks like you changed your default language and was not aware of the consequences.

In any case, this functionality is provided by the i18n module, so moving to the right queue.

ñull’s picture

Status: Active » Closed (fixed)

You are right. Changing the default language back to English allows you translate "normally". It is all a bit confusing and not very user friendly.