Hi Katrin,
I was thinking it would be good to change the structure to make it easier for translators, although that could also make it significantly harder for libraries to add missing languages too. I have a library that wanted to add Bosnian and Maltese, so I was able to just give them some SQL queries to do the trick. I suppose another way of doing it would be to have a database table of language codes with the native name and then use per-language templates to provide the translated names of the languages. I’ll comment on the Bug, although I don’t imagine this will change any time soon… David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Koha-devel <koha-devel-boun...@lists.koha-community.org> On Behalf Of Katrin Fischer Sent: Saturday, 24 April 2021 6:45 PM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Deleting entries from language_descriptions Hi David, it seems likely that these are unused. It would be nice to update our structure there, especially for easier translations. Bernardo has been working on something for this in the past: <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12017> Bug 12017 - Move language description out of database Katrin On 23.04.21 04:38, dc...@prosentient.com.au <mailto:dc...@prosentient.com.au> wrote: Hi all, I was looking at how to add languages to the Languages drop down in the OPAC advanced search and went down an unpleasant C4::Languages rabbithole… But looking at language_descriptions, I’m wondering if perhaps we could delete the following data, as I imagine it’s very outdated and unused: MySQL [koha_kohadev]> select * from language_descriptions; +----------+----------+------+---------------------------------------+-----+ | subtag | type | lang | description | id | +----------+----------+------+---------------------------------------+-----+ | opac | i | en | OPAC | 1 | | opac | i | fr | OPAC | 2 | | opac | i | de | OPAC | 3 | | intranet | i | en | Staff Client | 4 | | intranet | i | fr | Client personnel | 5 | | intranet | i | de | Dienstoberfläche | 6 | | prog | t | en | Prog | 7 | | prog | t | fr | Prog | 8 | | prog | t | de | Prog | 9 | At the moment, it looks like adding a language requires manual SQL queries to language_subtag_registry, language_descriptions, and language_rfc4646_to_iso639. It’s a shame there is no native interface for updating it. I imagine a plugin could work out well for it, although I think for the library in mind they’ll probably just do a manual insert, as it’s not worth the development cost… David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/
