translate
Issues with pootle localization files
I translated the new/changed strings of pootle it locale with Poedit, but i keep seeing strings in the english format. I cleared cache (i even used CTRL+Shift+R and CTRL+F5) and used another browser.
Image 1: still seeing "#1 contributor in Italian..." and "JohnnyKing94's language teams"
Image 2: even when you click the share link
Image 3: I translated the word 'task' in italian, i keep seeing it in english
Image 4/5/6: I updated the content with another one, still seeing the old one (referring to the string Find project by name, code etc)
If I find other issues related to the localization, i post them here ;)
To Image 3: The translation string contains the word "task":
https://pootle.locamotion.org/it/translate/#search=task&sfields=source,target&unit=1803464&offset=0
@milupo as i said in the caption, i locally translated it
I translated the word 'task' in italian, i keep seeing it in english
@JohnnyKing94 did you compile the translations? In other words could you maybe explain in more detail what you did to get this translated and how you actually compiled and deployed. If you just update a PO file, then no you haven't done what is needed.
@dwaynebailey I used Poedit, i opened the files, translated the needed strings, saved them and renamed the .mo files with the proper name in order to put them in the LC_MESSAGES folder... most of the strings translated are working, the ones i described up here are not...
Sorry if I took the procedure for granted... now it's been 2 years i'm using Poedit for local translations... 😄
@JohnnyKing94 no that helps. Simple answer, if any of these strings are actually in the PO file and its compiled correctly and its actually localising then the issue is cache of some sort or your files aren't in the right place or similar.
If the string is partial, well its getting the localisation from somewhere and clearly no where you expect.
If its fully in EN and not in the file, then it isn't translatable.
I'd try remove the cache of the rendered pages as a first step using pootle flush_cache
@JohnnyKing94 as a simple test for yourself that has nothing to do with the actual translation. Take a simple highly visible string and make a small change. If that does not appear then all your problems are centred around cache, wrong place for your files, etc. Its not a localisation issue really but one of getting refreshed localisation on your install.
I just run pootle flush_cache -all after i stopped the rqworker and i got this
Flushing cache...
RQ data removed.
Max unit revision restored.
All default Django cache data removed.
All lru cache data removed.
Still seeing the described issue with any browsers (cleared cache also)... My files are in the right location, otherwise the other strings i translated would not appear on Pootle
/locale/it/pootle.po
/locale/it/pootle_js.po
/locale/it/LC_MESSAGES/django.mo
/locale/it/LC_MESSAGES/djangojs.mo
Apparently it's only an issue with those strings... the other i translated work perfectly...
@JohnnyKing94 really no idea. If you say that some of your strings are actually now translated (that wasn't clear in the original report) and some not then I can't tell why some worked and some not.
A quick check msgunfmt django.mo and check that your string are in fact correctly in the file.
There is no magic: Pootle via Django, reads the MO file and replaces those strings. It won't be able to randomly decide to get 50%. But the fact that it's only your strings that it isn't getting, points to cache or file location.
Please try on another locale and with a locale switcher just to elminate the likely problems of cache and browsers interfering.
@dwaynebailey I just made a quick check with msgunfmt django.mo and msgunfmt djangojs.mo, and the strings concerned are actually translated and they exist in the file.
These are my files: https://www.dropbox.com/s/7tovid2khw7x1hs/it-pootle.7z?dl=0
Basically they're perfectly compiled... you can also upload them on your official repository and pootle plaftorm, i made several changes and fixed many mistakes... 92 strings need to be translated for pootle.po, I hoped to give them when I fully completed all the translations, but you can take them anyway.
Hope it helps to understand the issue...
@JohnnyKing94 doesn't help me to understand the issue of why you can't see them. I'm still concerned that you're pootle instance is not actually using the files where you made changes or that something has cached these.
Best way to submit translations is to make a PR or translate on pootle.locamotion.org
@dwaynebailey I'm open to any tests to make in order to resolve this issue... Anyway I also shared link just to let you see that these strings are actually there and if you wanted to make tests with them by changing your browser language... in this way you'll notice the same problem...
@JohnnyKing94 Did any of the strings you translated in this way update? Is the date-field newer than what is on the platform? Could you paste the strings of the file that contain the words in question?
No response, closing and hoping it works out in the revamp of the platform.
Sorry busy week @comradekingu Did any of the strings you translated in this way update? Any of the strings (as stated in the images) didn't update... other strings not in this issue (which I translated) were shown correctly on the platform...
Is the date-field newer than what is on the platform? I don't know what you mean
Could you paste the strings of the file that contain the words in question? I link the strings using your platform: https://pootle.locamotion.org/it/pootle/translate/pootle.po#unit=1843222 https://pootle.locamotion.org/it/pootle/translate/pootle.po#unit=1843232 https://pootle.locamotion.org/it/pootle/translate/pootle_js.po#unit=1803464 https://pootle.locamotion.org/it/pootle/translate/pootle_js.po#unit=1710425 https://pootle.locamotion.org/it/pootle/translate/pootle_js.po#unit=1710323 https://pootle.locamotion.org/it/pootle/translate/pootle_js.po#unit=1710415
Hope it will help...