[00:47] When I go to my LP translations page, I see "Russian" is listed under Translation for trunk, but then disappears after a second or two. [00:59] KombuchaKip: It shows only your preferred languages my default. You can show Russian again by clicking "View all languages" [01:00] wgrant: I'm an idiot. Thanks. [01:00] The list can get slightly large on well-translated projects [01:04] wgrant: Fair enough. Is there any way to set my translation catalogue template to be identified as en_CA already so that I don't have to provide a redundant en_CA.po? [01:07] wgrant: I see there is a 'Language' header field but I don't know how to set it. [01:23] KombuchaKip: POTs are always C [01:23] It's impossible to make them en_CA, because they are defined to be C [01:23] wgrant: By C, you mean en_US? [01:23] The POSIX locale. [01:25] wgrant: Which is en_US? [01:27] KombuchaKip: Not specifically, but it's usually treated as such. [01:27] wgrant: Thanks. [01:28] Pretty much everything treats C as en_US and lots of software probably makes assumes around that, so doing otherwise would be rather inadvisable. [01:29] wgrant: Fair enough. [01:30] wgrant: I am using AM_GNU_GETTEXT macro. I can't figure out how to set the CHARSET to utf-8 automatically when my .pot is generated each time with update-po target. Do you know how to do this, perchance? [01:31] wgrant: I'm fairly new to i18n / autotools / launchpad translation integration. [01:31] I only know the Launchpad side of translations, unfortunately. [01:33] wgrant: It's ok. Thanks anyways. [01:34] wgrant: How does Launchpad register new translation catalogues with a project? Do I simply commit a new lang.po file into the repository for my project and it automatically sees that and makes it available for translation? [01:35] KombuchaKip: https://translations.launchpad.net/avaneya will always show the user's preferred languages, so they can create a new translation themselves. [01:35] eg. I see en_AU and en_GB there, despite there being no existing translation [01:35] But if you have somethig to work from, adding an en_AU.po to the branch will work [01:36] wgrant: Ok. [01:37] wgrant: So in theory I shouldn't need to manually add any files to my tree in order for someone else to perform a translation on LP which can then be merged into my brach automatically? [01:37] *branch [01:37] KombuchaKip: Exactly [01:37] wgrant: So I should just delete these .po files I was creating as stubs. [01:38] Yep [01:38] Launchpad will autocreate them the first time a user translates a string in a new language [01:48] wgrant: Right on. So if I have someone who wants to translate into language X for my project, what is the best URL to send them to? [01:51] KombuchaKip: https://translations.launchpad.net/avaneya [01:52] wgrant: thanks [01:52] As long as they have their preferred languages configured in either LP or their browser/OS [02:19] wgrant: How do I add an additional template to here? [02:19] wgrant: Or does it happen automatically when LP detects that I commit a new .pot file? [02:20] KombuchaKip: In most cases it should work automatically [02:20] If you're not using bzr imports then you can go to https://translations.launchpad.net/avaneya/trunk and do a tarball import [02:20] wgrant: Ok, I imagine I just have to wait for it to refresh. [02:20] But since you're using bzr it should be automatic [02:20] wgrant: Fair enough. Thanks. [02:20] wgrant: Appreciate the help. [02:20] https://translations.launchpad.net/avaneya/trunk/+imports [02:21] KombuchaKip: You can see there that the pot imports are approved and in the queue [02:21] Right. [02:22] 2013-05-25 02:21:33 INFO Importing: Template "vlr" in Avaneya trunk [02:22] 2013-05-25 02:21:39 INFO Importing: Template "viking-extractor" in Avaneya trunk [02:22] 2013-05-25 02:21:44 INFO Import requests completed. [02:23] It should autodetect and import the translations within 15 minutes or so [02:28] wgrant: Thanks a lot. [02:28] np [02:29] wgrant: Here's a question for you. How can I test a ru.po translation? I don't speak Russian, but I installed language-pack-{ru,base} and then ran LANG=ru hello, but it's still in English. [02:29] wgrant: I tried rebooting as well. [02:32] KombuchaKip: You'll want to set LANGUAGE and LC_ALL [02:32] And possibly LANG [02:32] eg. LANGUAGE=en_RU:ru LANG=ru_RU LC_ALL=ru_RU.UTF-8 [02:33] wgrant: Ok, let me give it a try. [02:33] wgrant: Ok, there we go. hello works. =) [02:34] Er, s/en/ru/ [02:34] wgrant: Do I need to have language-pack-ru installed in order to do this, or is the .mo Russian file hello came with not enough? [02:36] KombuchaKip: You need to have the ru_RU.UTF-8 locale generated, which you can do without language-pack-ru by running 'sudo locale-gen ru' [02:36] But installing language-pack-ru gives you translations for Ubuntu and automatically generates those locales [02:36] wgrant: Thanks [02:36] So it's usually the way to go [02:37] KombuchaKip: Setting LANGUAGE=ru_RU:ru is probably sufficient for testing [02:37] It should override LANG and LC_ALL, I think [02:39] wgrant: Thanks. Why is it ru_RU:ru and not just ru_RU? [02:41] KombuchaKip: Good point, ru_RU or just ru should work [02:41] KombuchaKip: Thank you. [02:42] I'm used to using en_AU:en, because it's a priority list [02:42] wgrant: Right. [02:42] it'll try to use en_AU first, but if there's no en_AU message then it'll fall back to the default en locale [02:43] wgrant: Right. Makes sense. [15:22] Is there a particular reason many PPA builder machines are disabled during the weekends? [17:24] there's no way to get a builder for debian on a ppa is there? [17:24] (probably not)