[Koha-bugs] [Bug 25067] Move PO file manipulation code into gulp tasks

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25067

--- Comment #41 from Julian Maurice <julian.maurice at biblibre.com> ---
(In reply to Katrin Fischer from comment #39)
> Hm, I think I don't understand what you are referring to as source files.
> Will this work for tarball installations, packaging installations and git
> based installations alike? I believe we don't always have 2 copies of the
> files? 
> I am worried this could break things for some of those?
By source files I mean the files that are committed in the git repo. All files
that you have directly after a git clone.
IMO create and update should not be run on "installations", but directly on
files inside the git repository, independently of any installation.
'create' and 'update' are essentially developer tools to manage PO files within
the git repository.

> I think it's a wrong assumption that update and create will only be used by
> our translation manager or developers. I believe libraries have for example
> changed terms in po files and similar for the normal GUI.
I think that we should not support nor encourage that. Even if it's "only"
translations, it's still a fork of Koha. Everyone is free to do that, of
course, but then they are on their own to maintain their changes.
If translations are wrong, they should be fixed on translate.koha-community.org

> But I'd be interested in your workflow for separate po for other use cases.
> :)
Basically, for each client-specific development that adds new strings, we
create a PO file in misc/translator/po/fr-FR-<category>-<ticket-id>.po
containing all the new strings and their translation. When we need to update
fr-FR templates we call a script that "concatenates" (msgcat) all
fr-FR-<category>-*.po and runs misc/translator/translate install

-- 
You are receiving this mail because:
You are watching all bug changes.