From: Duncan B. <dun...@su...> - 2007-06-28 08:02:39
|
I've been tidying up the .pot files for kupu, and it has been suggested that I should add kupu's translation files to the PloneTranslations product so that people don't need access to codespeak when maintaining the .po files. Accordingly I've moved Kupu's .pot and .po files into PloneTranslations/trunk/i18n/kupu and Kupu now uses svn:externals to populate its own i18n directory. I'm not sure if that is the best location: if not then someone please suggest a better location and I'll move them. As part of the tidy up, I split the existing 2 i18n domains into 3. "kupu" contains the translatable strings used as part of the normal kupu usage (mostly Plone but it includes some used only for other versions of kupu). "kupuconfig" contains translatable strings used by Kupu's Plone configuration screens. "kupupox" (the new domain) contains translatable strings used in Javascript: these are not currently used in Plone at all (most of them you will never see, and those which can occur do not get translated in Plone). |