From Pasi.Kallinen at pttk.fi Mon Dec 2 08:37:02 2013 From: Pasi.Kallinen at pttk.fi (Kallinen Pasi) Date: Mon, 2 Dec 2013 07:37:02 +0000 Subject: [Koha-devel] Translation annoyances Message-ID: <25DCE6EB7C29A24A8ABC913AEB608972BAA1E06B@KS0105.ad.pohjoiskarjala.net> Hello. I've been translating Koha to Finnish for a bit, and I'm really starting to hate some of the automagically generated msgid's. 1) String concatenation is BAD. For example, this line of code: var disabledForCurrent = _("Disabled for") + ' ' + $branch; turns into this translatable string: msgid "Disabled for" For some languages this is very hard to translate without sounding stupid or just plain wrong. jQuery has some string placeholder support for javascript, so Koha really should be using those instead! The example above would turn into: var disabledForCurrent = _("Disabled for {0}"); msgid "Disabled for {0}" 2) Consistency would be good. msgid "EAN:" msgid "EAN: " msgid "EAN :" 3) Sentences should not be cut in pieces. msgid "Please" msgid "upload" msgid "one." The "upload"-text is a link in the sentence. Ideally this should be: msgid "Please %supload%s one." 4) Is it a verb or a noun? msgid "Copy" 5) The wiki-like help texts should be in separate po-file. The help texts inflate the staff UI po-file immensely, and the help translation is not quite as critical as the UI. Having all the help texts interspersed between all the actually important strings is irritating. 6) Translation is not programming. Replace all Template Toolkit code with placeholders. For example msgid "Cancel [% IF TransferWhenCancelAllWaitingHolds %]and Transfer [% END %]All" and msgid "Cancel hold and return to : [% overloo.branchname %]" 7) Exclude URLs. Those are not content that should be translatable. -- Yst?v?llisin terveisin Pasi Kallinen ICT-asiantuntija p. 0400-139747 pasi.kallinen at pttk.fi L?nsikatu 15 80110 Joensuu Pohjois-Karjalan Tietotekniikkakeskus Oy - www.pttk.fi From chrisc at catalyst.net.nz Mon Dec 2 08:42:32 2013 From: chrisc at catalyst.net.nz (Chris Cormack) Date: Mon, 2 Dec 2013 20:42:32 +1300 Subject: [Koha-devel] Translation annoyances In-Reply-To: <25DCE6EB7C29A24A8ABC913AEB608972BAA1E06B@KS0105.ad.pohjoiskarjala.net> References: <25DCE6EB7C29A24A8ABC913AEB608972BAA1E06B@KS0105.ad.pohjoiskarjala.net> Message-ID: <20131202074232.GJ24930@rorohiko.wgtn.cat-it.co.nz> * Kallinen Pasi (Pasi.Kallinen at pttk.fi) wrote: > Hello. > > I've been translating Koha to Finnish for a bit, and I'm really starting to hate some of the automagically generated msgid's. > > 1) String concatenation is BAD. > For example, this line of code: > var disabledForCurrent = _("Disabled for") + ' ' + $branch; > turns into this translatable string: > msgid "Disabled for" > > For some languages this is very hard to translate without sounding stupid or just plain wrong. jQuery has some string placeholder support for javascript, so Koha really should be using those instead! > The example above would turn into: > > var disabledForCurrent = _("Disabled for {0}"); > msgid "Disabled for {0}" > > > 2) Consistency would be good. > msgid "EAN:" > msgid "EAN: " > msgid "EAN :" > > > 3) Sentences should not be cut in pieces. > msgid "Please" > msgid "upload" > msgid "one." > > The "upload"-text is a link in the sentence. Ideally this should be: > msgid "Please %supload%s one." > > > 4) Is it a verb or a noun? > msgid "Copy" > > > 5) The wiki-like help texts should be in separate po-file. The help texts inflate the staff UI po-file immensely, and the help translation is not quite as critical as the UI. Having all the help texts interspersed between all the actually important strings is irritating. > > > 6) Translation is not programming. Replace all Template Toolkit code with placeholders. > For example > msgid "Cancel [% IF TransferWhenCancelAllWaitingHolds %]and Transfer [% END %]All" > and > msgid "Cancel hold and return to : [% overloo.branchname %]" > > > 7) Exclude URLs. Those are not content that should be translatable. > Great ideas, I will be more than happy to do sign off on your patches implementing them. Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand From maolins at gmail.com Mon Dec 2 08:47:28 2013 From: maolins at gmail.com (Anthony Mao) Date: Mon, 2 Dec 2013 15:47:28 +0800 Subject: [Koha-devel] Translation annoyances In-Reply-To: <25DCE6EB7C29A24A8ABC913AEB608972BAA1E06B@KS0105.ad.pohjoiskarjala.net> References: <25DCE6EB7C29A24A8ABC913AEB608972BAA1E06B@KS0105.ad.pohjoiskarjala.net> Message-ID: Hi Kallinen, I can not but agree with you. 2013/12/2 Kallinen Pasi : > Hello. > > I've been translating Koha to Finnish for a bit, and I'm really starting to hate some of the automagically generated msgid's. > > 1) String concatenation is BAD. > For example, this line of code: > var disabledForCurrent = _("Disabled for") + ' ' + $branch; > turns into this translatable string: > msgid "Disabled for" > > For some languages this is very hard to translate without sounding stupid or just plain wrong. jQuery has some string placeholder support for javascript, so Koha really should be using those instead! > The example above would turn into: > > var disabledForCurrent = _("Disabled for {0}"); > msgid "Disabled for {0}" > > > 2) Consistency would be good. > msgid "EAN:" > msgid "EAN: " > msgid "EAN :" > > > 3) Sentences should not be cut in pieces. > msgid "Please" > msgid "upload" > msgid "one." > > The "upload"-text is a link in the sentence. Ideally this should be: > msgid "Please %supload%s one." > > > 4) Is it a verb or a noun? > msgid "Copy" > > > 5) The wiki-like help texts should be in separate po-file. The help texts inflate the staff UI po-file immensely, and the help translation is not quite as critical as the UI. Having all the help texts interspersed between all the actually important strings is irritating. > > > 6) Translation is not programming. Replace all Template Toolkit code with placeholders. > For example > msgid "Cancel [% IF TransferWhenCancelAllWaitingHolds %]and Transfer [% END %]All" > and > msgid "Cancel hold and return to : [% overloo.branchname %]" > > > 7) Exclude URLs. Those are not content that should be translatable. > > > -- > Yst?v?llisin terveisin > > Pasi Kallinen > ICT-asiantuntija > > p. 0400-139747 > pasi.kallinen at pttk.fi > L?nsikatu 15 > 80110 Joensuu > > Pohjois-Karjalan Tietotekniikkakeskus Oy - www.pttk.fi > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Wishing you all the best. . . . Anthony Mao ??? ?886 2 29052334 (voice) + 886 2 29017405 (FAX) From bargioni at pusc.it Mon Dec 2 10:39:59 2013 From: bargioni at pusc.it (Stefano Bargioni) Date: Mon, 2 Dec 2013 10:39:59 +0100 Subject: [Koha-devel] Koha 3.12.x and VIAF Message-ID: <80759925-E551-4D9C-8CF3-47E9BB86987C@pusc.it> Hi, Partha: thanks for detecting this bug. I'm going to correct the wiki page. In Koha 3.12 please comment out or delete lines // $($('ul.toolbar')[0]).append('\ //
\ // [X] \ //
\ // '); and substitute them with $('#authoritytabs').prepend('\
\ \
\ '); BTW, $('#bibliodescriptions').tabs({ active: 1 } ); belongs to the next entry "Change the default view on OPAC detail pages". Bye. Stefano Fridolin SOMERS wrote: > Hie, > > In wiki page, there is a final note : > " > In 3.12 use: > $('#bibliodescriptions').tabs({ active: 1 } ); > " > Did you test this ? > > Le 27/09/2013 13:33, Partha Mukhopadhyay a ?crit : >> Dear all, >> >> The JQuery script >> (http://wiki.koha-community.org/wiki/JQuery_Library#Add_VIAF_autosuggest_for_new_NAME_authorities) >> for integrating Koha with VIAF is not working in Koha 3.12.x (tested from 3.12.1 >> to 3.12.5). >> >> Pl. check.... > From Holger.Meissner at hs-gesundheit.de Mon Dec 2 12:08:36 2013 From: Holger.Meissner at hs-gesundheit.de (Holger Meissner) Date: Mon, 2 Dec 2013 11:08:36 +0000 Subject: [Koha-devel] Koha development server on Debian Wheezy Message-ID: <2C614FEEE2356A428DC65441E30302E06F5220@nero> Hi Fridolin, this is the configuration from when I tried to install without packages: # Koha Apache Configuration Directives #NameVirtualHost * ## OPAC ServerAdmin webmaster at debian DocumentRoot /root/koha/koha-tmpl ServerName debianLOL # ServerAlias opac.mydomain.com ScriptAlias /cgi-bin/koha/ "/root/koha/opac/" ScriptAlias /index.html "/root/koha/opac/opac-main.pl" ScriptAlias /opac-search.pl "/root/koha/opac/opac-search.pl" ScriptAlias /search "/root/koha/opac/opac-search.pl" ErrorLog /root/koha-dev/var/log/koha-opac-error_log # CustomLog /root/koha-dev/var/log/koha-opac-access.log combined # TransferLog /root/koha-dev/var/log/koha-opac-access.log SetEnv KOHA_CONF "/root/koha-dev/etc/koha-conf.xml" SetEnv PERL5LIB "/root/koha" SetEnv MEMCACHED_SERVERS "" SetEnv MEMCACHED_NAMESPACE "" # This syntax allows you to override a system preference # for a given virtual host. Use with caution! # You should add all the system preferences you override # in one or more vhosts to the environment variable # OVERRIDE_SYSPREF_NAMES for your staff intranet vhost # SetEnv OVERRIDE_SYSPREF_PrefName Value Options -Indexes # Secure internal stuff Order deny,allow Deny from all mod_gzip_on yes mod_gzip_dechunk yes mod_gzip_keep_workfiles No mod_gzip_can_negotiate yes mod_gzip_update_static No mod_gzip_temp_dir /tmp mod_gzip_minimum_file_size 512 mod_gzip_maximum_file_size 1000000 mod_gzip_maximum_inmem_size 1000000 mod_gzip_handle_methods GET POST mod_gzip_item_exclude reqheader "User-Agent: .*Mozilla/4\..*\[" mod_gzip_item_exclude mime ^image/.* mod_gzip_item_exclude rspheader Content-Type:image/* mod_gzip_item_include file \.js$ mod_gzip_item_include mime ^application/javascript$ mod_gzip_item_include mime ^application/x-javascript$ mod_gzip_item_include file \.php$ mod_gzip_item_include mime ^text/html$ mod_gzip_item_include file \.css$ mod_gzip_item_include mime ^text/css$ # Compress content with type html, text, and css, ... AddOutputFilterByType DEFLATE text/plain text/html text/xml text/css AddOutputFilterByType DEFLATE application/xml application/xhtml+xml application/rss+xml application/javascript application/x-javascript DeflateCompressionLevel 9 # Properly handle old browsers that do not support compression BrowserMatch ^Mozilla/4 gzip-only-text/html BrowserMatch ^Mozilla/4\.0[678] no-gzip BrowserMatch \bMSIE !no-gzip !gzip-only-text/html DeflateFilterNote Input instream DeflateFilterNote Output outstream DeflateFilterNote Ratio ratio LogFormat '"%r" %{outstream}n/%{instream}n (%{ratio}n%%)' deflate #properly handle requests coming from behind proxies Header append Vary User-Agent # Repeat this virtualhost stanza changing the following environment vars to # create multiple OPAC interfaces with custom css and/or search limits: # SetEnv OPAC_CSS_OVERRIDE mystyle.css # SetEnv OPAC_SEARCH_LIMIT branch:CODE # SetEnv OPAC_LIMIT_OVERRIDE 1 Options +FollowSymLinks ErrorDocument 400 /cgi-bin/koha/errors/400.pl ErrorDocument 401 /cgi-bin/koha/errors/401.pl ErrorDocument 403 /cgi-bin/koha/errors/403.pl ErrorDocument 404 /cgi-bin/koha/errors/404.pl ErrorDocument 500 /cgi-bin/koha/errors/500.pl # Rewrite Rules RewriteEngine On # Uncomment to turn on rewrite logging #RewriteLog /root/koha-dev/var/log/koha-opac-rewrite.log #RewriteLogLevel 1 RewriteCond %{QUERY_STRING} (.*?)(?:[A-Za-z0-9_-]+)=&(.*) #RewriteRule (.+) $1?%1%2 [N,R,NE] RewriteRule ^/bib/([^\/]*)/?$ /cgi-bin/koha/opac-detail\.pl?bib=$1 [PT] RewriteRule ^/isbn/([^\/]*)/?$ /search?q=isbn:$1 [PT] RewriteRule ^/issn/([^\/]*)/?$ /search?q=issn:$1 [PT] ## Intranet ServerAdmin webmaster at debian DocumentRoot /root/koha/koha-tmpl ServerName debian:8080 # ServerAlias intranet.mydomain.com ScriptAlias /cgi-bin/koha/ "/root/koha/" ScriptAlias /index.html "/root/koha/mainpage.pl" ScriptAlias /search "/root/koha/search.pl" Alias /plugin/ "/root/koha-dev/var/lib/plugins/" ErrorLog /root/koha-dev/var/log/koha-error_log # TransferLog /root/koha-dev/var/log/koha-access.log SetEnv KOHA_CONF "/root/koha-dev/etc/koha-conf.xml" SetEnv PERL5LIB "/root/koha" SetEnv MEMCACHED_SERVERS "" SetEnv MEMCACHED_NAMESPACE "" Options +FollowSymLinks # If you are overriding any system preferences, # list them in this variable so the preference editor # knows that they have been overridden. # SetEnv OVERRIDE_SYSPREF_NAMES "Pref1,Pref2,Pref3" ErrorDocument 400 /cgi-bin/koha/errors/400.pl ErrorDocument 401 /cgi-bin/koha/errors/401.pl ErrorDocument 403 /cgi-bin/koha/errors/403.pl ErrorDocument 404 /cgi-bin/koha/errors/404.pl ErrorDocument 500 /cgi-bin/koha/errors/500.pl Options -Indexes # Secure internal stuff Order deny,allow Deny from all mod_gzip_on yes mod_gzip_dechunk yes mod_gzip_keep_workfiles No mod_gzip_can_negotiate yes mod_gzip_update_static No mod_gzip_temp_dir /tmp mod_gzip_minimum_file_size 512 mod_gzip_maximum_file_size 1000000 mod_gzip_maximum_inmem_size 1000000 mod_gzip_handle_methods GET POST mod_gzip_item_exclude reqheader "User-Agent: .*Mozilla/4\..*\[" mod_gzip_item_exclude mime ^image/.* mod_gzip_item_exclude rspheader Content-Type:image/* mod_gzip_item_include file \.js$ mod_gzip_item_include mime ^application/javascript$ mod_gzip_item_include mime ^application/x-javascript$ mod_gzip_item_include file \.php$ mod_gzip_item_include mime ^text/html$ mod_gzip_item_include file \.css$ mod_gzip_item_include mime ^text/css$ # Compress content with type html, text, and css, ... AddOutputFilterByType DEFLATE text/plain text/html text/xml text/css AddOutputFilterByType DEFLATE application/xml application/xhtml+xml application/rss+xml application/javascript application/x-javascript DeflateCompressionLevel 9 # Properly handle old browsers that do not support compression BrowserMatch ^Mozilla/4 gzip-only-text/html BrowserMatch ^Mozilla/4\.0[678] no-gzip BrowserMatch \bMSIE !no-gzip !gzip-only-text/html DeflateFilterNote Input instream DeflateFilterNote Output outstream DeflateFilterNote Ratio ratio LogFormat '"%r" %{outstream}n/%{instream}n (%{ratio}n%%)' deflate #properly handle requests coming from behind proxies Header append Vary User-Agent # Rewrite Rules RewriteEngine On # Uncomment to turn on rewrite logging #RewriteLog /root/koha-dev/var/log/koha-intranet-rewrite.log #RewriteLogLevel 1 RewriteCond %{QUERY_STRING} (.*?)(?:[A-Za-z0-9_-]+)=&(.*) #RewriteRule (.+) $1?%1%2 [N,R,NE] RewriteRule ^/bib/([^\/]*)/?$ /cgi-bin/koha/detail\.pl?bib=$1 [PT] RewriteRule ^/isbn/([^\/]*)/?$ /search?q=isbn:$1 [PT] RewriteRule ^/issn/([^\/]*)/?$ /search?q=issn:$1 [PT] The other one, from the package install where I get the 403 looks like this: # Koha Apache Configuration Directives #NameVirtualHost * ## OPAC ServerAdmin __WEBMASTER_EMAIL__ DocumentRoot __OPAC_WWW_DIR__ ServerName __WEBSERVER_HOST__ # ServerAlias opac.mydomain.com ScriptAlias /cgi-bin/koha/ "__OPAC_CGI_DIR__/opac/" ScriptAlias /index.html "__OPAC_CGI_DIR__/opac/opac-main.pl" ScriptAlias /opac-search.pl "__OPAC_CGI_DIR__/opac/opac-search.pl" ScriptAlias /search "__OPAC_CGI_DIR__/opac/opac-search.pl" ErrorLog __LOG_DIR__/koha-opac-error_log # CustomLog __LOG_DIR__/koha-opac-access.log combined # TransferLog __LOG_DIR__/koha-opac-access.log SetEnv KOHA_CONF "__KOHA_CONF_DIR__/koha-conf.xml" SetEnv PERL5LIB "__PERL_MODULE_DIR__" SetEnv MEMCACHED_SERVERS "__MEMCACHED_SERVERS__" SetEnv MEMCACHED_NAMESPACE "__MEMCACHED_NAMESPACE__" # This syntax allows you to override a system preference # for a given virtual host. Use with caution! # You should add all the system preferences you override # in one or more vhosts to the environment variable # OVERRIDE_SYSPREF_NAMES for your staff intranet vhost # SetEnv OVERRIDE_SYSPREF_PrefName Value Options -Indexes # Secure internal stuff Order deny,allow Deny from all mod_gzip_on yes mod_gzip_dechunk yes mod_gzip_keep_workfiles No mod_gzip_can_negotiate yes mod_gzip_update_static No mod_gzip_temp_dir /tmp mod_gzip_minimum_file_size 512 mod_gzip_maximum_file_size 1000000 mod_gzip_maximum_inmem_size 1000000 mod_gzip_handle_methods GET POST mod_gzip_item_exclude reqheader "User-Agent: .*Mozilla/4\..*\[" mod_gzip_item_exclude mime ^image/.* mod_gzip_item_exclude rspheader Content-Type:image/* mod_gzip_item_include file \.js$ mod_gzip_item_include mime ^application/javascript$ mod_gzip_item_include mime ^application/x-javascript$ mod_gzip_item_include file \.php$ mod_gzip_item_include mime ^text/html$ mod_gzip_item_include file \.css$ mod_gzip_item_include mime ^text/css$ # Compress content with type html, text, and css, ... AddOutputFilterByType DEFLATE text/plain text/html text/xml text/css AddOutputFilterByType DEFLATE application/xml application/xhtml+xml application/rss+xml application/javascript application/x-javascript DeflateCompressionLevel 9 # Properly handle old browsers that do not support compression BrowserMatch ^Mozilla/4 gzip-only-text/html BrowserMatch ^Mozilla/4\.0[678] no-gzip BrowserMatch \bMSIE !no-gzip !gzip-only-text/html DeflateFilterNote Input instream DeflateFilterNote Output outstream DeflateFilterNote Ratio ratio LogFormat '"%r" %{outstream}n/%{instream}n (%{ratio}n%%)' deflate #properly handle requests coming from behind proxies Header append Vary User-Agent # Repeat this virtualhost stanza changing the following environment vars to # create multiple OPAC interfaces with custom css and/or search limits: # SetEnv OPAC_CSS_OVERRIDE mystyle.css # SetEnv OPAC_SEARCH_LIMIT branch:CODE # SetEnv OPAC_LIMIT_OVERRIDE 1 Options +FollowSymLinks ErrorDocument 400 /cgi-bin/koha/errors/400.pl ErrorDocument 401 /cgi-bin/koha/errors/401.pl ErrorDocument 403 /cgi-bin/koha/errors/403.pl ErrorDocument 404 /cgi-bin/koha/errors/404.pl ErrorDocument 500 /cgi-bin/koha/errors/500.pl # Rewrite Rules RewriteEngine On # Uncomment to turn on rewrite logging #RewriteLog __LOG_DIR__/koha-opac-rewrite.log #RewriteLogLevel 1 RewriteCond %{QUERY_STRING} (.*?)(?:[A-Za-z0-9_-]+)=&(.*) #RewriteRule (.+) $1?%1%2 [N,R,NE] RewriteRule ^/bib/([^\/]*)/?$ /cgi-bin/koha/opac-detail\.pl?bib=$1 [PT] RewriteRule ^/isbn/([^\/]*)/?$ /search?q=isbn:$1 [PT] RewriteRule ^/issn/([^\/]*)/?$ /search?q=issn:$1 [PT] ## Intranet ServerAdmin __WEBMASTER_EMAIL__ DocumentRoot __INTRANET_WWW_DIR__ ServerName __WEBSERVER_HOST__:__WEBSERVER_PORT_LIBRARIAN__ # ServerAlias intranet.mydomain.com ScriptAlias /cgi-bin/koha/ "__INTRANET_CGI_DIR__/" ScriptAlias /index.html "__INTRANET_CGI_DIR__/mainpage.pl" ScriptAlias /search "__INTRANET_CGI_DIR__/search.pl" Alias /plugin/ "__PLUGINS_DIR__/" ErrorLog __LOG_DIR__/koha-error_log # TransferLog __LOG_DIR__/koha-access.log SetEnv KOHA_CONF "__KOHA_CONF_DIR__/koha-conf.xml" SetEnv PERL5LIB "__PERL_MODULE_DIR__" SetEnv MEMCACHED_SERVERS "__MEMCACHED_SERVERS__" SetEnv MEMCACHED_NAMESPACE "__MEMCACHED_NAMESPACE__" Options +FollowSymLinks # If you are overriding any system preferences, # list them in this variable so the preference editor # knows that they have been overridden. # SetEnv OVERRIDE_SYSPREF_NAMES "Pref1,Pref2,Pref3" ErrorDocument 400 /cgi-bin/koha/errors/400.pl ErrorDocument 401 /cgi-bin/koha/errors/401.pl ErrorDocument 403 /cgi-bin/koha/errors/403.pl ErrorDocument 404 /cgi-bin/koha/errors/404.pl ErrorDocument 500 /cgi-bin/koha/errors/500.pl Options -Indexes # Secure internal stuff Order deny,allow Deny from all mod_gzip_on yes mod_gzip_dechunk yes mod_gzip_keep_workfiles No mod_gzip_can_negotiate yes mod_gzip_update_static No mod_gzip_temp_dir /tmp mod_gzip_minimum_file_size 512 mod_gzip_maximum_file_size 1000000 mod_gzip_maximum_inmem_size 1000000 mod_gzip_handle_methods GET POST mod_gzip_item_exclude reqheader "User-Agent: .*Mozilla/4\..*\[" mod_gzip_item_exclude mime ^image/.* mod_gzip_item_exclude rspheader Content-Type:image/* mod_gzip_item_include file \.js$ mod_gzip_item_include mime ^application/javascript$ mod_gzip_item_include mime ^application/x-javascript$ mod_gzip_item_include file \.php$ mod_gzip_item_include mime ^text/html$ mod_gzip_item_include file \.css$ mod_gzip_item_include mime ^text/css$ # Compress content with type html, text, and css, ... AddOutputFilterByType DEFLATE text/plain text/html text/xml text/css AddOutputFilterByType DEFLATE application/xml application/xhtml+xml application/rss+xml application/javascript application/x-javascript DeflateCompressionLevel 9 # Properly handle old browsers that do not support compression BrowserMatch ^Mozilla/4 gzip-only-text/html BrowserMatch ^Mozilla/4\.0[678] no-gzip BrowserMatch \bMSIE !no-gzip !gzip-only-text/html DeflateFilterNote Input instream DeflateFilterNote Output outstream DeflateFilterNote Ratio ratio LogFormat '"%r" %{outstream}n/%{instream}n (%{ratio}n%%)' deflate #properly handle requests coming from behind proxies Header append Vary User-Agent # Rewrite Rules RewriteEngine On # Uncomment to turn on rewrite logging #RewriteLog __LOG_DIR__/koha-intranet-rewrite.log #RewriteLogLevel 1 RewriteCond %{QUERY_STRING} (.*?)(?:[A-Za-z0-9_-]+)=&(.*) #RewriteRule (.+) $1?%1%2 [N,R,NE] RewriteRule ^/bib/([^\/]*)/?$ /cgi-bin/koha/detail\.pl?bib=$1 [PT] RewriteRule ^/isbn/([^\/]*)/?$ /search?q=isbn:$1 [PT] RewriteRule ^/issn/([^\/]*)/?$ /search?q=issn:$1 [PT] -----Urspr?ngliche Nachricht----- Von: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] Im Auftrag von Fridolin SOMERS Gesendet: Freitag, 29. November 2013 17:20 An: koha-devel at lists.koha-community.org Betreff: Re: [Koha-devel] Koha development server on Debian Wheezy Hie, Give your Apache configuration : etc/koha-httpd.conf Regards, Le 29/11/2013 17:13, Holger Meissner a ?crit : > Dear community, > > I'd like to set up Koha and Git for development. I use Oracle VM Virtual Box and Debian 7.2 Wheezy. First thing I tried, was to follow those instructions: > http://wiki.koha-community.org/wiki/Install_and_Setup_Koha_to_use_Git_ > on_a_Development_Server > > After pointing the files to the kohaclone I get a 403 Forbidden, when trying to navigate localhost:8080. > How do I upgrade the database? > > I also tried to use Koha-gitify, but there was the same problem. > https://github.com/mkfifo/koha-gitify > > Then I tried to install without packages: > http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=INSTALL.debi > an Yet the VirtualHost configuration seems to be incorrect and I'm > unable to figure out why. > [warn] NameVirtualHost *:80 has no VirtualHosts [warn] NameVirtualHost > *:8080 has no VirtualHosts > > Any suggestions how to fix these errors? > Thanks! > > Holger > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Fridolin SOMERS Biblibre - P?le support fridolin.somers at biblibre.com _______________________________________________ Koha-devel mailing list Koha-devel at 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/ From z.tajoli at cineca.it Tue Dec 3 17:25:26 2013 From: z.tajoli at cineca.it (Zeno Tajoli) Date: Tue, 03 Dec 2013 17:25:26 +0100 Subject: [Koha-devel] The best option for index after a batch change Message-ID: <529E05F6.7000603@cineca.it> Hi to all, I will do a batch chage on bibliographic data with a perl script. Around 2.000 record on 150.000 biblios. Before to launch the script, I close the background indexing (I use Tamil daemon). After the change I will have 2.000 entry in zebraque table. In your opinion what is the best oprion to do after ? a)I restart background indexing with Tamil's daemon or b)I reindex on command line with -z option ? Cheers Zeno Tajoli -- Dr. Zeno Tajoli Dipartimento Gestione delle Informazioni e della Conoscenza z.tajoli at cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate From tomascohen at gmail.com Tue Dec 3 18:37:44 2013 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Tue, 3 Dec 2013 15:37:44 -0200 Subject: [Koha-devel] RSS method for checking and warning about current installed version Message-ID: What would you think of adding some way for the about.pl page to load information on newer versions available, or even if the currently used branch has reached EOL? Regards To+ -- Tom?s Cohen Arazi Prosecretar?a de Inform?tica Universidad Nacional de C?rdoba ? +54 351 4333190 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From f.demians at tamil.fr Tue Dec 3 18:53:08 2013 From: f.demians at tamil.fr (=?UTF-8?B?RnLDqWTDqXJpYyBEZW1pYW5z?=) Date: Tue, 03 Dec 2013 18:53:08 +0100 Subject: [Koha-devel] The best option for index after a batch change In-Reply-To: <529E05F6.7000603@cineca.it> References: <529E05F6.7000603@cineca.it> Message-ID: <529E1A84.40503@tamil.fr> > I will do a batch chage on bibliographic data with a perl script. > Around 2.000 record on 150.000 biblios. Before to launch the script, > I close the background indexing (I use Tamil daemon). After the > change I will have 2.000 entry in zebraque table. > > In your opinion what is the best oprion to do after ? a)I restart > background indexing with Tamil's daemon or b)I reindex on command > line with -z option ? If your Perl script call Koha API (ModBiblio) to modify biblio records, just restart your indexing daemon. Otherwise, do a full reindexing, then restart your indexer. Note that you have an equivalent to rebuild_zebra.pl -z with: koha-index --select queue --verbose Kind regards, -- Fr?d?ric DEMIANS http://www.tamil.fr/fdemians From chris at bigballofwax.co.nz Tue Dec 3 19:48:26 2013 From: chris at bigballofwax.co.nz (Chris Cormack) Date: Wed, 4 Dec 2013 07:48:26 +1300 Subject: [Koha-devel] RSS method for checking and warning about current installed version In-Reply-To: References: Message-ID: On 4/12/2013 6:38 am, "Tomas Cohen Arazi" wrote: > > What would you think of adding some way for the about.pl page to load information on newer versions available, or even if the currently used branch has reached EOL? > I like this idea, assuming it is an opt in option. (and easily switched off again too) Chris > Regards > To+ > > -- > Tom?s Cohen Arazi > Prosecretar?a de Inform?tica > Universidad Nacional de C?rdoba > ? +54 351 4333190 ext 13168 > GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From gmc at esilibrary.com Tue Dec 3 21:45:55 2013 From: gmc at esilibrary.com (Galen Charlton) Date: Tue, 3 Dec 2013 12:45:55 -0800 Subject: [Koha-devel] RSS method for checking and warning about current installed version In-Reply-To: References: Message-ID: Hi, On Tue, Dec 3, 2013 at 10:48 AM, Chris Cormack wrote: > > What would you think of adding some way for the about.pl page to load > information on newer versions available, or even if the currently used > branch has reached EOL? > > > > I like this idea, assuming it is an opt in option. (and easily switched > off again too) > Given the desirability of staying up to date, I would be inclined to nagging opt-in, perhaps -- via a header or something that displays in the staff interface offering to check for version upgrades periodically. The user would have the option to dismiss the nag or subscribe, and could later change the relevant system preference value. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mtompset at hotmail.com Tue Dec 3 21:57:52 2013 From: mtompset at hotmail.com (Mark Tompsett) Date: Tue, 3 Dec 2013 15:57:52 -0500 Subject: [Koha-devel] RSS method for checking and warning about currentinstalled version In-Reply-To: References: Message-ID: Greetings, > What would you think of adding some way for the about.pl page > to load information on newer versions available, > or even if the currently used branch has reached EOL? I like the idea, but the question is: how would it know it has reached EOL? A lot of software has ?About ?> check for updates? If it wasn?t triggered unless they expressly went to the ?check for updates? tab, I don?t see why you need to worry about opt-in or opt-out. GPML, Mark Tompsett -------------- next part -------------- An HTML attachment was scrubbed... URL: From gmc at esilibrary.com Tue Dec 3 22:00:58 2013 From: gmc at esilibrary.com (Galen Charlton) Date: Tue, 3 Dec 2013 13:00:58 -0800 Subject: [Koha-devel] RSS method for checking and warning about currentinstalled version In-Reply-To: References: Message-ID: Hi, On Tue, Dec 3, 2013 at 12:57 PM, Mark Tompsett wrote: > > What would you think of adding some way for the about.pl page > > to load information on newer versions available, > > or even if the currently used branch has reached EOL? > > I like the idea, but the question is: h > ow would it know it has reached EOL? > Because something would say so -- perhaps a little web service we add to the website. > A lot of software has ?About ?> check for updates? > If it wasn?t triggered unless they expressly went to the ?check for > updates? tab, I don?t see why you need to worry about opt-in or opt-out. > Opt-in would be required for any automatic, periodic check -- some jurisdictions have strict laws forbidding software where from phoning home unbeknownst to the user. Just having a "check for updates" button perhaps wouldn't need a separate opt-in step, but would have to make it clear that it was getting information from a remote server. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a at navalmarinearchive.com Tue Dec 3 23:46:04 2013 From: paul.a at navalmarinearchive.com (Paul A) Date: Tue, 03 Dec 2013 17:46:04 -0500 Subject: [Koha-devel] RSS method for checking and warning about current installed version In-Reply-To: References: Message-ID: <5.2.1.1.2.20131203162051.02ff5530@pop.navalmarinearchive.com> At 07:48 AM 12/4/2013 +1300, Chris Cormack wrote: >On 4/12/2013 6:38 am, "Tomas Cohen Arazi" ><tomascohen at gmail.com> wrote: > > > > What would you think of adding some way for the > about.pl page to load information on newer versions > available, or even if the currently used branch has reached EOL? > > >I like this idea, assuming it is an opt in option. (and easily switched >off again too) >Chris Tom??s, please tell me that this does NOT involve instances of Koha attempting, unsupervised, to contact an external website. Thanks and best regards, Paul -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Tue Dec 3 23:55:02 2013 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Tue, 3 Dec 2013 20:55:02 -0200 Subject: [Koha-devel] RSS method for checking and warning about current installed version In-Reply-To: <5.2.1.1.2.20131203162051.02ff5530@pop.navalmarinearchive.com> References: <5.2.1.1.2.20131203162051.02ff5530@pop.navalmarinearchive.com> Message-ID: My main concern is people having Koha instances that already reached EOL and/or are not supported anymore. How to do it is the topic in discussion. I like the idea of a button (maybe in the form of a tab in the about page ;-) and maybe with a disclamer notice and a confirmation button). Having a syspref defaulting to "disabled" could work if this is troublesome in several jurisdictions. Regards To+ On Tue, Dec 3, 2013 at 7:46 PM, Paul A wrote: > At 07:48 AM 12/4/2013 +1300, Chris Cormack wrote: > > On 4/12/2013 6:38 am, "Tomas Cohen Arazi" wrote: > > > > What would you think of adding some way for the about.pl page to load > information on newer versions available, or even if the currently used > branch has reached EOL? > > > I like this idea, assuming it is an opt in option. (and easily switched > off again too) > Chris > > > Tom??s, please tell me that this does NOT involve instances of Koha > attempting, unsupervised, to contact an external website. > > Thanks and best regards, > Paul > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Tom?s Cohen Arazi Prosecretar?a de Inform?tica Universidad Nacional de C?rdoba ? +54 351 4333190 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a at navalmarinearchive.com Wed Dec 4 02:35:50 2013 From: paul.a at navalmarinearchive.com (Paul A) Date: Tue, 03 Dec 2013 20:35:50 -0500 Subject: [Koha-devel] RSS method for checking and warning about current installed version In-Reply-To: References: <5.2.1.1.2.20131203162051.02ff5530@pop.navalmarinearchive.com> <5.2.1.1.2.20131203162051.02ff5530@pop.navalmarinearchive.com> Message-ID: <5.2.1.1.2.20131203202017.076fe428@pop.navalmarinearchive.com> At 08:55 PM 12/3/2013 -0200, Tomas Cohen Arazi wrote: >My main concern is people having Koha instances that already reached EOL >and/or are not supported anymore. How to do it is the topic in discussion. >I like the idea of a button (maybe in the form of a tab in the about page >;-) and maybe with a disclamer notice and a confirmation button). Having a >syspref defaulting to "disabled" could work if this is troublesome in >several jurisdictions. I'm referring to professionals who know full well what they are doing with their library systems, we don't need the security implications of any "preference" having external file editing capability. If amateurs need reminding, that's another question that should be available during installation, not afterwards. Look around the landscape: does perl, or apache, or mysql, or zebra, or etc, etc... do this? You say "could work" -- I'm suggesting that security must be bullet proof. As far as I'm concerned, this avenue should be blackballed for a standard install/upgrade. It's just the thin end of the wedge towards other intrusions. Best regards -- Paul >Regards >To+ > > >On Tue, Dec 3, 2013 at 7:46 PM, Paul A ><paul.a at navalmarinearchive.com> wrote: >At 07:48 AM 12/4/2013 +1300, Chris Cormack wrote: >>On 4/12/2013 6:38 am, "Tomas Cohen Arazi" >><tomascohen at gmail.com> wrote: >> > >> > What would you think of adding some way for the >> about.pl page to load information on newer versions >> available, or even if the currently used branch has reached EOL? >> > >>I like this idea, assuming it is an opt in option. (and easily switched >>off again too) >>Chris > >Tom????s, please tell me that this does NOT involve instances of Koha >attempting, unsupervised, to contact an external website. > >Thanks and best regards, >Paul > >_______________________________________________ >Koha-devel mailing list >Koha-devel at 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/ > > > > >-- >Tom??s Cohen Arazi >Prosecretar??a de Inform??tica >Universidad Nacional de C??rdoba >??? +54 351 4333190 ext 13168 >GPG:? B76C 6E7C 2D80 551A C765 ? E225 0A27 2EA1 B2F3 C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.nighswonger at gmail.com Wed Dec 4 02:57:42 2013 From: chris.nighswonger at gmail.com (Christopher Nighswonger) Date: Tue, 3 Dec 2013 20:57:42 -0500 Subject: [Koha-devel] RSS method for checking and warning about current installed version In-Reply-To: <5.2.1.1.2.20131203202017.076fe428@pop.navalmarinearchive.com> References: <5.2.1.1.2.20131203162051.02ff5530@pop.navalmarinearchive.com> <5.2.1.1.2.20131203202017.076fe428@pop.navalmarinearchive.com> Message-ID: On Tue, Dec 3, 2013 at 8:35 PM, Paul A wrote: > At 08:55 PM 12/3/2013 -0200, Tomas Cohen Arazi wrote: > > My main concern is people having Koha instances that already reached EOL > and/or are not supported anymore. How to do it is the topic in discussion. > I like the idea of a button (maybe in the form of a tab in the about page > ;-) and maybe with a disclamer notice and a confirmation button). Having a > syspref defaulting to "disabled" could work if this is troublesome in > several jurisdictions. > > > I'm referring to professionals who know full well what they are doing with > their library systems, we don't need the security implications of any > "preference" having external file editing capability. If amateurs need > reminding, that's another question that should be available during > installation, not afterwards. > > Look around the landscape: does perl, or apache, or mysql, or zebra, or > etc, etc... do this? > I'll bet your favorite browser has the option to notify you of updates. Furthermore, I'll bet you allow it to. The last time I did a fresh Ubuntu install, (a few weeks ago) I was offered the option of automagic updates (either full or just security). I'd bet Debian has this option too (probably other distros as well). So I'm not sure I see the sky falling yet. Not to knock security concerns, but this is well established practice as far as I can see. And I think that's the sort of thing we're talking about here. FTR: I'd love to see some sort of notification system implemented. Kind Regards, Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From robin at catalyst.net.nz Wed Dec 4 03:04:31 2013 From: robin at catalyst.net.nz (Robin Sheat) Date: Wed, 04 Dec 2013 15:04:31 +1300 Subject: [Koha-devel] RSS method for checking and warning about current installed version In-Reply-To: References: <5.2.1.1.2.20131203162051.02ff5530@pop.navalmarinearchive.com> <5.2.1.1.2.20131203202017.076fe428@pop.navalmarinearchive.com> Message-ID: <1386122671.28498.12.camel@zarathud> Christopher Nighswonger schreef op di 03-12-2013 om 20:57 [-0500]: > The last time I did a fresh Ubuntu install, (a few weeks ago) I was > offered the option of automagic updates (either full or just > security). I'd bet Debian has this option too (probably other distros > as well). This is even more common in web things. Wordpress does this, Vanilla (forum software) does, I seem to recall that Gallery does too. -- Robin Sheat Catalyst IT Ltd. ? +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part URL: From bargioni at pusc.it Wed Dec 4 09:29:01 2013 From: bargioni at pusc.it (Stefano Bargioni) Date: Wed, 4 Dec 2013 09:29:01 +0100 Subject: [Koha-devel] The best option for index after a batch change In-Reply-To: References: Message-ID: Ciao Zeno, if you are not interested to short the batch change as much as possible, you can add a delay in your loop, to ensure that your zebra queue is filled at a regular pace, and that rebuild-zebra will manage only few records each time it runs. This solution, if suitable for your installation, doesn't require to modify the background indexing, neither to stop cataloguing. And if you are using the solr-browse we developed together, don't forget its reindexing process... Bye. Stefano > Hi to all, > > I will do a batch chage on bibliographic data with a perl script. > Around 2.000 record on 150.000 biblios. > Before to launch the script, I close the background indexing (I use > Tamil daemon). > After the change I will have 2.000 entry in zebraque table. > > In your opinion what is the best oprion to do after ? > a)I restart background indexing with Tamil's daemon > or > b)I reindex on command line with -z option ? > > Cheers > Zeno Tajoli From Pasi.Kallinen at pttk.fi Wed Dec 4 13:14:47 2013 From: Pasi.Kallinen at pttk.fi (Kallinen Pasi) Date: Wed, 4 Dec 2013 12:14:47 +0000 Subject: [Koha-devel] Translation annoyances Message-ID: <25DCE6EB7C29A24A8ABC913AEB608972BAA1E5D8@KS0105.ad.pohjoiskarjala.net> >Katrin Fischer wrote: > >I'd rather keep some additional %s and not lose the context and the Pity Koha doesn't support msgctxt - the gettext context string! Translators are not coders, nor vice versa. The variable names will mean nothing to the translators - it's good if the translator knows what '%s' means, and '%%' will confuse them. The translation script could be improved somewhat by discarding totally useless placeholders. Some simple(?) improvements: 1) Replace all inline TT code in msgid with a placeholders. (eg "[% variable_name|filter %]" => "%s") 2) If the msgid begins with a placeholder that is IF, and ends in a placeholder that's either END or ELSE, and there are no other placeholders, do not include the placeholders. 3) Do not include the placeholder in the msgid, if it is 'END' or 'ELSE' token and is at the beginning of the msgid. 4) Do not include the placeholder in the msgid, if it is 'END' or 'ELSE' token and is at the end of the msgid. 5) If there's only one placeholder, and it is a flow control token (IF, ELSE, etc), and it is not in the beginning or end of msgid, cut the msgid into two msgid's. 6) Ignore XSLT foobar 7) Ignore XSLT foobar 8) If msgid is nothing but placeholders (and spaces), do not use it. -- Yst?v?llisin terveisin Pasi Kallinen ICT-asiantuntija p. 0400-139747 pasi.kallinen at pttk.fi L?nsikatu 15 80110 Joensuu Pohjois-Karjalan Tietotekniikkakeskus Oy - www.pttk.fi ________________________________________ From: koha-translate-bounces at lists.koha-community.org [koha-translate-bounces at lists.koha-community.org] on behalf of Katrin Fischer [Katrin.Fischer.83 at web.de] Sent: Wednesday, December 04, 2013 13:43 To: koha-translate at lists.koha-community.org Subject: [Koha-translate] Translation annoyances Hi, I'd rather keep some additional %s and not lose the context and the chance to do grammatically more correct translations. I'd like to give some examples: Grouping together related sentences/error messages: %sNote: your comment contained illegal markup code. It has been saved with the markup removed, as below. You can edit the comment further, or cancel to retain the comment as is. %s %sError! Your comment was entirely illegal markup code. It has NOT been added.%s %sError! You cannot add an empty comment. Please add content or cancel.%s %sEdit course%sCreate course%s Suggestion status: "%s Pending %s Accepted %s Ordered %s Rejected %s Checked %s %s %s %s " Import status: "%s Cleaned %s Imported %s Importing %s Reverted %s Reverting %s Staged %s %s %s " Allowing translation of 'constructed' sentences: "%sEdit%sCreate%s Label layout" "%s Delete %s %s Update %s %s Move %s %s Copy %s %s %s 1st %s %s field %s%s$%s%s %s with value " Also if you only take variables into account, a simple [% IF %] checking for the existance of a variable could be a problem breakting the translation string: #. %1$s: name #. %2$s: IF ( invoice ) #. %3$s: invoice #. %4$s: END #. %5$s: ordernumber #: intranet-tmpl/prog/en/modules/acqui/orderreceive.tt:130 #, c-format msgid "Receive items from : %s %s[%s] %s (order #%s)" I think the translation scripts are not so much the problem, but badly constructed strings in the templates are. I think fixing the templates would be the better way. Katrin Am 04.12.2013 11:34, schrieb Fischer, Katrin: > > > > -----Urspr?ngliche Nachricht----- > Von: koha-translate-bounces at lists.koha-community.org im Auftrag von > Fridolin SOMERS > Gesendet: Mi 04.12.2013 11:05 > An: koha-translate at lists.koha-community.org > Betreff: Re: [Koha-translate] Translation annoyances > > I agree, specially on point 6. > PO shoould only consider TT vars [% var %], no other TT tag. > > I will try to work on it. > > Le 02/12/2013 08:37, Kallinen Pasi a ?crit : >> Hello. >> >> I've been translating Koha to Finnish for a bit, and I'm really > starting to hate some of the automagically generated msgid's. >> >> 1) String concatenation is BAD. >> For example, this line of code: >> var disabledForCurrent = _("Disabled for") + ' ' + $branch; >> turns into this translatable string: >> msgid "Disabled for" >> >> For some languages this is very hard to translate without sounding > stupid or just plain wrong. jQuery has some string placeholder support > for javascript, so Koha really should be using those instead! >> The example above would turn into: >> >> var disabledForCurrent = _("Disabled for {0}"); >> msgid "Disabled for {0}" >> >> >> 2) Consistency would be good. >> msgid "EAN:" >> msgid "EAN: " >> msgid "EAN :" >> >> >> 3) Sentences should not be cut in pieces. >> msgid "Please" >> msgid "upload" >> msgid "one." >> >> The "upload"-text is a link in the sentence. Ideally this should be: >> msgid "Please %supload%s one." >> >> >> 4) Is it a verb or a noun? >> msgid "Copy" >> >> >> 5) The wiki-like help texts should be in separate po-file. The help > texts inflate the staff UI po-file immensely, and the help translation > is not quite as critical as the UI. Having all the help texts > interspersed between all the actually important strings is irritating. >> >> >> 6) Translation is not programming. Replace all Template Toolkit code > with placeholders. >> For example >> msgid "Cancel [% IF TransferWhenCancelAllWaitingHolds %]and > Transfer [% END %]All" >> and >> msgid "Cancel hold and return to : [% overloo.branchname %]" >> >> >> 7) Exclude URLs. Those are not content that should be translatable. >> >> >> -- >> Yst?v?llisin terveisin >> >> Pasi Kallinen >> ICT-asiantuntija >> >> p. 0400-139747 >> pasi.kallinen at pttk.fi >> L?nsikatu 15 >> 80110 Joensuu >> >> Pohjois-Karjalan Tietotekniikkakeskus Oy - www.pttk.fi >> _______________________________________________ >> Koha-translate mailing list >> Koha-translate at lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate >> website: www.koha-community.org >> git: git.koha-community.org >> bugs: bugs.koha-community.org >> > > -- > Fridolin SOMERS > Biblibre - P?le support > fridolin.somers at biblibre.com > _______________________________________________ > Koha-translate mailing list > Koha-translate at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate > website: www.koha-community.org > git: git.koha-community.org > bugs: bugs.koha-community.org > > > _______________________________________________ Koha-translate mailing list Koha-translate at lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate website: www.koha-community.org git: git.koha-community.org bugs: bugs.koha-community.org From Katrin.Fischer.83 at web.de Wed Dec 4 13:48:29 2013 From: Katrin.Fischer.83 at web.de (Katrin Fischer) Date: Wed, 04 Dec 2013 13:48:29 +0100 Subject: [Koha-devel] Translation annoyances In-Reply-To: <25DCE6EB7C29A24A8ABC913AEB608972BAA1E06B@KS0105.ad.pohjoiskarjala.net> References: <25DCE6EB7C29A24A8ABC913AEB608972BAA1E06B@KS0105.ad.pohjoiskarjala.net> Message-ID: <529F249D.5050405@web.de> Hi, I know that things are not perfect for translating Koha, but we have already fixed a lot of issues since I started translating it a few years ago and we keep improving. It's not easy and it can only be done by people dedicating time and work. I have added some notes and comments to the points you raised: > 1) String concatenation is BAD. > For example, this line of code: > var disabledForCurrent = _("Disabled for") + ' ' + $branch; > turns into this translatable string: > msgid "Disabled for" There is a bug for that: Bug 7327 - Translation script doesn't like concatenated javascript strings http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7327 > For some languages this is very hard to translate without sounding stupid or just plain wrong. jQuery has some string placeholder support for javascript, so Koha really should be using those instead! > The example above would turn into: > > var disabledForCurrent = _("Disabled for {0}"); > msgid "Disabled for {0}" I think this method looks good and I have seen something similar being used in the newer code for translating the datatable toolbars: #. For the first occurrence, #. SCRIPT #: intranet-tmpl/prog/en/includes/datatables-strings.inc:1 #: intranet-tmpl/prog/en/includes/datatables.inc:2 msgid "(filtered from _MAX_ total entries)" So this looks like something we could do, but fixing all existing strings will take a lot of work and testing. > 2) Consistency would be good. > msgid "EAN:" > msgid "EAN: " > msgid "EAN :" We already fixed a gazillion of those small inconsistencies when we cleaned up the templates after agreeing on some capitalization rules. Some things like this still remain, also often we will have a term with and without :. For an additional space like this a patch would be really easy. > 3) Sentences should not be cut in pieces. > msgid "Please" > msgid "upload" > msgid "one." > The "upload"-text is a link in the sentence. Ideally this should be: > msgid "Please %supload%s one." Agreed. Also, sentences should not be 'constructed' with if-else-constructs where it can be avoided. I think this problem here especially shows when there is a link in the string, because the scripts look for html tags. It might be possible to improve that. > 4) Is it a verb or a noun? > msgid "Copy" I am not sure how to improve that - do you have a suggestion? Often it helps to look at the list of files a string appears in to make a bit more sense of it. In Pootle you can see the list when you hover over the 'Comment:' bit on the left. > 5) The wiki-like help texts should be in separate po-file. The help texts inflate the staff UI po-file immensely, and the help translation is not quite as critical as the UI. Having all the help texts interspersed between all the actually important strings is irritating. I've sent it to the koha-translate list earlier, but repeating it for koha-devel - there are some bugs related to this: Bug 7934 - Separate po file for help pages http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7934 Bug 7939 - Separate po files for different MARC dialects http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7939 > 6) Translation is not programming. Replace all Template Toolkit code with placeholders. > For example > msgid "Cancel [% IF TransferWhenCancelAllWaitingHolds %]and Transfer [% END %]All" > and > msgid "Cancel hold and return to : [% overloo.branchname %]" Are you suggesting to replace the %s with the real variable names? This could be a bit easier to read. We got comments in Pootle showing you what %s stands for what, but I admit that with a lot of %s in a string it gets a bit hard. > 7) Exclude URLs. Those are not content that should be translatable. In some cases I have wanted to change URLs in translation. For example I am linking to the German Firefox Plugin page for the offline-circulation plugin on the circulation home page: #: intranet-tmpl/prog/en/modules/help/offline_circ/list.tt:5 #, c-format msgid "https://addons.mozilla.org/en/firefox/addon/koct/" msgstr "https://addons.mozilla.org/de/firefox/addon/koct/" Hope it helps, Katrin From fridolin.somers at biblibre.com Wed Dec 4 14:25:27 2013 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Wed, 04 Dec 2013 14:25:27 +0100 Subject: [Koha-devel] Koha development server on Debian Wheezy In-Reply-To: <2C614FEEE2356A428DC65441E30302E06F5220@nero> References: <2C614FEEE2356A428DC65441E30302E06F5220@nero> Message-ID: <529F2D47.7050103@biblibre.com> Le 02/12/2013 12:08, Holger Meissner a ?crit : > This means connexion is only allowed by localhost. Simply replace by Same for -- Fridolin SOMERS Biblibre - P?le support fridolin.somers at biblibre.com From fridolin.somers at biblibre.com Wed Dec 4 14:30:35 2013 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Wed, 04 Dec 2013 14:30:35 +0100 Subject: [Koha-devel] Please help: biblio and biblionumber In-Reply-To: <527C1BD2.2020101@slacky.it> References: <527C1BD2.2020101@slacky.it> Message-ID: <529F2E7B.2030304@biblibre.com> hie, Your framework is correct. In UNIMARC the most used fields for local numbers are 001 and 090$a (090$9 may be used also). It is the warning who is wrong. Le 08/11/2013 00:01, Andrea Furin a ?crit : > hi. I had a very big problem: I cannot solve this: > in "MARC bibliographic framework test" I have an error: > "biblio and biblionumber The biblio.biblionumber and > biblioitems.biblioitemnumber fields be mapped to a MARC subfield" > > Installed Koha 3.12.6 via deb. > > I use Unimarc. > > My records.abs tells: > ############ IDENTIFICATION NUMBERS ################## > melm 001 Local-number,Local-number:n > # Local-number (biblionumber can be either in 090$9 or, on some setup, > on 001) > melm 009 Identifier-standard:w,Identifier-standard:n > melm 090$a Local-number,Local-number:n > melm 099$c > date-entered-on-file:s,date-entered-on-file:n,date-entered-on-file:y,Date-of-acquisition,Date-of-acquisition:d,Dat$ > melm 099$d > Date/time-last-modified:s,Date/time-last-modified:n,Date/time-last-modified:y > melm 099$t ccode:w > > My framework: > biblio.biblionumber -> 001_@ > bilioitems.biblioitemnumber -> 090_a > > > Please help, thanks in advance > > a.f. > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Fridolin SOMERS Biblibre - P?le support fridolin.somers at biblibre.com From Holger.Meissner at hs-gesundheit.de Thu Dec 5 10:02:43 2013 From: Holger.Meissner at hs-gesundheit.de (Holger Meissner) Date: Thu, 5 Dec 2013 09:02:43 +0000 Subject: [Koha-devel] Koha development server on Debian Wheezy Message-ID: <2C614FEEE2356A428DC65441E30302E06F559D@nero> Michael Hafen wrote: > The real problem though, the 403 error, is more of a mystery.? In my experience this error is usually caused by > file system permissions which don't allow apache to read and execute the perl files.? That would be the first > thing to check.? If the files are owned by you, then they need to be read and executable by everyone.? On the > other hand if the files are owned by www-data then the file need to be read and executable by the user.? The > first case is the most likely in your case in my opinion. It was the first case. I installed koha in root, but didn't set any permissions. Now everything works, thanks again! From philippe.blouin at inLibro.com Mon Dec 9 16:39:07 2013 From: philippe.blouin at inLibro.com (Philippe Blouin) Date: Mon, 09 Dec 2013 10:39:07 -0500 Subject: [Koha-devel] Issue with boostrap translation in 3.14 Message-ID: <52A5E41B.7080002@inLibro.com> (posted to both koha-translate and koha-devl) Hol? koha! Anyone else has issue with boostrap translation in 3.14? Seems a lot of strings are not picked up by "translate update" anymore, due to not being "obvious" to the tool anymore. For example: opac-tmpl/bootstrap/en/includes/masthead.inc : 131