Summary: | message type in messaging table not translatable | ||
---|---|---|---|
Product: | Koha | Reporter: | Katrin Fischer <katrin.fischer> |
Component: | I18N/L10N | Assignee: | Katrin Fischer <katrin.fischer> |
Status: | CLOSED FIXED | QA Contact: | Bugs List <koha-bugs> |
Severity: | enhancement | ||
Priority: | PATCH-Sent (DO NOT USE) | CC: | gmcharlt |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Attachments: |
screenshot of messaging table in opac
screenshot Proposed patch |
Description
Chris Cormack
2010-05-21 01:13:40 UTC
Created attachment 2194 [details] screenshot I solved this by translating the .sql files (http://lists.koha-community.org/pipermail/koha-patches/2010-May/011998.html). The database field message_attributs.message_name is only varchar(20). I think this field should be longer to make it easier to fit translations in. The field is also shown to patrons in the OPAC and it should be possible to put an easily understandable description in it. Created attachment 2220 [details]
Proposed patch
Patch changes message_attributes.message_name from varchar(20) to varchar(40).
Patch pushed. Please test and close. Confirm fixed. |