Translation Process : Installer and Javascript libraries improvements

From Koha Wiki

Jump to: navigation, search
Home
Home
Home
Home
Home
Koha > Technical > Development > RFCs
Koha > Technical > Development > RFCs > Koha components for RFCs > Aspects of multiple components RFCs > Internationalisation, Localisation, and Globalisation RFCs
Koha > Technical > Development > RFCs > Koha components for RFCs > Library System Modules RFCs > System Administration RFCs > Installation and Upgrade RFCs > Command-line installer RFCs
Koha > Technical > Development > RFCs > Koha components for RFCs > Library System Modules RFCs > System Administration RFCs > Installation and Upgrade RFCs > Web based installer RFCs
Koha > Technical > Development > RFCs > Koha version targeted RFCs > RFCs not targeted at a particular Koha version
  • In order to make tardists smaller, I propose to generate the translations with web installer or with command line installation. This would only require a new question making Makefile and install-code.pl would be done when all the cpan modules are installed.
    • tardist lighter And installation process lighter too, with only selected languages installed, which in My opinion is smarter and cool.
  • In order to make translation quicker and safer, we could/should place all the js libs into a common central place so that it could be shared at least by all the languages. A naive person would think it would be even better to share that between OPAC and intranet. But for security reason and the fact that both OPAC and Intranet can and MUST be able to be installed on two separate machines, it is not desirable.
  • Everything with packages, apt-cache search koha spanish:
    koha-l10n-es - integrated (physical) library management system -- Spanish language package
Personal tools