unimaze / unimaze-peppol-stylesheets

UniStyles - Templates for displaying PEPPOL BIS EN (European Norm) invoices and credit notes, maintained by Unimaze Software.
Apache License 2.0
11 stars 6 forks source link
en16931 european-norm peppol peppol-bis stylesheets templates unimaze xslt xslt-stylesheet

README - UniStyles

Version Contributors Version License

This template is being implemented by Unimaze Software with feedback from the FUT Technical Committee of Icelandic Standards, which is a member of the European standards organizations CEN, CENELEC and ETSI as well as the international standards organizations ISO and IEC.

Common language files were derived and adapted from the work of SFTI in Sweden and OIOUBL in Denmark. Layout and visual appearance was inspired from the work of the Authoritiy of Iceland and Icelandic Standards.

As part of the POOL-TSPs project and during its duration, the work been co-financed by the European Commission through its eInvoicing 2017 CEF Telecom Call, CEF-TC-2017-3.

Objectives

The implementation of this template aims to:

Features

List of features:

Licensing

Apache License 2.0

See LICENSE for the full text.

Samples

See samples files.

      

## Requirements Currently this stylesheet requires XSLT 1.0 and has been tested with Saxon v9.7 & v9.9 and MSXML 3.0. To trigger the transformation from UBL XML to HTML type via commandline type at project root level: mvn clean install * The UBL test input files are in the directory: [src/test/resources/ubl21](src/test/resources/ubl21). * The XSL stylesheets are in the directory: [src/main/resources/xslt/html](src/main/resources/xslt/html). * The HTML output will be created in the directory: [target/generated-resources/xml/xslt](target/generated-resources/xml/xslt). ## Adding a new language In order to add another language to the stylesheet, there are a few steps. `*` is your language code Create a file named Headlines-BT_*.xml (or copy and rename Headlines-BT_en.xml) The structure of the xml should be: ``
    ``
       ` The official term name in your language `
        ` The definition of the term --->Optional`
        ` A description of the term --->Optional`
        ` The preferred display name in the stylesheet (if abscent, the TermName will be used) - If present but empty, no lead text will be shown in the stylesheet.`
        `
--> Optional`
    `
`
`
`
Pleas make sure to add all the BusinessTerms you wish to be visible in the stylesheet, there is no fallback if a term is missing, the lead text will then be abscent. Create files corresponding to all the relevant code lists in your language by replacing the * with your language code. With these code lists, there will be a fallback to english code values if the value is missing in your language. The format of all of the code lists below are in generic code 1.0 : http://docs.oasis-open.org/codelist/ns/genericode/1.0/ The relevant code lists are: * UBLClassificationCode_*.xml --> Item classification identifier * UBLInvoiceBaseType_*.xml --> Base type of document: Invoice or Credit Note * UBLPeriodDescriptionCode_*.xml --> Invoice period description code * UBLTaxCategoryCode_*.xml --> Tax category code * UNCL1001_*.xml --> Sub-type of document * UNCL4461_*.xml --> Payment means code * UNCL5189_*.xml --> Allowance reason code * UNCL7161_*.xml --> Charge reason code * UNECE_*.xml --> Unit of measure code ## Setting the default language Open the user_config.xsl and under the tag: `` change the `*` to your language code, corresponding to the `*` in your file names. The language can be changed in runtime by setting the `lang` XSLT parameter when invoking the transaction. --- ![CEF - Connecting Europe Facility](docs/en_cef_300x42.png)