I found some of my SVN revisions were gone after the transition!
And for now I can't commit codes to wowace...
This issue appear again. Is it related to the migration to Overwolf ?
In reply to Torhal:
Thanks Torhal. I was looking for the solution for quite a while, and finally got this answer.
Your archived file seems to be only available to you, at least I can download it.
I think I have encounter similar issue like you but probably with different causes.
For me, I use SVN mostly, and for libraries, I usually set external links which link to corresponding source URL of those lib. But I also use .pkgmeta and set externals there. I know this looks to be redundant, but anyway, that works fine in the past.
Recently (actually for a few months), some of the libs will get conflict files in the auto-packaged zip. For example, the files would be something like below:
So then I disable the external settings in .pkgmeta and only use the SVN's external links, though problem seems to be the same.
My guess is that during the packaging, curseforge also check-out the codes of the project, so when I use SVN externals, it will reflect to the one curseforge checked-out.
But then the problem could be, somehow curseforge will modify the files, line-breaking style, BOM, or something else, that made the files in modified stage. And then when the libraries have updates, conflicts will happen....
I think you need to do a trick.
Sometimes when you revise a phrase and you are sure your revision is correct and no need to have "need review" status, but you forgot to un-check the "need review" checkbox before clicking Save button. Then the trick is to temporary revise the translation such as adding one redundant space, save it, and change the translation again but this time don't forget to un-check the "need review".
This should do the thing.
The default behavior seems to get changed in these few days.
Although the KB says the default is set to blank, but it seems to be "ignore" previously.
It's fine for me if this is not "corrected" and if not defined, then default will be "blank". But this bring up another issue. See below.
2. Multiple lines but translation is empty.
Assumed we have below in English:
L[ [=[Hello World!]=] ] = [=[Hello World!]=]
Now, when handle-unlocalized is set to blank, the current result will be:
--Translation missing -- L[ [=[Hello World!]=] ] = ""
This will result in errors.
The default is "none" which is working fine previously. But today I found the namespace "ToC" I created was also exported.
If I am understanding correctly, "ToC" as a namespace is a subnamespace to the "base", which should not be exported unless specified.
But correct me if I am wrong.
As I got above behavior, so I tried to specified namespace="" to force it to export the base only. But still the "ToC" get exported in any way.
In reply to pas06:
So I went to enable the Localization phrases updates on my project.
I expect to get notification when any translator adding or updating translation so that I can prepare for trigger next release.
The actual result seems to be the fact that I will only receive notification when I did add any new entry, or updated any translation.
I then go to Localization -> Overview page and then realized other translators have already updated several entries, but I never receive notification on their changes.
Could you check?
Not supporting non-Latin Unicode for importing would be troublesome especially when dealing with Asian languages or Russian.
This used to be supported, but recently when I am importing translation, I got this message:
Non Latin Unicode characters are temporarily not allowed.
Is there any other workaround?
Any update on the packaging issue?
I have tried a few tricks on AtlasLoot including to remove all external libs, or set them as hard-embedded, but all keeps the external links in pkgmeta. Still the packaging is not working. As 7.1.5 is about to go live, I hope this can get resolved soon so that we can release a new version to players.