Inhalte aufrufen

Profilbild

Localization vs. resources from plugins

export gmc google google merchant center

1 Antwort zu diesem Thema

#1 Ondrej Mackovic

Ondrej Mackovic

    Newbie

  • Members
  • 7 Beiträge

Geschrieben: 16 August 2017 - 13:05

Hello,

when you localize resources from a plugin and then get newer plugin version/reinstall plugin/click "refresh plugin resources" button guess what happens? Your translated resources are replaced with english and your work is lost. Wouldn't it be better to keep translated resources untouched and just insert newly added strings?

 

By the way. Importing translated resources (XML file) works very weirdly. It only replaces "some" resources with translations - no, its not just omiting the "dbo.LocaleStringResource.IsTouched" column. It omits much more strings. Thousands. I had to write my own tool to import translated strings back.


  • RidgeOi gefällt das

#2 Murat Cakir

Murat Cakir

    SmartStore AG

  • Administrators
  • 1015 Beiträge

Geschrieben: 16 August 2017 - 17:13

 

 

Wouldn't it be better to keep translated resources untouched and just insert newly added strings?

 

Actually this is already working this way. But you shouldn't translate an existing resource file, because your changes will be overwritten with each upgrade.

 

Instead, create a new file with file name pattern resources-[lang].xml, where [lang] stands for the region ISO code or just the neutral language code. Also ensure that a corresponding language entity has been created for this language in the backend.


Murat Cakir
SmartStore AG




Auf dieses Thema antworten



  

Auch markiert mit einem oder mehrerer dieser Schlüsselwörter: export, gmc, google, google merchant center