Bug 26347 - Wrong publication pattern locale on months
Summary: Wrong publication pattern locale on months
Status: RESOLVED DUPLICATE of bug 30035
Alias: None
Product: Koha
Classification: Unclassified
Component: Serials (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low minor
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-02 07:22 UTC by Hugo Agud
Modified: 2022-07-16 11:43 UTC (History)
1 user (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

Note You need to log in before you can comment on or make changes to this bug.
Description Hugo Agud 2020-09-02 07:22:34 UTC
Configuring publication patterns with locale ca-ES we have discovered that months are wrong translated

january = gener and now it is translating = de gener
februry = febrer and now it is translating = febrer
march.....etc

locale should use just months not full name
Comment 1 Katrin Fischer 2020-10-19 16:33:21 UTC
Hi Hugo, I am not sure I understand the issue. Can you share a screenshot of your advanced pattern and how they should show up?
Comment 2 Hugo Agud 2020-11-04 08:15:48 UTC
Let me give you an example:

When we create a pattern using months, the user expect just months names: january, february, march...etc, when using locate = ca-ES, we are not getting months, we are getting:

de gener (of january) it should be just 'gener' (january)
de febrer (of february) it should be just 'february' (february)
de març (of march) it should be just 'march' (march)

Example:
Wrong: New england journal of medicine vol:23 issue:333 of january 2020
Right: Wrong: New england journal of medicine vol:23 issue:333 january 2020

This is happeing at least locat ca-ES
Comment 3 Katrin Fischer 2020-11-04 08:28:32 UTC
The translations don't appear to be in translate.koha-community.org - I believe we are using a Perl library to generate these. It might be wrong there.
Comment 4 Katrin Fischer 2022-07-16 11:43:25 UTC
*** This bug has been marked as a duplicate of bug 30035 ***