Firstly, don’t extract your own strings. There are various ways to create custom translations…
If you add a new language file, then by default this will create a new PO file from woocommerce.pot which will have ~12k strings, and be 0% translated. Presumably this is what your first screenshot is showing, but this isn’t an error. Any custom translations you add into this file will be merged with the original system file when they’re displayed on your site.
I don’t know what your second screenshot is showing, but it’s important to understand that the 12k strings you see at that link include script translations which GlotPress deliberately removes from the PO file that WordPress installs. That’s why your system PO shows 9k strings. You can’t edit the additional 3k strings directly via this PO (in fact you shouldn’t edit it at all), so the count is technically correct. But if you copy this and select Merge strings from related JSON files this should give you the full 12k, and also copy the translations if you want that duplication.
Both of these methods will let you override the GlotPress translations. Which method you use depends on exactly what you’re trying to achieve, and also how reliable the installed PO file is vs the bundled POT file.
Feel free to elaborate on exactly you’re trying to achieve and what isn’t working for you.
Hi @timwhitlock
thank you very much for your response. It is more clear now for me. Actually what I wanted to do was to use complete the current woocommerce ES_CL translation file and just make the change to some words.
Best regards