We need PO editor

[dodyg]

Right now it is really cumbersome to deal with string translation because you have to deal with source code level to deploy and enrich the localization key/string.

It will make life so much easier if admin/editor can just add more translation key/string from the admin section and use them immediately at the template.

[nogginbox]

Orchard are using Crowdin to manage the localisations. I've been meaning to check it out for another project, but not got round to it yet. You might want to look into this or see if there are other po editor tools on the market.

[dodyg]

That's not the problem though. The problem lies in maintaining multi lingual templates. As your multi-lingual page grows, you will need more translation data to be available. Right now you have to deploy to do so or use a bunch of if statement in your liquid template.

[hishamco]

It will make life so much easier if admin/editor can just add more translation key/string from the admin section and use them immediately at the template.

@dodyg the localization load the localizable strings when the Startup of the localization module runs, so adding them at runtime needs restart the app. I think you could add your localization strings directly in the PO file, so when the app fires all of your resources will be available

[hishamco]

Moving translations to table will change the resources source, I already did somthing similar in the past with EFLocalizer, we planned to do something similar but for those localization strings that are dynamic such as content types, content fields .. etc

[dodyg]

@hishamco is there any mechanism to reset cached localization string so there is no need to restart the system? I will be working on a PO editor that touch *.po files directly. The question is whether there is a way to let ASP.NET Core knows that these files have been changed and it needs to reload the PO files.

Can we have LocalizationManager to support something like Reset or Reload method? https://github.com/OrchardCMS/OrchardCore/blob/main/src/OrchardCore/OrchardCore.Localization.Core/LocalizationManager.cs

[hishamco]

Luckly this working fine with me in JSON Localizer becuase I'm using configuration APIs. What you want could be done using by invalidate the cache which is not supported in the current implementation AFAIK

FYI recently I was working on Data Localization in OCC I faced similar issue, where I need to refesh the cache, simply I remove the cached entries by the key as shown here

We may need a method to purge the cache as provider level, @sebastienros your though?

[dodyg]

@hishamco what is a JSON Localizer? Is this a new library?

[hishamco]

It's a project that I created long time ago, you can find it here I also did an OC implementation in Orchard Core Contrib repo