Hi Rubén,
we have the AdvancedSearchLanguages system preference to allow
configuration of the languages shown in the pull down. You enter the
language codes for the languages you want to show - so it's easy and
adding a new language doesn't change existing installations.
Katrin
On 22.08.2018 15:38, Rubén Fernández Asensio wrote:
Thanks Katrin!
I think the "IGNORE" version isn't necessary, it may be related to the
case of collision between Georgian and Kannada codes in the example
you pointed to.
I'll try running the SQL command in my own test server.
Also, what code would it be to delete a language from the list?
Given that there are 7000 languages in the world, if only 1000 are
written, that's still unwieldly for a drop-down menu... That's why I'm
unsure about submitting a bug report and having Esperanto added to the
default interface. It should be easier to customise this though.
Ruben
El 22/08/18 a les 07:48, Katrin Fischer ha escrit:
Hi Rubén,
first and second look the same to me? It looks about right. I just
ran the SQL in my test database and Esperanto showed up in the
language pull down.
Katrin
On 20.08.2018 09:34, Rubén Fernández Asensio wrote:
I'd rather file a bug, but adding Esperanto (and other languages)
has already been proposed:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18493
Why is the status of that bug "Failed QA"?
I suspect the only way of having that bug fixed and Esperanto added
to Koha Advanced Search may be providing a solution myself...
OK, let's say I type something like this:
INSERT INTO language_subtag_registry( subtag, type, description,
added) VALUES ( 'eo', 'language', 'Esperanto','2018-08-20');
INSERT INTO language_rfc4646_to_iso639(rfc4646_subtag,iso639_2_code)
VALUES ( 'eo', 'epo');
INSERT INTO language_descriptions(subtag, type, lang, description)
VALUES ( 'eo', 'language', 'eo', 'Esperanto');
INSERT INTO language_descriptions(subtag, type, lang, description)
VALUES ( 'eo', 'language', 'en', 'Esperanto');
And this:
INSERT IGNORE INTO language_subtag_registry( subtag, type,
description, added) VALUES ( 'eo', 'language',
'Esperanto','2018-08-20');
INSERT IGNORE INTO
language_rfc4646_to_iso639(rfc4646_subtag,iso639_2_code) VALUES (
'eo', 'epo');
INSERT IGNORE INTO language_descriptions(subtag, type, lang,
description) VALUES ( 'eo', 'language', 'eo', 'Esperanto');
INSERT IGNORE INTO language_descriptions(subtag, type, lang,
description) VALUES ( 'eo', 'language', 'en', 'Esperanto');
What should I do next?
El 20/08/18 a les 08:09, Katrin Fischer ha escrit:
Example:
INSERT IGNORE INTO language_descriptions(subtag, type, lang,
description) VALUES ( 'ka', 'language', 'ka', 'ქართული');
For translations:
INSERT IGNORE INTO language_descriptions(subtag, type, lang,
description) VALUES ( 'ka', 'language', 'fr', 'Géorgien');
...
You could also file a bug on bugzilla about adding Esperanto to the
list for new versions.
Katrin
_______________________________________________
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha