• 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
  • 0

    posted a message on Packager BUG
    Quote from oscarucb >>
    Quote from ZeldoKavira >>

    Quote from oscarucb >>

    #@no-lib-strip@ in TOC files is also being ignored, breaking no-lib creation.

     

    Is there a new syntax for no-lib exclusion? (it does not appear in the new packager docs)

     I am adding a ticket for this now, should still be the same. 
    The problem here appears to be that the new packager is not correctly handling svn's built-in externals - ie any libs pulled in by the svn:externals property are being pulled into the -nolib package, even if they should not be.
    Most likely the fix is to add the --ignore-externals option to any svn checkout/update command used to fetch the repository before packaging. This should mimic the behavior of the old packager and avoid sucking svn:externals into -nolib packages, whilst still allowing developers the use of svn:externals for their convenience in their local working directory.
     
     In my case, as I am using SVN, but some of the libs are not SVN, for example LibAboutPanel is using Git. So for my own development, I actually hard-added LibAboutPanel to my lib folder, not using external in the properties.
    With the old packager, I use "ignore" in .pkgmeta to ignore those hard-added folder so that they won't be included. But they were defined in "external" section so that the packager knows what to pull out from and put into the package.
    Now the new packager's behavior seems to also ignore what is defined in "ignore" section when pulling out the external lib, or maybe to exclude while creating the final ZIP.
    Posted in: WoW Sites Feedback
  • 0

    posted a message on Auto-packaging issue: Localization keyword replacement not working; external lib not included

    OK, I will try using those replacement again and see how it goes with my next release.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Auto-packaging issue: Localization keyword replacement not working; external lib not included

    So for the URL, the below is correct for those are Git or HG?

    Libs/LibAboutPanel: https://repos.curseforge.com/wow/libaboutpanel

     

    For localization, yes if I re-download the old ZIP (for example, v2.08.00), I can see everything looks fine with proper localization in both TOC and loc lua files. Though the problem is several users reported the problem while I think they are most likely download via curse client.

    I read another thread similar to this and you explain the problem. So somehow the ZIP which is not yet processed went public too early. Correct?

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Auto-packaging issue: Localization keyword replacement not working; external lib not included

    I have tagged a new release today on my addon Accountant Classic and realizing the following is not working with the auto-packaging:

    • Localization keyword replacement in TOC file is not working
    • Localization keyword replacement in lua file is not working
    • The external Git libs are not included with the auto-packaging while my addon is on SVN.
      So for this one I am wondering if my statement in .pkgmeta is wrong:
    externals:
        Libs/AceAddon-3.0: https://repos.wowace.com/wow/ace3/trunk/AceAddon-3.0
        Libs/LibAboutPanel: https://repos.curseforge.com/wow/libaboutpanel
    

     LibAboutPanel is on Git.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on "Repository -> Tagging" function

    True. But my another addon (also using SVN) on curforge is working fine with the auto-packaging. AtlasLoot is on WowAce, although not sure if that matter.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on "Repository -> Tagging" function

    @Torhal, Proteyer's question is for AtlasLoot. I tried deleted two tags he made and re-tagged a brand new "/tags/v8.01.07". Now let's see if the auto-packaging will work or not.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Bug on the localization site.

    I guess there is something wrong with the brackets' (< & >) handling.

    Hoping this can get fixed so that translators won't get confused on the actual English text.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Packager BUG

    previously before the migration, the keyword replacement handles the "do-not-package" properly.

    for example, the entire block enclosed by "--@do-not-package@" and "--@end-do-not-package@" will be removed after auto-packaging.

    Now after the migration, everything enclosed by those two tags will be removed except the ending tag.

    Means the "--@end-do-not-package@" is still there.

    Although this is no harm to the function, but still a bug.

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Localization history log
    Quote from Tuhljin >>

    Thanks for your response. I'm looking forward to this feature's return.

     Same here. The localization activities log is quite helpful to know who translate what so that I can mentioned it in the change log when a new release is going to be out.
    Posted in: WoW Sites Feedback
  • To post a comment, please or register a new account.