Joplin seriously need an overhaul for local translations

Tried to translate joplin, its a hazzle

Ok, so i cant upload into the localization directory on github, latest updates on my language is 7 months ago acroding to that directory there. Youre making contributing with translations extremely difficult, joplin crew, this will halt your development bigtime. Look at collabora, i did 70 lines of translation there in a breeze (just a few minutes) a few minutes ago. Now i have a .po file with atleast a hour or two with translations i dont know what to do with, i guess you dont want it since i cant send it to joplin. Seriously, joplin is a wonderful piece of software, please do something about this, people want to contribute but if you dont change your way to let people contribute with translations i cant see joplin moving forward much in foreign languages.

Welcome @Saint.77 to the forum! Just for those who read for entertainment, to which language did you contribute a translation?

That would be in norwegian. I went on and added about 200 lines in total of translation to collabora after this post... thats about 1/7 of what remains i believe... If you want to see how to get your software translated, look at collabora... if anyone here wants to contribute, head over to collabora. its libreoffice engine but libreoffice looks like a 1990s program, collabora is pretty and functional and a huge much needed facelift to libreoffice, its the office suite i hope pulls ahead (beside onlyoffice, which also lacks translation)... and then we have Joplin... It has the software but its offer of translation is practically non-existent or so poor you wont get me to do more on it, what takes 10 minutes on collabora takes 4-5 times more sitting in poedit that wants to charge you money for using google translate, while i can just shoot trough with google translate for free in my browser translating for collabora

As far as I understand you are supposed to open a pull request to update that po file. If you do not know how to do that, share your po file, maybe here or maybe in a github issue, and hopefully a developer will do it for you.

Example of this happening: Contribute to translation - .po file cannot be opened - #4 by tessus