Extension talk:IM Status

i18n
First I want to say that this is realy nice work, thank you. I would like to help creating a German translation for the Help. I think it would useful when there would be a i18n file with the messages or when the messages would be translatable throug translatewiki/Betawiki DaSch 22:17, 11 May 2008 (UTC)
 * Well, I'm still learning how all this extension stuff works, and I don't have much spare time currently... I think I'll be able to make a version with a i18n file by mid-june. Or maybe I could post the code here in a subpage? The main reason why I didn't do it yet is because I was afraid it might mess up with the code indentation. Patheticcockroach 05:47, 12 May 2008 (UTC)
 * It's not that nessasary. I think mid-june is enough for me. DaSch 18:08, 12 May 2008 (UTC)
 * Ok, I'm really stuck in there. Localizing the extension seemed pretty straight forward... until I got this very weird error:
 * Fatal error: Call to undefined function wfMsg in /www/extensions/IM/IMStatus.php on line 51
 * Undefined wfMsg? All other extensions use it, wtf? Anyway, any help about this would be welcomed, the documentation (wfMsg, Extensions) says nothing about this (do I need to include some file, etc?). Patheticcockroach 09:52, 9 June 2008 (UTC)


 * I think this is important, here the file is loadd


 * then second this is important

--DaSch 18:52, 9 June 2008 (UTC)
 * Thanks. I already had the first part. The second part, though, gives the same kind of result as wfMsg:
 * Fatal error: Call to undefined function wfLoadExtensionMessages in /www/extensions/IM/IMStatus.php on line 41
 * Patheticcockroach 20:22, 9 June 2008 (UTC)
 * Never mind I figured it out: for some reason wfLoadExtensionMessages and wfMsg must be called from inside functions... I can start working on the localization now :) Patheticcockroach 20:46, 9 June 2008 (UTC)
 * Okay very nice. After your next release I will create a german translation. --DaSch 21:50, 9 June 2008 (UTC)
 * Done. To make your translation just edit Extension:IM_Status/IMStatus.i18n.php. And to test it, use it with the beta. Patheticcockroach 17:54, 10 June 2008 (UTC)
 * Made it easier now that the extension is in . Cheers! Siebrand 20:27, 5 October 2008 (UTC)
 * Thanks, but I just don't understand how this website works. Spent like 30 minutes browsing around their awfully unhelpful help pages and stuff, and didn't manage to find the link to download all translations as an i18n (or i18n-ready) file... Localizing is something I totally hate (everyone please learn English and zillions of hours - and dollars - wasted on translations will be spared), so I can do it if it's straightforward like babelzilla.org, but I won't spend more time RTFMing there. Patheticcockroach 07:18, 6 October 2008 (UTC)
 * The page you should have ended up on, after most probably not reading the welcome message on your talk page, is linked in the translator section, betawiki:Translating:Intro. The page after that is betawiki:Translating:How_to_start. That shouldn't take longer than 5-10 minutes, and you're ready to roll. It took me longer to work out how to navigate in Babelzilla (and it appears collaboration is hardly possible there). Cheers! Siebrand 07:27, 6 October 2008 (UTC)
 * I've already read these 3 pages. Still I find no link to download the i18n file. The best I found is a page to download every locale separately where after trying a few options again, I just found how to get the translation in i18n format: "Export translation to file from" (this option doesn't work with the default language - en - which is why I missed it earlier toady), but it's still only for one locale at a time. Any way to grab them all at once? If not, I suggest adding "All" at the top of the list in the "Language" drop down box, or just an extra "Download all locales" link somewhere on this page... In comparison to BabelZilla, your site is very unbalanced in favor of translators. I mean, there doesn't seem to be much tools (submit/update/download) for extension developers. That's what I meant when saying BabelZilla is more straightforward. Patheticcockroach 09:46, 6 October 2008 (UTC)
 * Commits are centralised at the backend in the Betawiki scope. You'll see localisations pop up in SVN about every two days. From a translator point of view we focus on one language per translator, which means that you do not need multiple languages. Cheers! Siebrand 12:20, 6 October 2008 (UTC)
 * Oh... so localization updates are all automatic? Well, perfect then :) Patheticcockroach 12:28, 6 October 2008 (UTC)

MS Communicator
Great Work. Could someone get it to work with Microsoft Communicator in a corporate environment?

GobleS 19:19, 22 August 2008 (UTC)
 * This extension uses IM status services for websites provided by the makers of the various IM programs: for instance, for Skype I used this... Do you know if Microsoft Communicator provides the same kind of service? After a quick search I didn't find anything. I'll search more tomorrow, but if you happen to have any information on such a feature, it would help :) Patheticcockroach 21:36, 22 August 2008 (UTC)
 * Well, I can't seem to find any official pre-made status checker :/ The help doesn't even mention this option. Did anyone get more luck than me? Patheticcockroach 14:39, 28 August 2008 (UTC)