You can clone with
Cannot retrieve contributors at this time
The Makefile.in.in here was originally produced by gettextize, but hassince been modified extensively.If you convert a C file for use with gettext, add it to POTFILES.in andthen run make update-poto recreate R.pot and update the automated `translations'.Target make update-pkg-poupdates the message catalogs for the C and R code in the standard packages,uses msgmerge --update to update the translations and then re-makes the compiled (.mo) files.To do this for an individual standard package use make pkgname.pkg-updatee.g. make grid.pkg-update.To add a new translation, add the lang.po file to this directory andadd the language to LINGUAS. Hopefully 'make all R' (in the builddir,if separate) will do the rest (create ll.gmo and install it asrequired). For fuller manual control, use msgfmt -c --statistics -o ll.gmo ll.poto check and compile the translation, and mkdir R_BUILD_DIR/share/locale/ll/LC_MESSAGES cp ll.gmo R_BUILD_DIR/share/locale/ll/LC_MESSAGES/R.moto install it manually for testing.Windows RGui translations=========================These are contained in RGui.pot, created by running 'make RGui.pot-update'.Translations should be called RGui-ll.po for language 'll': such a file iscompiled by msgfmt -c --statistics -o RGui-ll.gmo RGui-ll.poTo add a translation, add both the .po and .gmo files to theRGUI-CATALOGS macro in Makefile.in.in: it will then be automaticallydistributed.To test a translation on Windows, use cp RGui-ll.gmo ../share/locale/ll/LC_MESSAGES/RGui.moand then startup RGui.exe in an appropriate locale, or set LANGUAGE=llon the command line. (All RGui-*.gmo files will installed to theright places when 'make -f Makefile.win' is run in this directory,which is part of the main 'make' process.)To re-make RGui.pot and all the translations use 'make update-RGui'.