$value = $contact_row[0];
    $contact_row[1] = _($contact_row[1]);   //   this line is added
    $descr = $opts['format']==null ?  $contact_row[1] :

Then when you manually put the translations in the PO file and make a new MO file your combo boxes will also be translated.

Example:

The first 2 entries in the chart_types table are "Current Assets" and "Inventory Assets".

Then add the following to your PO file:

#: from table chart_types
msgid "Current Assets"
msgstr "Omløpsmidler"

#: from table chart_types
msgid "Inventory Assets"
msgstr "Anleggsmidler"

The translation shown above is Norwegian, but you put the translation in your own language.

I have made a file of most of the database entries that should be translated and will try to make it available for all to download.

Check the 3166/3167 Mercurial for sprintf for example workarounds. Otherwise the litteral varable name will be parsed instead. Make sure every possible variable value has a translation in the .po/.mo files.

The lines (they seem okay in hindsight):

    label_cell(_($myrow["name"]));//   here the _() is put
    label_cell(_($parent_text));//   here the _() is put
    label_cell(_($bs_text));//   here the _() is put

should possibly be (%d for numbers and %s for strings) where every possible value of :

    label_cell(sprintf(_("%s"), $myrow["name"]));//   here the _() is put
    label_cell(sprintf(_("%s"), $parent_text));//   here the _() is put
    label_cell(sprintf(_("%s"), $bs_text));//   here the _() is put

Even this may not work as intended since %s will be parsed as is and there is no preceeding or succeeding text to be translated. An eval() may have to be done on a cocatenated string containing the variable.

Try the following as well:

    label_cell(_(sprintf("%s", $myrow["name"])));//   here the _() is put
    label_cell(_(sprintf("%s", $parent_text)));//   here the _() is put
    label_cell(_(sprintf("%s", $bs_text)));//   here the _() is put

Maybe a check to see if $parent_text is empty before translation would be all that is needed:

    label_cell($empty(trim($parent_text)) ? "" : _($parent_text));//   here the _() is put

The 2 easy ones are found in the "while" statement starting around line 133 in the file /frontaccounting/gl/manage/gl_account_types.php.
In the label_cell function calls around line 150 the _() are inserted as shown below. When the correct translations are inserted in the PO file, they are translated correctly.
I found that the ($parent_text) could not be empty. You have to assign it some value. Otherwise it returns the whole PO file.

while ($myrow = db_fetch($result))
{

    alt_table_row_color($k);

    $bs_text = get_account_class_name($myrow["class_id"]);
    $parent_text = "-";
    if ($myrow["parent"] == '-1')
    {
        $parent_text = "-";
    }
    else
    {
        $parent_text = get_account_type_name($myrow["parent"]) . " ";
    }

    label_cell($myrow["id"]);
    label_cell(_($myrow["name"]));//   here the _() is put
    label_cell(_($parent_text));//   here the _() is put
    label_cell(_($bs_text));//   here the _() is put
    inactive_control_cell($myrow["id"], $myrow["inactive"], 'chart_types', 'id');
    edit_button_cell("Edit".$myrow["id"], _("Edit"));
    delete_button_cell("Delete".$myrow["id"], _("Delete"));
    end_row();
}
--------------------------------------------------------------------------------------------------------------------------------------------
The 2 combo boxes at the bottom of the page are more difficult to handle. I have not managed to find out where to introduce the _(). I have tried several places in the "gl_account_types.php" file and in the ui_lists.php file and the gl_db_account_types.inc file but I cannot find out where to put them.

Do you have any suggestions where to put the _()?

As you see recipe is simple, but you need to spent a couple of days to be satisfied.

Janusz

msgid "Payment due within 10 days"
msgstr "whatever it is in your language"

and whenever this phrase appeared in the combo boxes it would be translated to your language.

So my question is: Is there a way to fix this?

The Wiki pages for Language and Translation String updation would be useful.

At least this is my experience.

/Joe

Simply translate them inside FrontAccounting.

The chart of Accounts script should have been translated from the beginning.

Joe