Projekt

Allgemein

Profil

« Zurück | Weiter » 

Revision 88626a85

Von Hans P. Schlaepfer vor fast 5 Jahren hinzugefügt

  • ID 88626a850ac813782872df9d269deec4072d834a
  • Vorgänger 2fd60059
  • Nachfolger 697669b9

Neues Design 2019 Standard-Code templates/webpages/client_config/_datev_check_configuration.html

Unterschiede anzeigen:

templates/webpages/client_config/_datev_check_configuration.html
2 2
[% USE L %]
3 3

  
4 4
<div id="datev_check_configuration">
5
 <table>
6
  <tr>
7
   <td colspan="3">[% LxERP.t8('It is possible to make a quick DATEV export everytime you post a record to ensure things work nicely with their data requirements. This will result in a slight overhead though you can enable this for each type of record independently.') %]</td>
8
  </tr>
5
<div class="wrapper">
6

  
7
<p>[% LxERP.t8('It is possible to make a quick DATEV export everytime you post a record to ensure things work nicely with their data requirements. This will result in a slight overhead though you can enable this for each type of record independently.') %]</p>
8

  
9

  
10

  
11
<table class="tbl-horizontal">
12
  <tbody>
9 13
  <tr>
10
   <td align="right">[% LxERP.t8('Check on sales invoice') %]</td>
11
   <td>[% L.yes_no_tag('defaults.datev_check_on_sales_invoice', SELF.defaults.datev_check_on_sales_invoice) %]</td>
12
   <td>[% LxERP.t8('Perform check when a sales invoice or a payment for a sales invoice is posted?') %]</td>
14
    <th>[% LxERP.t8('Check on sales invoice') %]</th>
15
    <td>[% L.yes_no_tag('defaults.datev_check_on_sales_invoice', SELF.defaults.datev_check_on_sales_invoice) %]</td>
16
    <td class="longdesc">[% LxERP.t8('Perform check when a sales invoice or a payment for a sales invoice is posted?') %]</td>
13 17
  </tr>
14 18
  <tr>
15
   <td align="right">[% LxERP.t8('Check on purchase invoice') %]</td>
16
   <td>[% L.yes_no_tag('defaults.datev_check_on_purchase_invoice', SELF.defaults.datev_check_on_purchase_invoice) %]</td>
17
   <td>[% LxERP.t8('Perform check when a purchase invoice or a payment for a purchase invoice is posted?') %]</td>
19
    <th>[% LxERP.t8('Check on purchase invoice') %]</th>
20
    <td>[% L.yes_no_tag('defaults.datev_check_on_purchase_invoice', SELF.defaults.datev_check_on_purchase_invoice) %]</td>
21
    <td class="longdesc">[% LxERP.t8('Perform check when a purchase invoice or a payment for a purchase invoice is posted?') %]</td>
18 22
  </tr>
19 23
  <tr>
20
   <td align="right">[% LxERP.t8('Check on ar transaction') %]</td>
21
   <td>[% L.yes_no_tag('defaults.datev_check_on_ar_transaction', SELF.defaults.datev_check_on_ar_transaction) %]</td>
22
   <td>[% LxERP.t8('Perform check when an ar transaction is posted?') %]</td>
24
    <th>[% LxERP.t8('Check on ar transaction') %]</th>
25
    <td>[% L.yes_no_tag('defaults.datev_check_on_ar_transaction', SELF.defaults.datev_check_on_ar_transaction) %]</td>
26
    <td class="longdesc">[% LxERP.t8('Perform check when an ar transaction is posted?') %]</td>
23 27
  </tr>
24 28
  <tr>
25
   <td align="right">[% LxERP.t8('Check on ap transaction') %]</td>
26
   <td>[% L.yes_no_tag('defaults.datev_check_on_ap_transaction', SELF.defaults.datev_check_on_ap_transaction) %]</td>
27
   <td>[% LxERP.t8('Perform check when an ap transaction is posted?') %]</td>
29
    <th>[% LxERP.t8('Check on ap transaction') %]</th>
30
    <td>[% L.yes_no_tag('defaults.datev_check_on_ap_transaction', SELF.defaults.datev_check_on_ap_transaction) %]</td>
31
    <td class="longdesc">[% LxERP.t8('Perform check when an ap transaction is posted?') %]</td>
28 32
  </tr>
29 33
  <tr>
30
   <td align="right">[% LxERP.t8('Check on gl transaction') %]</td>
31
   <td>[% L.yes_no_tag('defaults.datev_check_on_gl_transaction', SELF.defaults.datev_check_on_gl_transaction) %]</td>
32
   <td>[% LxERP.t8('Perform check when a gl transaction is posted?') %]</td>
34
    <th>[% LxERP.t8('Check on gl transaction') %]</th>
35
    <td>[% L.yes_no_tag('defaults.datev_check_on_gl_transaction', SELF.defaults.datev_check_on_gl_transaction) %]</td>
36
    <td class="longdesc">[% LxERP.t8('Perform check when a gl transaction is posted?') %]</td>
33 37
  </tr>
34 38
  <tr>
35
   <td align="right">[% LxERP.t8('Datev export encoding') %]</td>
36
   <td>[% L.select_tag('defaults.datev_export_format', [ [ 'cp1252', LxERP.t8('Strict and halt') ],[ 'cp1252-translit', LxERP.t8('Strict but replace') ],[ 'utf-8', LxERP.t8('Relaxed (UTF-8)') ]  ], default=SELF.defaults.datev_export_format) %]
37
   <td>[% LxERP.t8('DATEV expects the encoding to be Western Europe conform (LATIN-1, cp1252). By setting this to "Strict and halt" the DATEV export halts with a error if there is a single character in "Posting Text" which is not LATIN-1 encodeable. By setting this to "Strict but replace" kivitendo will replace the character with a similar one and the export will simply warn about those fields. By setting this to relaxed (UTF-8) the DATEV export encoding will be in kivitendo (UTF-8) encoded and the external import program has to handle this (this may work for DATEV deriviates or future versions of DATEV). Background details: For example turkish characters (Ç) are not valid cp1252 charactes and armenian characters like "Գեղարդ" are probably not replaceable in cp1252') %]</td>
39
    <th>[% LxERP.t8('Datev export encoding') %]</th>
40
    <td>[% L.select_tag('defaults.datev_export_format', [ [ 'cp1252', LxERP.t8('Strict and halt') ],[ 'cp1252-translit', LxERP.t8('Strict but replace') ],[ 'utf-8', LxERP.t8('Relaxed (UTF-8)') ]  ], default=SELF.defaults.datev_export_format) %]</td>
41
    <td class="longdesc">[% LxERP.t8('DATEV expects the encoding to be Western Europe conform (LATIN-1, cp1252). By setting this to "Strict and halt" the DATEV export halts with a error if there is a single character in "Posting Text" which is not LATIN-1 encodeable. By setting this to "Strict but replace" kivitendo will replace the character with a similar one and the export will simply warn about those fields. By setting this to relaxed (UTF-8) the DATEV export encoding will be in kivitendo (UTF-8) encoded and the external import program has to handle this (this may work for DATEV deriviates or future versions of DATEV). Background details: For example turkish characters (Ç) are not valid cp1252 charactes and armenian characters like "Գեղարդ" are probably not replaceable in cp1252') %]</td>
38 42
  </tr>
39
 </table>
40
</div>
43
  </tbody>
44
</table>
45

  
46
</div><!-- /.wrapper -->
47
</div><!-- /#datev_check_configuration.wrapper -->

Auch abrufbar als: Unified diff