Bug 34856 - Move strings in messages.po back into their original file (or move everything into messages.po)
Summary: Move strings in messages.po back into their original file (or move everything...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: I18N/L10N (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-20 19:24 UTC by Caroline Cyr La Rose
Modified: 2024-03-05 21:54 UTC (History)
2 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

Note You need to log in before you can comment on or make changes to this bug.
Description Caroline Cyr La Rose 2023-09-20 19:24:20 UTC
With all the developments that have been done on translatability, a lot of strings have been moved from staff-prog.po and opac-bootsrap.po to a new file called messages.po.

I personally don't understand the purpose of this file. For example, why are some OPAC strings in opac-bootstrap.po and others in messages.po? Why are they not all in messages.po or all in opac-bootstrap.po?

We could move opac strings back from messages.po back into opac-bootstrap.po and staff interface strings back into staff-prog.po.

Or we could move everything into a single .po file.

There are good arguments on both sides, and I am open to discussing the various options. I just want it to be less confusing for people who are translators and don't necessarily know the technical stuff behind the creation of these files.

P.S. Note that I'm not talking about messages-js.po which is an entirely different thing.