Re: Damned Lies Gateway error on sending gnome-commander

2021-09-14 Thread Enrico via gnome-i18n
Greetings to all Thank you Philipp, I will do a next try ASAP based on the new translatable strings available at the project, so I can observe the behavior 😉 Have a nice week Be Well and Stay Safe, Enrico. ‐ Em sex., 10 de set. de 2021 11:37, Philipp Kiemle escreveu: > ...forgot

Add Apostrophe to damned-lies

2021-09-14 Thread Manuel via gnome-i18n
Hi, i18 team! Apostrophe was moved recently to the World repo, and it'd be nice to have it in damned lies as well. The app is already translated by volunteers on poeditor, but I'm not 100% sure on the quality of the strings for other languages than the ones I speak https://gitlab.gnome.org/World/

Re: DL Error : File not UTF8

2021-09-14 Thread Matej Urban via gnome-i18n
Hello, im getting a similar error, but different encoding ... »'ascii' codec can't encode character '\u010d' in position 11: ordinal not in range(128)«. Is this me or the system? Hopefully it is the system, because I can not find the problem ;). Thank you. Matej On Sat, Jul 24, 2021 at 3:47 PM Ra

Re: DL Error : File not UTF8

2021-09-14 Thread Philipp Kiemle via gnome-i18n
Hello, We at the German team have a similar error message when trying to commit a translation: 'ascii' codec can't encode character '\xfc' in position 7: ordinal not in range(128) See this translation: https://l10n.gnome.org/vertimus/gucharmap/master/po/de/ Philipp Am Di., 14. Sept. 2021 um 21:3

Thanks

2021-09-14 Thread Georges Basile Stavracas Neto via gnome-i18n
This cycle was a bumpy ride for Settings in particular, so I just wanted to let everyone in the i18n team that I appreciate your patience and your hard work on acting quickly to translate these changes. Cheers for the impending GNOME release. Best regards, Georges

Re: DL Error : File not UTF8

2021-09-14 Thread Rafael Fontenelle
Hello Matej and Phillip, The culprit for this issue should have been fixed already. Personally, I don't see this issue anymore in my translation actions. I suggest that you try re-uploading the PO file that is presenting this encoding error in order to work around the encoding issue already fixed