How to export translations of custom Views?

On a clean Umami install (which contains english and spanish out of the box) I go to /admin/config/development/configuration/full/export and then export the config it contains a 'es' folder that contains all the spanish config, including the Views.

Not sure what you are looking for, that config should just be exported along with the other config.

I translated several custom views from English to German in a development system. But I cannot find a way to export my dev translations to import them into the production system. That means my hard translation work get lost.

How can I transfer the translations of my custom views (not the module) to other systems? I simply cannot find the translated strings in any export I tried out.

my custom views (not the module)

What does that mean? Are they Views from the Views module or are they database view tables?

You click the "Add view" button and create your own by hand - and save it later in the database. Than you translate the stuff... and now I need the translation on a different system and how I can export these translations?

To my knowledge there is no way in core for exporting translations

That sounds really bad… data loss is really al problem and redoing the translation is waste of time.

Should we convert the case to a feature request now?

May be something that needs sign off if it’s to be included in core or should be a contrib feature

Example https://www.drupal.org/project/translate_export →

Thanks for sharing. I take a look if they fill the gap and export the custom views only.

Sorry, I still don't understand the problem. Views translations are like any other config translation, and they get exported along with all the other config when you export it. This works fine.

Are you exporting config one thing at a time or something like that when you move things from dev to prod? And not the whole config folder at once? I've never done that (and that sounds like a lot of work), but in that case you might have to export the translations separately since they are their own config object I think.

The examples @smustgraves provides are for interface translation and not config translation, so I don't think those would apply here, but if they are I would recommend using https://www.drupal.org/project/potx → just to make the list complete

I just checked and if you are moving things one by one via /admin/config/development/configuration/single/export, you are correct, I don't see an export feature for translations there. But that goes for all entities, that has nothing to do with Views specifically.

And the workaround would be to export the full config and manually grab the translation files from there.

@marc.bau: It would be great if you outlined in detail:

• The steps you take (which pages, which buttons, etc.)
• The expected outcome
• What happened
• How you like it to work

I have just worked with translations, and had a hard time understanding how it all ties together -- like "There's interface translation AND configuration translation, working in each their own way, huh?".

There are many different methods, so understandably, we all have a hard time understanding your challenge, unless you supply the details. Do you want to use a .po file, do you use Drush, the interface, or something else ... If you are moving .yml files individually, if yes, from which folders, etc.

Also, what exactly do you mean with a "custom view"? Like, if it's just clicking on the button and creating a View, I wouldn't consider that "custom", that's just a View, in my opinion. When you use the word "custom", we start thinking that perhaps you coded it in some strange way, but maybe you didn't? In other words, if you created the View with the regular method, you can drop the word "custom".