Author Topic: Translating parts of civi offline (Read 1502 times)

dragontree · February 08, 2010, 02:57:05 am

Some time ago I asked if there was a way to translate only a part of Civi. The answer was no.
Now I'm gonna rephrase my question

Does anybody know a .po file editor (like Poedit) which would show the strings based on the sources? Basically this would show the list of all files that contain strings to be translated.

That way I could skip the files for contributions or whatever parts I don't need.

Donald Lobo · February 08, 2010, 08:14:20 am

does it make sense for civicrm to split the translation file for each directory seperately? main issue will be what about common strings? might be somethign we want to mov towards as we add more modules

lobo

dragontree · February 08, 2010, 01:53:40 pm

I'm not to familiar how the gettext translation works but theoretically common strings would not be a problem if the whole translation system uses one source file, as it does now afaik.

An example:

Code: [Select]

#: templates/CRM/Mailing/Form/Component.tpl
#: templates/CRM/Mailing/Page/Component.tpl
#, fuzzy
msgid "New Mailing Component"
msgstr "Uus postituse komponente"

So the string "New Mailing Component" would be present in to separate files. But if the source is the same then if the string is changed in one file it would be changed in the other also.

Although the example would only be valid if there were only one person translating that string at a certain time.

Anyways, I don't really have any good suggestions at the moment how it would work, but the possibility of translating modules separately does seem appealing.

Piotr Szotkowski · February 15, 2010, 05:47:24 am

We currently break all of the CiviCRM strings into the following files: civicrm-core.pot (strings from core files), civicrm-helpfiles.pot (string from .hlp tempaltes), civicrm-menu.pot (menu entries) and civicrm-modules.pot (string from non-core Civi* modules).

The -core and -modules split is based on source subdirectories of the CRM and templates/CRM directories:

Code: [Select]

$modules  = array('Case', 'Contribute', 'Event', 'Grant', 'Mailing', 'Member', 'Pledge');
$excluded = array('Bridge', 'Project', 'Touchstone');

– this tends to work most of the time.

Would it make sense for the above to be split on a per-module basis (i.e., separate file for each module)?

dragontree · February 18, 2010, 02:12:33 am

Splitting it based on modules sounds good. Although probably not that important as I originally thought.
It was important for me as I only needed to translate 2 modules for now. If you end up translating everything it really doesn't matter how you do it.

CiviCRM Community Forums (archive)

News:

Author Topic: Translating parts of civi offline (Read 1502 times)

dragontree

Translating parts of civi offline

Donald Lobo

Re: Translating parts of civi offline

dragontree

Re: Translating parts of civi offline

Piotr Szotkowski

Re: Translating parts of civi offline

dragontree

Re: Translating parts of civi offline