Ricardo, Thanks for the offer to help translate Dogtag! You mention Dogtag 1.3 -- thats a very old version! We are working on version 10.2. Unfortunately, Dogtag is not well set up right now for internationalization. There are plans to improve this, but they will likely fall in the 10.3 time frame. Still, there is a lot that can be done. 1. Server code: some attempt has been made to internationalize some of the server code. As a result, there are some properties files with string definitions: base/server/cmsbundle/src/UserMessages.properties base/server/cmsbundle/src/LogMessages.properties dogtag/console-ui/src/CMSAdminRS.properties There are probably other properties files in the console source code. Translated versions of those files would have extension .es_ES. 2. Dogtag 10 has many man pages that can be translated, especially for pkispawn, pkidestroy etc. 3. The Javascript in the UI is for the most part, not set up for translation. Externalizing the strings is what is planned for 10.3. If you want to get a jump on that though, the way to do it is pretty straightforward. See: ./base/ca/shared/webapps/ca/ee/ca/ProfileList.template You will notice that the strings have been externalized to a properties file: dogtag/common-ui/shared/ca/ee/ProfileList.properties Translating that UI page would simply be a matter of creating a translated properties file: dogtag/common-ui/shared/ca/ee/ProfileList.properties_es_ES Unfortunately, this is the only UI page for which this has been done so far. We need to do a similar string externalization (and adding the jquery bit on top) for all the template files. We've started a wiki page http://pki.fedoraproject.org/wiki/Internationalization to start tracking this effort. Let us know what you are interested in working on! Thanks! Ade On Fri, 2014-05-02 at 20:11 -0500, Ricardo Alexander Alexander Perez Ricardez wrote: