[KDE-India] installing desktop_*.po?

Vivek Rai vivek.rai at gmail.com
Fri Jan 20 13:45:28 CET 2006


>
> Hope  you are  co-ordinating this  with the  teams already  working on
> Indic  translation; and  geuss  you  will be  better  off asking  this
> question the indlinux list - see
> https://lists.sourceforge.net/lists/listinfo/indlinux-group


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.

Hmm.. there is  some confusion - you should  be translating files with
> the extension  .pot; you do not  (cannot) build anything  from the .po
> files.


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/

You want to build the files  for translating from sources? Or you want
> to  install  the  translated  .po  file?  (once  again,  googling  for
> localisation will help)
> also see:-
>
> http://www.ncst.ernet.in/groups/research/oss/downloads/localisation/localisation-guide.pdf


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..

the answer is:
1) the desktop_*.po files have the target *.desktop file name as a comment
above the msgid in the po file.
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.

a) merge_desktop_files.sh (looks like it creates an apply.mo from the
desktop_*.po and it then calls the executable apply to 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) )
b) createdesktop.pl (appears to be doing the reverse of above, generating
pot files from desktop entries)

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.

Thanks guys, at least the next person in the universe facing the same
question should have a ready answer within the kde.org website. ;-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-india/attachments/20060120/68f2b823/attachment.html 


More information about the KDE-india mailing list