Bug 27540 - Allow local definition of gender options
Summary: Allow local definition of gender options
Status: RESOLVED DUPLICATE of bug 23609
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-24 20:49 UTC by Andrew Fuerste-Henry
Modified: 2021-06-21 20:52 UTC (History)
5 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Fuerste-Henry 2021-01-24 20:49:51 UTC 
Bug 25364 added an "other" option for gender, which is great!
But why are the gender options hardcoded to begin with? We allow each install to define their own options for borrower titles. We should do the same for gender (either in a dedicated syspref as we have for title or in an authorized value).
Comment 1 Katrin Fischer 2021-01-24 21:20:58 UTC 
I think one reason was that the authorised values are still not translatable :( Which means it makes it really hard to work this out for multi-language installation to always display nicely.
Comment 2 David Cook 2021-01-24 23:03:36 UTC 
(In reply to Katrin Fischer from comment #1)
> I think one reason was that the authorised values are still not translatable

Do we have a bug open for that?

I imagine that the way to fix that would be to add a locale column? Initially we could default to English but build up support for passing in locales.
Comment 3 Katrin Fischer 2021-01-25 12:16:38 UTC 
(In reply to David Cook from comment #2)
> (In reply to Katrin Fischer from comment #1)
> > I think one reason was that the authorised values are still not translatable
> 
> Do we have a bug open for that?
> 
> I imagine that the way to fix that would be to add a locale column?
> Initially we could default to English but build up support for passing in
> locales.

bug 20307
Comment 4 David Cook 2021-01-26 23:09:20 UTC 
(In reply to Katrin Fischer from comment #3)
> (In reply to David Cook from comment #2)
> > (In reply to Katrin Fischer from comment #1)
> > > I think one reason was that the authorised values are still not translatable
> > 
> > Do we have a bug open for that?
> > 
> > I imagine that the way to fix that would be to add a locale column?
> > Initially we could default to English but build up support for passing in
> > locales.
> 
> bug 20307

Yikes bug 20307 and bug 24975 look a bit stuck.
Comment 5 Andrew Fuerste-Henry 2021-06-21 20:52:05 UTC 

*** This bug has been marked as a duplicate of bug 23609 ***