Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

DM900/DM920 multiboot Translation issue

Updating the pot is fine. Just don't update the po files as this adds false translations and exceptions.
 
just so i understand... pot files are only used if you want to add a translation for a language that has not been translated before. correct?
 
Yes. They are like a po file that is empty in the destination language.

When po files are updated a translator needs to check them, because not only does the automation create fuzzy translations that are completely wrong (sometimes not even related), it also adds or removes syntax such as %s, leading to python crashes, such as "TypeError: not enough arguments for format string", or "TypeError: not all arguments converted during string formatting".
 
yes, i tried the update script... and it messed up the de.po. but somehow we should be able to update the po files to detect and remove unused translations and add new ones.
 
The update script deletes old entries and adds the new ones. The only problem is if it adds fuzzy to the new one. So, run the script, then diff the de.po and verify the changes are OK. When satisfied commit de.po. You can even make the script just do your po.

But the point is to only commit po files you have verified and test... rather than let an automated process add crashes to what was previously working.
 
The update script deletes old entries and adds the new ones. The only problem is if it adds fuzzy to the new one. So, run the script, then diff the de.po and verify the changes are OK. When satisfied commit de.po. You can even make the script just do your po.

But the point is to only commit po files you have verified and test... rather than let an automated process add crashes to what was previously working.
that is hard manual work... :-( i updated the po and get lots of fuzzy stuff.
 
i modified the updateallpo.sh script to not create fuzzy stuff. it also accepts a language as a parameter to just process one language.
it seems to create reasonable output. have a look, if you like.
 

Attachments

OpenViX Feeds Status

Back
Top