X-Git-Url: http://wagnertech.de/git?a=blobdiff_plain;f=templates%2Fwebpages%2Fclient_config%2F_datev_check_configuration.html;h=dc99c218e3893c4ce8ae3b55fc9c8c9e3d569ad0;hb=6caf1000dabee234d86457ff433268cebd8e0447;hp=13d12aaa267c31516c6b03ce1abb90bd8242dfd6;hpb=368f144b970a4b307a50d82bb398e704d65eec43;p=kivitendo-erp.git

diff --git a/templates/webpages/client_config/_datev_check_configuration.html b/templates/webpages/client_config/_datev_check_configuration.html
index 13d12aaa2..dc99c218e 100644
--- a/templates/webpages/client_config/_datev_check_configuration.html
+++ b/templates/webpages/client_config/_datev_check_configuration.html
@@ -1,10 +1,8 @@
 [%- USE LxERP -%][%- USE L -%]
 <div id="datev_check_configuration">
- <div class='listheading'>[% LxERP.t8('DATEV check configuration') %]</div>
-
  <table>
   <tr>
-   <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 independantly.') %]</td>
+   <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>
   </tr>
   <tr>
    <td align="right">[% LxERP.t8('Check on sales invoice') %]</td>
@@ -31,5 +29,10 @@
    <td>[% L.yes_no_tag('defaults.datev_check_on_gl_transaction', SELF.defaults.datev_check_on_gl_transaction) %]</td>
    <td>[% LxERP.t8('Perform check when a gl transaction is posted?') %]</td>
   </tr>
+  <tr>
+   <td align="right">[% LxERP.t8('Datev export encoding') %]</td>
+   <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>[% 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>
+  </tr>
  </table>
 </div>

[% 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 independantly.') %]			[% 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.') %]
[% LxERP.t8('Check on sales invoice') %]	[% L.yes_no_tag('defaults.datev_check_on_gl_transaction', SELF.defaults.datev_check_on_gl_transaction) %]	[% LxERP.t8('Perform check when a gl transaction is posted?') %]
[% LxERP.t8('Datev export encoding') %]	[% 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) %] +	[% 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') %]