[MonoDevelop] German translation
Sun, 11 Jul 2004 17:00:26 -0500
I've been fixing some things in the Spanish translation
working directly on the es.po file (no touching of gmo
is need afaik)
Once you're done if you just need to do minor adjustments
you can simple do this:
msgfmt -o monodevelop.mo <YOUR LOCALE>.po
You get the monodevelop.mo file you need to replace on top
of the one found at /usr/share/locale/<YOUR LOCALE>/LC_MESSAGES/
and then restart monodevelop.
You should see the changes in action without recompiling
Also if you're a translation mantainer and new messages
get internationalized resulting in a new mondevelop.pot
file you can merge this new file with you current work with
msgmerge <YOUR LOCALE>.po monodevelop.pot
Hope this is usefull,
On Fri, 02 Jul 2004 15:37:06 -0400, Todd Berman <firstname.lastname@example.org> wrote:
> Viktor Stansvik wrote:
> > Hi. I just created a swedish translation by:
> > 1. Downloading the tarball
> > 2. Entering the po/ directory and running 'intltool-update --pot'
> > 3. 'cp monodevelop.pot sv_SE.po'
> > 4. Adding translated strings to sv_SE.po
> > 5. 'intltool-update sv_SE'
> > 6. Converting sv_SE.po to utf-8 by running
> > 'msgconv -t UTF-8 sv_SE.po > sv_SE.po.new && mv sv_SE.po.new
> > sv_SE.po'
> > 7. Adding sv_SE to ALL_LINGUAS in configure.in
> > 8. running ./configure and make (but not make install, I already have
> > monodevelop installed from an ebuild)
> > 9. Creating a .mo file by running msgfmt -cv sv_SE.po and copying it
> > to /usr/share/locale/sv/LC_MESSAGES/
> > After this I thought I could test the translation by entering the
> > build/bin/ directory and running MonoDevelop.exe from there, but I
> > seemed to be wrong.
> > What do I have to do to test my translation? I noticed that no .gmo file
> > was created during any of the steps described above, has it got
> > something to do with that?
> > Hope I provided enough info for you to help me.
> > - Viktor
> I believe the make install process handles everything properly, but I am
> not sure.
> So you can most likely look there to see what it is doing exactly.
> Monodevelop-list mailing list