composed strings from multiple keys

example: templates/base/scripts/BxBaseMailBox.php:340

$aLanguageKeys = array
'back_inbox'       => _t( '_Back' ) . ' ' . _t( '_to' ) . ' ' . _t( '_Inbox' ),
'back_outbox'      => _t( '_Back' ) . ' ' . _t( '_to' ) . ' ' . _t( '_Outbox' ),
'back_trash'       => _t( '_Back' ) . ' ' . _t( '_to' ) . ' ' . _t( '_Trash' ),

Composing language keys does not work in a multi language system. _to in 'mail to' may be a different word than _to in 'back to' in another language.

I don't know if there are other cases like this.

There are two 'to' keys '_To' and '_to' (in system). Could you explain the difference in usage between them to clarify how to translate them.

That is a strange way to handle a language string.  There really is  no need to split those into 3 separate keys.  It makes me wonder what they were thinking when they did it.

I would assume that _To translates to 'To' which would be capitalized for use in the beginning of a sentence, whereas _to would translate to 'to', for use mid-sentence.

If it's a problem, you can edit the source file to use your own keys, ie:

                'back_inbox'       => _t( '_Back_to_inbox' ),
                'back_outbox'      => _t( '_Back_to_outbox' ),
                'back_trash'       => _t( '_Back_to_trash' ),

If they did this in one place, odds are they did all over the place.

 But they both have value 'to'.

If they did this in one place, odds are they did all over the place.

That's what I worry about and it's why I don't try to fix it myself although it's in a template file.

Actually, a search of the source files for ". _t( '_to' ) ." indicates that this is the only instance of this... at least for the word "to".  They may have done it for other common words though.

Thank you for pointing this out:

http://www.boonex.com/trac/dolphin/ticket/3374