Koji, I think it will be very confusing for the users if the customized name reads "General" in this dialog, and then is displayed in the chosen language instead. What I propose is that the default values are translated, so if the user opens this dialog it will be displayed not as "General" but as whatever it is translated into. Then, if the user changes the name to something else, this choice will not be translated, so there is no risk of confusion.
To put it simply, we don't add translation of the customizable tab names, but we make sure the default names are in the user's chosen language. -- Morten 2011/5/17 K. Yokota <yokot...@gmail.com>: >> reserved words. As a candidate, I chose to add "[[CUSTOM_TAB]]" to >> those keywords which is unlikely to become necessary for users. > > I noticed those default keywords also appear in "Setting General > Field" dialog, so we may not have to attach such reserved words at > all, because there is no reason to distinguish default "General" and > customized "General". > > Koji > ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Jabref-devel mailing list Jabref-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jabref-devel
