Quoting Neil Williams <[EMAIL PROTECTED]>:
> > > Should the strings be translatable?
> > > #define AS_STRING_CASE(name, value) \
> > > case name: return _(#name);
> > > instead of return #name?
> >
> > NOT AT ALL! Enum values are source-code level things (and the string
> values
> > for these as well), but gettext translations are for user-visible things.
>
> OK, I may investigate methods of using user-visible translatable strings
> instead of a direct mapping, it could be useful in some situations. The
> Doxygen problem is the hardest one to solve.
You never want to translate non-user-input data in the data file. The problem
is that if you change locales between the writer and reader you no longer
retain the ability to read the data file. I'll note that some QIF
implementations have this problem, where they write out !Tipo:Banco instead of
!Type:Bank. It means you can't read in this data file if you're in a French
locale.
> Thanks for the comments.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
