Translatable strings in .h file -- best way to resolve?

[Mike Alexander]

--On March 18, 2010 11:04:25 AM -0400 Derek Atkins <warlord at MIT.EDU> 
wrote:

>> (export gnc:*business-label* gnc:*company-name* gnc:*company-addy*
>> gnc:*company-id*
>>             gnc:*company-phone* gnc:*company-fax* gnc:*company-url*
>>             gnc:*company-email* gnc:*company-contact*)
>>
>> (define gnc:*option-section-accounts* (_ OPTION-SECTION-ACCOUNTS))
>> (define gnc:*option-name-trading-accounts* (_ 
OPTION-NAME-TRADING-ACCOUNTS))
>>
>> (export gnc:*option-section-accounts*
>> gnc:*option-name-trading-accounts*)
>>
>> (define gnc:*option-section-budgeting* (_ OPTION-SECTION-BUDGETING))
>> (define gnc:*option-name-default-budget* (_ 
OPTION-NAME-DEFAULT-BUDGET))
>>
>> (export gnc:*option-section-budgeting*
>> gnc:*option-name-default-budget*)
>
> These calls would define these options as the translated versions of
> these strings.  I'm not sure this is correct.  So long as the OPTION
> strings are defined as N_ in the C code you don't need to translate
> them here unless you ONLY want access to the translated version of the
> string.

I really don't think you want the "(_" on these.  I think that will 
cause the KVP keys to be translated too.

          Mike