1

Topic: Variant to ANSI a TXT-file

It was puzzled with the general-purpose transport of the data between forms, applications and files. smile
Task essence: to send field values  and values  in an ANSI-file and it is reverse lost-free.
Why ANSI? For scalability. To store in any container: any DB (including ), any file (ini, txt, csv), register Win.
Primary data can be in any form and the coding including the unicode. Can be  and the binary fields, different types Float, Dates with time to . Distinct transmission of empty values (it is good if an empty line/0/NULL will be different concepts).
Coding of the data in an ANSI-file can be on choice HEX/base64/MIME and so forth not in essence. XML/JSON/TXT - it is not basic.
The main thing - conversion there and reversely without superfluous .
While speech about an exchange between wines-appendices, i.e. everyones NIX with their strange dates while we lower.
Initially we admit that each "field" after transportation gets  to a proper place: int in int, Float in Float, date in date,  in .
The task not such simple as can seem at first sight.
So, we exchange experience, links and so forth

2

Re: Variant to ANSI a TXT-file

It is possible to begin with a simple bicycle https://ru.wikipedia.org/wiki/Tag-length-value

3

Re: Variant to ANSI a TXT-file

LSV wrote:

It was puzzled with the general-purpose transport of the data between forms, applications and files. smile
Task essence: to send field values  and values  in an ANSI-file and it is reverse lost-free.
Why ANSI? For scalability. To store in any container: any DB (including ), any file (ini, txt, csv), register Win.
Primary data can be in any form and the coding including the unicode. Can be  and the binary fields, different types Float, Dates with time to . Distinct transmission of empty values (it is good if an empty line/0/NULL will be different concepts).
Coding of the data in an ANSI-file can be on choice HEX/base64/MIME and so forth not in essence. XML/JSON/TXT - it is not basic.
The main thing - conversion there and reversely without superfluous .
While speech about an exchange between wines-appendices, i.e. everyones NIX with their strange dates while we lower.
Initially we admit that each "field" after transportation gets  to a proper place: int in int, Float in Float, date in date,  in .
The task not such simple as can seem at first sight.
So, we exchange experience, links and so forth

Utf8 - Our all

4

Re: Variant to ANSI a TXT-file

Probably I do not understand something,  like for a long time is invented, ObjectBinaryToText is invented approximately then, in what an essence of an exchange by experience?

5

Re: Variant to ANSI a TXT-file

LSV> Why ANSI? For scalability.
It is a joke such? Friday the day after tomorrow.
> The main thing - conversion there and reversely without superfluous .
Auxiliary  (tags and so forth) considers superfluous?

6

Re: Variant to ANSI a TXT-file

Rustam wrote:

LSV> Why ANSI? For scalability.
It is a joke such? Friday the day after tomorrow.
> The main thing - conversion there and reversely without superfluous .
Auxiliary  (tags and so forth) considers superfluous?

1. And what not so? smile
2. SI (tags) are not considered.

7

Re: Variant to ANSI a TXT-file

ANSI, whether it is serious that? You will not check, but the masochists, voluntary shooting to yourself in a foot, almost do not remain.

8

Re: Variant to ANSI a TXT-file

asutp2 wrote:

ANSI, whether it is serious that? You will not check, but the masochists, voluntary shooting to yourself in a foot, almost do not remain.

APPRX. You while offered nothing.
: And unless any XML/JSON as a matter of fact not an ANSI-file?
Speaking about ANSI meant: in a file only a Latin and digits .

9

Re: Variant to ANSI a TXT-file

LSV wrote:

it is passed...
APPRX. You while offered nothing.
: And unless any XML/JSON as a matter of fact not an ANSI-file?
Speaking about ANSI meant: in a file only a Latin and digits .

Base64 - Our all

10

Re: Variant to ANSI a TXT-file

schi wrote:

Base64 - our all

Is all well, but at first it is necessary to receive bytes which will then be wrapped in Base64.
Is  with fields:
int
string
Float
Datetime
image (mssql BLOB) it is admissible there an icon 44
binary (16) a-lja a key from 1.
How it should look before  in Base64?

11

Re: Variant to ANSI a TXT-file

LSV wrote:

as it should look before  in Base64?

And should. For coding in Base64 it is necessary to specify the pointer in the data and data size. On an output - a line

12

Re: Variant to ANSI a TXT-file

[quote = _ Vasilisk _] it is passed...
And should. For coding in Base64 it is necessary to specify the pointer in the data and data size. On an output - a line

Re-read a question. To  in base64.
To, Charles!
As  in base64 here likely all know also it is uninteresting.