Custom fields design doc

[Sean McAfee]

I wrote:
>Gervase Markham <gerv at mozilla.org> wrote:
>>Sean McAfee wrote:
>>> field_id integer auto_increment primary key,
>>> field_name tinytext not null,
>>> display_name tinytext not null,

>>If this isn't in templates, it can't be localised - i.e. you can only 
>>have a single value, no matter how many nationalities of people use your 
>>Bugzilla. I still think we should have a mechanism where it uses 
>>field_name to begin with, and you then define display names in templates 
>>on a per-language basis...

>By this time, my desire to avoid requiring the admin to twiddle templates is
>well-known.  Hmmm.  OK, how about storing display names in a table like
>this:
[snip]

OK, I had a better idea.  Leave the display_name in custom_fields as
I originally proposed.  The name in the table represents the field's
display name in a default locale, which can be a new Bugzilla parameter.
Those who want to provide alternate names for different locales can
override the default on a per-locale basis in an appropriate template.
This way, those who don't need to support multiple locales don't need to
edit templates, and those who do can do so using the mechanism you
suggested.

How's that?


-- 
Sean McAfee -- etzwane at schwag.org