Ticket #637 (new feature request)

Opened 6 years ago

Last modified 5 years ago

Enable site-specific localizations to basic components so that upgrading new component by pear doesn't run those over

Reported by: netblade Assigned to: bergie
Priority: minor Milestone: 8.09.10 Ragnaroek
Component: MidCOM core Version: 8.09 Ragnaroek
Keywords: Cc:

Description (Last modified by bergie)

If you change locales for some component by ais/l10n/ , it write's those changes to that components locale-folder. When someone upgrade that component, those changes are overrun and lost.

So, there should be 2 kinds of locale's. Those that come from the component and no-one can't change those from the site. And as an addition to those, site specific translations, that are not overrun by upgrading the component. If I make changes to some locale-string that comes from the component locale-folder, we save that change somewhere else than to that locale-folder.

Change History

12/12/08 12:28:48 changed by bergie

  • type changed from defect to feature request.
  • milestone changed from 8.09.3 Ragnaroek to 8.09.4 Ragnaroek.

12/12/08 12:28:59 changed by bergie

  • summary changed from Enable site-spesific localizations to basic components so that upgrading new component by pear doesn't run those over to Enable site-specific localizations to basic components so that upgrading new component by pear doesn't run those over.

02/17/09 20:20:21 changed by bergie

  • description changed.
  • milestone changed from 8.09.4 Ragnaroek to 8.09.5 Ragnaroek.

04/29/09 15:52:55 changed by bergie

  • milestone changed from 8.09.5 Ragnaroek to 8.09.6 Ragnaroek.

10/20/09 13:39:28 changed by piotras

  • milestone changed from 8.09.6 Ragnaroek to 8.09.7 Ragnaroek.