Hi, Hm, I agree that the way we currently do it is not very nice and that there is certainly room for improvement. But as long as we have no better solution, I would also like to avoid breaking the non-English installer files.
I could bring up quite a few of examples where forgetting to add new content to the other installers has broken functionality in installations using those. So I'd rather have something there in English, than getting a Perl error message in Koha later with no idea what is missing and how it has to be named/added correctly etc. I am not sure how hard it would be to generate po files for the installer's SQL files. I think some like the MARC21/UNIMARC frameworks would be really good candidates. Currently we have patches pending to update the English MARC21 frameworks with all changes to the standard and using po files could save us a lot of work in the near future. Salvaging the existing translations would also be something to think about here. Some other tables/files would probably be more problematic or require a different solution: The SQL files for the bidi/language code tables should really not be on top level. They are multilingual anyway and should not exist in the language specific directories. (I think there is already a bug for that, even if I can't find it right now) As line breaks don't translate well with pootle, the notices could be a bigger problem here. The idea to have the English files as base and only update and maybe amend them from the non-English installer files sounds good to me. Hope this makes some sense, Katrin > -----Original Message----- > From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel- > boun...@lists.koha-community.org] On Behalf Of Galen Charlton > Sent: Friday, June 14, 2013 4:33 PM > To: Marcel de Rooy > Cc: koha-devel@lists.koha-community.org Devel > Subject: Re: [Koha-devel] QA: Language material in install/mysql/data > > Hi, > > On Fri, Jun 14, 2013 at 1:04 AM, Marcel de Rooy <m.de.r...@rijksmuseum.nl> > wrote: > > A good improvement recently was the approach for systempreferences. > > They are inserted with the general sysprefs.sql in the root folder, > > and optionally updated by a translation in the language folder. So the > > pref comes always in, translation depending on others. (I think we > > should extend that approach to the other files now: insert in English, > > only update translatable things in the other languages. Example: only > > update name, title and content for a notice, only liblibrarian and > > libopac for frameworks, etc. ) > > I think this is a good idea. With some more work, there's also no reason > why the text couldn't be extracted into .pot files for exposure to the > normal translation tools. > > > For some folders there are already 'informal' maintainers. Couldn't we > > just formalize that someone can step forward to maintain such a folder > > and let devs just propose changes to the general files and/or the en- > folder ? > > Sure, if folks are willing to step up and take on responsibility for a > localization. Eventually, however, all such strings ought to be handled by > the existing translation framework. Once support for that is in place, the > main purpose for language-specific SQL scripts would be setting > localization-dependent configuration defaults (e.g., like the fr-FR > unimarc_standard_system_preferences.sql). > > One thing that I think we should ensure, however, is that if we adopt this > idea, that correct functioning of Koha should not depend on any action by > localization maintainers. In other words, regardless of which language you > pick during installation, one should always have a functioning system that > includes the necessary default values. One way to do that might be to move > the globally mandatory bits of installer/data/mysql/en/mandatory into a new > installer/data/mysql/global/mandatory directory that always gets run during > installation. > > Regards, > > Galen > -- > Galen Charlton > Manager of Implementation > Equinox Software, Inc. / The Open Source Experts > email: g...@esilibrary.com > direct: +1 770-709-5581 > cell: +1 404-984-4366 > skype: gmcharlt > web: http://www.esilibrary.com/ > Supporting Koha and Evergreen: http://koha-community.org & http://evergreen- > ils.org _______________________________________________ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : http://git.koha- > community.org/ bugs : http://bugs.koha-community.org/ > _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
