[10:15] trijntje: Hi! Have you find the answer about building of translated ubuntu-docs? [10:15] yurchor: no, I havent yet [10:16] Did you try just ./autogen.sh then make? [10:20] If it does not help, you can use manual conversion for this Mallard documentation: http://itstool.org/documentation/basic-usage/ [10:21] Mallard (in oppose to DocBook) does not support PDF conversion, so you can use Calibre to convert HTML. [10:22] I mean HTML -> ePub or PDF. [10:23] yurchor: I did also try ./autogen.sh and then maken, but make aborts with an error [10:24] Oops, then only hardcore ITS tool way... [10:29] I think make calls itstool, which than crashed [10:29] http://paste.ubuntu.com/930794/ [10:33] He-he, replace en_Uk with en-GB in Makefile.am (these guys do not even read what they write). Then regenerate makefile. [10:34] I mean ubuntu-help subdir. [10:34] And en_GB for sure [10:40] yurchor: cool, thanks! Now make runs without problem [10:42] trijntje: yurchor, did you fix the errors in ubuntu-docs in your own translations? [10:42] if you're going to make a printed book/PDF, it would make sense to fix the actual errors in -docs in your own translation [10:43] just saying [10:43] trijntje: M-m-m, I have not translated it at all (I do not use neither Ubuntu, nor Gnome). [10:43] yurchor: ok [10:43] Sorry.. Mistyped, artnay [10:43] artnay: what kind of errors in -docs? [10:44] xmllint errors, I think. [10:44] trijntje: well here are a few that I reported: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bugs?search=Search&field.bug_reporter=jiri-gronroos [10:44] I'm sure there's more [10:45] jbicha will probably fix those in SRUs [10:45] trijntje: mainly non-working keyboard shortcuts/missing information/incorrent terms [10:46] Typo: "choosen" in net-proxy.page is not fixed ;) [10:47] artnay: ah I see, problems in the source text [10:47] I could look into that, I'm not a huge fan of 'fixing' stuf in translations, unless its really big mistakes [10:47] trijntje: yes. I'm actually surprised that other translators haven't reported more bugs since they're easy to spot IF translators just don't translate but in fact follow the instructions step-by-step [10:48] translating (and following!) -docs is probably the best way to spot such errors before release [10:48] there's never enough proofreading [10:49] artnay: Crowd translations... [10:49] It's easier to ignore the bugs, than report them. [10:50] that's just bad [10:50] the least one can do is to report bugs [10:50] I havent worked on the docs this cycle, but I usually follow all steps and report bugs when I find them [10:53] we did a lot of work for -docs this cycle (still 31 untranslated), and we commited our translations to gnome-user-docs (which grew like 60 %) [10:54] with a little bit of manual work gnome-user-docs would grow to 80 % or more [10:56] anyways, if there's a lot of changes to -docs in next releases and LP won't gain any sort of fuzzy support, I guess we'll focus our efforts to -docs once again in next LTS [10:57] gtranslator is a pretty good software with its open-trans support and advanced fuzzy algorithms [10:58] yeah, lack of fuzzy in lp is too bad. But you can alway'se use msgmerge to merge the docs yourself, resolve the fuzzy's and then upload it to launchpad [10:58] but that probably won't work so well when you have more than 2 people working on it [10:59] if only gnome/KDE would adopt their own transifex instance as xfce did. it's a pretty welcome addition to git. [11:01] I thinkg synchronisation with gnome should be automated by now? [11:01] I don't know if you care about KDE, but I found this pretty interesting: http://techbase.kde.org/Localization/Workflows/PO_Summit [11:02] trijntje: we did something interesting in upstream gnome this cycle [11:03] trijntje: we setup our own instance of translatewiki (see http://translatewiki.net/wiki/Main_Page) and imported all po/pot files from upstream [11:04] then we did a lot of translation work in our translatewiki (lots of corrections, twiki has a decent fuzzy support and translation memory) [11:05] and after five days we had gained a lot of unification and new translations, then we sent the results to upstream. and now those translations are in Ubuntu (and well, in other distros as well) [11:06] better than translating in LP, merging from LP templates makes upstream curse. :-) [11:06] artnay: thanks for the link. Upstream integration with gnome is pretty good for dutch right now, so I was planning to look into better cooperation with kde [11:09] trijntje: as do we. I went back to KDE in 4.3 and now with 4.8.2 I'm happy with it EXCEPT the translations... [11:10] in general, gnome has better translation coverage and quality. but we're actually focusing our effors on KDE before 4.9. lots of work to do. [11:10] trijntje: and this is godsent: http://l10n.kde.org/dictionary/search-translations.php [11:11] the only problem with is that it ignores (as expected) accessory keys (is that the right term? I mean Alt + letter) [11:14] I think they are called accelarators [11:14] true, true [11:14] We alway's use http://en.nl.open-tran.eu/ to check for consitency in translations [11:14] thanks for correcting [11:15] trijntje: open-tran.eu is actually integrated in gtranslator [11:16] trijntje: http://projects.gnome.org/gtranslator/ [11:17] you mean as the 'translation memory' or a real plugin for opentran? [11:23] trijntje: plugin [11:27] nice [14:20] dpm: do we need to re-upload the translation for calligra? because the translation stuff was last uploaded before the pkg-kde-tools fix? [16:24] Salut ! Y a-t-il des Français ici ? [16:27] Is there any French here ?