LibBabble-DigSites-3.0 is designed to translate the dig site names easily for addon authors. In its short life, many of the translations have already been put into place.
The lib awaits approval, but other than that, it is ready to use even in its current alpha form.
There is more information on the main page, but it is fairly simple.
No, there was never a version 1.0 or 2.0, I just followed LibBabble-3.0 naming convention.
After speaking to Torhal (who the project claims to be the manager of this Babble lib), i added DigSites into my babble update script, which will export the babble locales directly into the repository.
I did some rather massive updates to all locales and will do the same for the last remaining (zhCN) shortly.
Does that mean I'd have to wait a week for an updated package for Archy? (for example)
My real question is: Is editing the file to force a repackage in the
- 'not necessary' (under normal circumstances) category or the
- 'will break stuff' category?
Its not necessary, and if anyone does it, next push will overwrite it. I also got Torhal to lock the repository to members only ;)
If you want a new update faster then my normal schedule, just ping me, and i'll build one. Only thing i would prefer to limit to once a week is tags, but exceptiosn can be made if required.
Maybe I didn't explain myself well enough, I don't mean manually editing the localization files.
I mean touching the .toc for example to force the packager to pickup the new translations from the localization app.
If I can't do that, it's not a very good deal for me :-P
Nvm, I see this is an old decision that for some reason LibBabble-DigSites-3.0 escaped from sofar.
You're just fixing it, I'll stop making waves now :-D
Touching the toc would not update translations anyway, its no longer using the packagers localization tag, my scripts export the translation into the repository directly.
This allows people that don't use the wowace packager to directly use the svn versions, which was the main argument we made back then to do it this way.
Like i said, if you for some reason need an updated package, instead of poking the toc, just send me a message.
Someone sent me a PM with a partial list of the dig site blobIDs, mostly for Pandaria. Great, I know about ArcheologyGetVisibleBlobID and ArcheologyMapUpdateAll, but neither gives you a comprehensive list of all dig sites, nor does it convert the IDs into locale independent names. That is why I never used the APIs. Of course, somehow, Blizzard can put that information on the map, so I'm wondering how they do it?
Yes, I am trying to find a way to depreciate this library.
Blizzard uses a special frame type which probably comes with a C function which shows the name from C side. Of course the game knows all names, but they dont give them to us (so far).
Nevcairiel, do you want me to tag the latest build for patch 5.3, or are you doing that with your semi-weekly localization bumps of all things LibBabble?
Tagging a TOC bump for a library doesn't seem like a thread-bump-worthy issue... anyone using standalone libraries should be savvy enough to know how to use the "Load out of date addons" checkbox. If you have tagging permissions on the project, and you think it needs a tag and is in a release-ready state, just tag it. :/
The lib awaits approval, but other than that, it is ready to use even in its current alpha form.
There is more information on the main page, but it is fairly simple.
No, there was never a version 1.0 or 2.0, I just followed LibBabble-3.0 naming convention.
The SVN should no longer be manually edited.
Does that mean I'd have to wait a week for an updated package for Archy? (for example)
My real question is: Is editing the file to force a repackage in the
- 'not necessary' (under normal circumstances) category or the
- 'will break stuff' category?
If you want a new update faster then my normal schedule, just ping me, and i'll build one. Only thing i would prefer to limit to once a week is tags, but exceptiosn can be made if required.
I mean touching the .toc for example to force the packager to pickup the new translations from the localization app.
If I can't do that, it's not a very good deal for me :-P
Nvm, I see this is an old decision that for some reason LibBabble-DigSites-3.0 escaped from sofar.
You're just fixing it, I'll stop making waves now :-D
This allows people that don't use the wowace packager to directly use the svn versions, which was the main argument we made back then to do it this way.
Like i said, if you for some reason need an updated package, instead of poking the toc, just send me a message.
Yes, I am trying to find a way to depreciate this library.