[koha-commits] main Koha release repository branch 3.8.x updated. v3.08.13-6-ga1e9c27

Git repo owner gitmaster at git.koha-community.org
Thu Jun 6 11:21:33 CEST 2013


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "main Koha release repository".

The branch, 3.8.x has been updated
       via  a1e9c273537c5c14f60afd4e77bf5cd84d34a88b (commit)
       via  8449be610e28733a529083e35e9f2980e76ddc5a (commit)
      from  6513661a1d2f8bf3af18377e328333251b76da04 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit a1e9c273537c5c14f60afd4e77bf5cd84d34a88b
Author: Chris Cormack <chrisc at catalyst.net.nz>
Date:   Sun Apr 8 20:10:19 2012 +1200

    Bug 6709 : Patch for testing translating .xml files
    
    Signed-off-by: Bernardo Gonzalez Kriegel <bgkriegel at gmail.com>
    Signed-off-by: Katrin Fischer <Katrin.Fischer.83 at web.de>
    Comment on second patch.

commit 8449be610e28733a529083e35e9f2980e76ddc5a
Author: Bernardo Gonzalez Kriegel <bgkriegel at gmail.com>
Date:   Mon Apr 29 13:07:11 2013 -0300

    Bug 6709 - marc21_field_006.xml and marc21_field_008.xml can't be translated
    
    This patch changes
    1) structure and schema for xml files used in MARC21
    006 and 008 value builders.
    2) JavaScript functions used to show value builders.
    
    Xml processing is enabled in previous patch
    
    Any translatable string has been moved to an xml element,
    those strings that no need translation remains as xml
    attributes.
    
    NOTE_1: I do not include as translatable material types
    codes, because those values are restricted in schema
    definition. But this restriction can be removed.
    
    NOTE_2: Anyone with experience in XML/XSD please
    check the new schema definition.
    
    NOTE_3: Anyone with experience in the former and
    JavaScript please check xmlControlfield.js
    
    To test:
    1) Apply the patch
    2) Verify that 006 and 008 value builders show and work
    properly
    3) Update translation files for your favorite language,
    a new set of strings must show up corresponding to
    names and descriptions on value builders.
    
    Note: messed up patches, sending again.
    Signed-off-by: Katrin Fischer <Katrin.Fischer.83 at web.de>
    All tests and QA script pass.
    
    Did regression tests on the plugins for 006 and 008 and could
    spot no differences in behavior of the plugins to before.
    
    Also tested the translation process and found it working nicely.
    Thank you for fixing this long standing translation bug!

-----------------------------------------------------------------------

Summary of changes:
 .../intranet-tmpl/prog/en/js/xmlControlfield.js    |   23 +-
 .../cataloguing/value_builder/marc21_field_006.xml | 1562 ++++++------
 .../cataloguing/value_builder/marc21_field_008.xml | 2566 ++++++++++----------
 .../cataloguing/value_builder/marc21_field_CF.xsd  |   26 +-
 misc/translator/tmpl_process3.pl                   |    2 +-
 5 files changed, 2093 insertions(+), 2086 deletions(-)


hooks/post-receive
-- 
main Koha release repository


More information about the koha-commits mailing list