• 0

    posted a message on Don't know why I am suddenly no longer allowed to commit?

    In reply to Torhal:

     Thanks Torhal. I was looking for the solution for quite a while, and finally got this answer.

    Posted in: Need Help?
  • 0

    posted a message on Library autopackaging packaged a 'diff' of the last two library builds

    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:

    • Libaaaa.lua
    • Libaaaa.lua.mine
    • Libaaaa.lua.r10
    • Libaaaa.lua.r12

    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....

     

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Localization by the players and 'needs review'

    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.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Issues with localization exporting during auto-packaging

    The default behavior seems to get changed in these few days.

    1. handle-unlocalized

    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.

     

    3. handle-subnamespaces

    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.

     

    4. namespace

    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.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on "Repository -> Tagging" function

    In reply to Torhal:

     I have no idea. Now it shows:
    Unhandled error while processing request. - Please submit a support ticket at https://support.curse.com for further assistance.
     
    Posted in: WoW Sites Feedback
  • 0

    posted a message on "Repository -> Tagging" function

    In reply to Torhal:

     line 17 has tag: latest for CallbackHandler-1.0, let me remove it and see how it goes.
     
    Posted in: WoW Sites Feedback
  • 0

    posted a message on "Repository -> Tagging" function

    Still not working for AtlasLoot.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Localization by the players and 'needs review'

    In reply to pas06:

    So are you able to un-check the "Needs Review" and then click Save button which we should expect to see this phrase's current translation being set as normal (means needs review will be gone)?
    Or are you able to see the "Approve" link so that you can "approve" this translation?
    Posted in: WoW Sites Feedback
  • 0.991404011461318

    posted a message on Project's "Following" option to follow localization phrases updates

    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?

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Localization Importing not support non Latin Unicode characters

    Great, thanks!

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Localization Importing not support non Latin Unicode characters

    Not supporting non-Latin Unicode for importing would be troublesome especially when dealing with Asian languages or Russian.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Localization Importing not support non Latin Unicode characters

    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?

     
    Posted in: WoW Sites Feedback
  • 0

    posted a message on "Repository -> Tagging" function

    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.

     
    Posted in: WoW Sites Feedback
  • 0

    posted a message on "Repository -> Tagging" function

    I wonder this could be related to some errors during the packaging. In the previous packager, we are able to see the full logs of the packaging process, and sometimes there were some errors and we might be able to fix it.

    My Currency Tracking was not auto-packaged until I update the .pkgmeta with correct external libs' URLs. Though I am not sure if that's the root cause since my Accountant Classic is still not auto-packaged...

     
    Posted in: WoW Sites Feedback
  • 0

    posted a message on "Repository -> Tagging" function

    Auto packaging was working fine with my Accountant Classic but now seems to stop working. I have several revisions committed.

    Similar behavior seems to apply to my Currency Tracking

    Posted in: WoW Sites Feedback
  • To post a comment, please or register a new account.