[08:06] good morning and happy new year everyone! :) [08:30] morning :) [10:15] Hi, want to test updated open office translation, how do i get the new mo files into ubuntu? [10:17] Hi, want to test updated open office translation, how do i get the new mo files into ubuntu? [10:17] Hi, want to test updated open office translation, how do i get the new mo files into ubuntu? [10:17] arjunaraoc, could you give us a bit more info? (i.e. is this a new translation, for which language, which openoffice version, etc?) [10:18] hi dpm [10:18] btw, no need to ask 3 times ;) [10:18] sorry trying new chat tool and facing problems [10:18] no worries :) [10:19] i will drop xchat and rejoin over chatzilla [10:23] hi dpm, I found bugs in OO3.2 Telugu translations. I updated translation strings locally. I have generated directory with mo files. How do I install on ubuntu for local testing before submisison to Libo/OOo [10:23] arjunaraoc: Please read this: http://wiki.services.openoffice.org/wiki/Translation:General_Information#Generate_GSI.2FSDF_file_from_translated_PO_files [10:24] in general openoffice translations come straight from the upstream package, and they are not mo files. openoffice uses its own translation system ^ [10:26] thx yurchor, dpm. It means that I can't test locally the updated translation, without an updated build from OOO/LibO [10:26] am i right? [10:26] arjunaraoc, correct [10:26] arjunaraoc: No. You can test it [10:26] :-( [10:27] hey dpm, I'm curious about what to do with libreoffice in the future. I'm not sure whether it will be shippt with natty, but it is determined to be there someday. [10:28] * happyaron shipt -> shipped [10:28] arjunaraoc: It is enough to install Translate Toolkit and use it in a right way. [10:29] hey happyaron :) I'm not sure, either. I'm not up to date with the situation with LibO, so I'd recommend asking at #ubuntu-desktop. In any case, we still don't have a dedicated maintainer for the office stack, so this makes things a bit more difficult [10:31] yurchor I have to make lot of corrections. As OO core consists of over 21K strings, I thought I will check for consistency before submission. [10:31] The translations of formula related files is confusing [10:34] see, LO is still stucked with xliff files, at least for 3.3 release. It was and is a nightmare... [10:53] happyaron, xliff? [11:01] dpm: yes, .xlf [11:03] happyaron, I haven't been following LibO/OO.o development recently, so did they switch from GSI/SDF to xliff? [11:03] dpm: no, they use a mixture of sdf, xliff and gettext now [11:04] happyaron, what do you mean a mixture? Which part of LibO/Oo.o uses which format? [11:04] dpm: lo-build use po, docs use xliff, other parts seems to be sdf [11:05] oh dear [11:06] dpm: for LO extensions, I'm not sure what format they are using. The suffix is .properties [11:07] real mess [11:09] .properties I guess are java/javascript properties definitions, the same as Firefox [11:09] perhaps, but not sure. [11:11] the good thing is translation-tookit has a tool to handle those formats, the bad thing is the tool does not generate valid po files, :( [11:50] dpm, we were previously talking about the ubuntu translators' tools ( https://code.launchpad.net/~glatzor/ubuntu-translator-tools/main ) and that it would be good to have some ubuntu packages. I've compiled a package and published it for lucid, maverick and natty: https://launchpad.net/~askhl/+archive/ppa/ . [11:58] @ashkl_ : what do these tools do ? [12:00] andrejz, it's a tool to search for strings in the installed langpack(s), which is useful for finding out which template a particular string comes from [12:01] andrejz, there's also a tool to diff po-files [12:02] (andrejz, in case you're interested I also work on some other po-file related tools found on https://launchpad.net/pyg3t ) [12:07] askhl_, that's awesome, good work!. I'd also recommend asking around on #ubuntu-motu to see if someone would like to sponsor your packages to the universe repositories, so they can be available to anyone without subscribing to the ppa [12:11] askhl_ : looks really useful, I will definetly look at it [12:17] andrejz, if there's any particular thing you would like to do with a po-file, I'm always looking for excuses to implement something useful [12:17] dpm, done [12:18] a lot of times when i am searching for some strings with non proper terminology [12:18] could you elaborate? [12:18] i have problems because often words have a line _ in between (for keyborad shortcuts) so i cannot find them [12:19] i want to find Executre [12:19] Executre [12:19] andrejz: that's handled by gtgrep from pyg3t already [12:19] ok, goodie :D [12:19] then i am going to try it first thing after i come home [12:19] andrejz: (although gtgrep doesn't directly work on the installed langpack mo-files. Supporting that may be desirable...) [12:20] is it possible to also include custom .po files in the string search [12:20] andrejz, note that pyg3t and the ubuntu-translator-tools cannot (as of now) be installed at the same time as they both contain a script named podiff [12:21] custom .po files? [12:21] because in our gnome translation team we have a shared dropbox folder with all .po files [12:21] so it would be great if i could simultaneously also see if the error is also present in gnome packages or not [12:22] if one could search both in the system .mo files and this additional .po files i could quickly see whether error comes from launchpad or gnome [12:22] of course my workflow is very specific so it might not be useful for many people [12:23] Right, that's not possible without writing some lines in bash (a loop with an msgunfmt command or such) [12:23] additionally i am not a coder, so i cannot image how difficult this is (easy or very hard) [12:24] Since pyg3t works on po-files (not mo-files) it is straightforward to use it on the GNOME po-files. THe installed mo-files have to be msgunfmt'ed first though - that's the only thing [12:26] I have GNOME .po files in my case