sync and save and loco forget the new strings

The reason is that you are editing a MO file, not a PO file.

MO files by design don’t include untranslated strings, so when you save and reload you won’t get any of those new strings back, because they’re not in the file. Try translating one before saving and you’ll see that count go up from 1,848 to 1,849.

I guess the author has not shipped a PO file with their MO file. Not very useful, if so. But after the save operation Loco Translate will have created a new PO. So Sync and Save, but then go back to the dashboard and find it again to edit the PO instead. I think that will solve your problem.

@timwhitlock yes the workaround to translate before save worked.

With 20+ .po files each 300Kb = 6000KB. 6 MB for only saving the untranslated strings is in my eyes to much. A 7 MB plugin raise to a 13 MB plugin. So we decide to remove all other files and keep only .mo and .pot

Maybe respect and support smaller plugin size by make the .mo only progress easier.

Maybe respect and support smaller plugin size by make the .mo only progress easier.

If you want to ship without PO files to save a few MB of disk space, that’s your call, but I won’t be encouraging translation workflows that go against how Gettext is designed.

I’m already allowing the editor to load MO files (when PO is absent), but this is more than I need to have done, because this is not what MO files are for.