<div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hope you are co-ordinating this with the teams already working on<br>Indic translation; and geuss you will be better off asking this
<br>question the indlinux list - see<br><a href="https://lists.sourceforge.net/lists/listinfo/indlinux-group">https://lists.sourceforge.net/lists/listinfo/indlinux-group</a></blockquote>
<div> </div>
<div>Yes, i have been working as a volunteer in indlinux for a few years now, and had asked the question there too.. just duplicated it here in desperation .. (indlinux mailing list can suddenly go very queit at times!).. actually, i have found the answer now.
</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hmm.. there is some confusion - you should be translating files with<br>the extension .pot; you do not (cannot) build anything from the .po
<br>files.</blockquote>
<div> </div>
<div>umm... actually... .pot files are the untranslated templates.. created out of running xgettext on the source files. u then create a .po file for your language (either a simple cp, or after merging with various compendium, or after merging the old po with the latest pot), and do translations of the .po file, these get built to .mo files (using msgfmt) which are normally deployed under /usr/share/locale/
</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">You want to build the files for translating from sources? Or you want<br>to install the translated .po file? (once again, googling for
<br>localisation will help)<br>also see:-<br><a href="http://www.ncst.ernet.in/groups/research/oss/downloads/localisation/localisation-guide.pdf">http://www.ncst.ernet.in/groups/research/oss/downloads/localisation/localisation-guide.pdf
</a></blockquote>
<div> </div>
<div>Thanks for the link.. this was a specific case of applying translations to desktop_*.po files. After build+install these would appear as *.desktop files. I was looking to findout how this works..</div>
<div> </div>
<div>the answer is:</div>
<div>1) the desktop_*.po files have the target *.desktop file name as a comment above the msgid in the po file. </div>
<div>2) There are 2 scripts under l10n/scripts (at the top level of your KDE source tree, if you checked l10n module out), which do the task.. arent documented well.. no comments, but i think i should be able to hack them around.
</div>
<div><font size="2"></font> </div>
<div><font size="2">a) merge_desktop_files.sh (looks like it creates an apply.mo from the desktop_*.po and it then calls the executable <font size="2">apply to </font>apply translations to dektop files, looking at apply.cc
, it simply iterates and dumps out various entries needed by a .desktop file (Name=xxx, GenericName=yyy etc) )</font></div>
<div><font size="2">b) createdesktop.pl (appears to be doing the reverse of above, generating pot files from desktop entries)</font></div>
<div><font size="2"></font> </div>
<div><font size="2">I can take these utils as my starting point, and create a simple perl/sed script which will apply my desktop_kdenetwork.po translations to the target kopete_*.desktop files. </font></div>
<div><font size="2"></font> </div>
<div><font size="2">Thanks guys, at least the next person in the universe facing the same question should have a ready answer within the <a href="http://kde.org">kde.org</a> website. ;-) </font></div></div>