Closed Zorono closed 2 years ago
Please try the same action now, I've made a little corrections in .gitattributes, but it should be tested.
Please try the same action now, I've made a little corrections in .gitattributes, but it should be tested.
unfortunately that didn't work too
I guess i have nothing to do except re-cloning it
Yeah, try this
So, did it help?
So, did it help?
yea thanks dude, re-cloning seemed to be the only available fix for this :(
That's interesting because I still don't understand whether my last commit solved that or the previous .gitattributes was also correct and you had problems because of older repo settings.
I still don't understand whether my last commit solved that or the previous .gitattributes was also correct and you had problems because of older repo settings.
in fact, the problem doesn't relate to file attributes but I still don't understand what is causing it or how to fix it without re-cloning... but it could be my Operating System's locale's fault... which is by the way a very low probability since updating my local repo was as easy as expected last time...
I changed .gitattributes in this specific case to correct repo encoding in which there is a problem. Now there is no forcing to use cp1251 for the whole repo so now it seems it's not more needed to convert those .lang files which wasn't in utf-8 by default.
please what do you suggest... (i tried searching about this many times and tried a lot of methods which didn't work)