Dimensioner: File Exchange Format

Technical Specification for Data Exchange (CSV)

1. Format and Structure

• File Type: Data must be provided as flat text files in CSV format (.csv).

• Field Separator: The separator character used is a semicolon (;).

• Line Break: Each data line must end with the standard Windows line break, i.e., Line Feed and Carriage Return (CRLF / \r\n).

• Text Qualifiers: Text qualifiers (such as quotation marks "text" or apostrophes 'text') must not be used around text fields.

2. Data Validation and Formatting

• Trimming: All data must be fully trimmed. There must be no leading or trailing spaces.

• Data Cleaning: Data must be cleaned of unintended whitespace characters. Double spaces, tabs (\t), or unexpected line breaks within data fields are not allowed.

3. Encoding and Character Set (Charset)

By default, Windows-1252 (ANSI/Western European) is used unless otherwise specifically agreed. However, the system supports a number of other standards as listed below.

Overview of Supported Character Sets:

• UTF: UTF-8, UTF-16LE, UTF-16BE, UTF-16

• Windows: Windows-1250, Windows-1251, Windows-1252 (Default), Windows-1253, Windows-1254, Windows-1255, Windows-1256, Windows-1257, Windows-1258, Windows-874

• ISO: ISO-8859-1, ISO-8859-2, ISO-8859-3, ISO-8859-4, ISO-8859-5, ISO-8859-6, ISO-8859-7, ISO-8859-8, ISO-8859-9, ISO-8859-15

• Other: ASCII, KOI8-R, Shift_JIS, EUC-JP, EUC-KR, Big5, GB2312, GB18030, LMBCS

Suggested Follow-up / Email to Partner (Agreement on Character Set):

If you need to send this directly to a recipient and want to clarify the last point (character set alignment), you can add the following:

"The above are our technical standard requirements for file deliveries. Please note that our default character set is set to Windows-1252. If your systems require or prefer a different character set – for example, UTF-8 – please kindly notify us before the start of testing so we can register and adjust the integration accordingly."