Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not supporting different encoding. #2

Closed
DJArty opened this issue Jan 21, 2021 · 15 comments
Closed

Not supporting different encoding. #2

DJArty opened this issue Jan 21, 2021 · 15 comments

Comments

@DJArty
Copy link

DJArty commented Jan 21, 2021

2021-01-21_14-08
Looks like not supporting different encoding - only win1255 or utf8? Need more: IBM866, DOS... etc.
Now see empty table with moving blue line..
Maybe godbf project can help with it.

@APerricone
Copy link
Owner

Hello, can you send me a example dbf ?

@DJArty
Copy link
Author

DJArty commented Jan 22, 2021 via email

@APerricone
Copy link
Owner

can you send me the zip to my email, antonino.perricone@yahoo.it ?
can you try last version also?

@APerricone
Copy link
Owner

There is no information about the code page or encoding used inside the dbf, you see it correctly on DBFNavigator because it uses the codepage of the system, in your case cp866.
From v.0.0.7 this extension uses the setting "files.encoding" to decode the dbf file, I added a setting "dbf-table.encoding" also, to allow different encoding for text and dbf.

@DJArty
Copy link
Author

DJArty commented Jan 23, 2021

uses the setting "files.encoding"

Thank you! Now its cool.

@DJArty
Copy link
Author

DJArty commented Feb 16, 2021 via email

@APerricone
Copy link
Owner

jut this morning, testing the old sample I saw an error, are you trying the 0.1.1 ?

@APerricone
Copy link
Owner

no, the last version does not open it, how did you do it?

@DJArty
Copy link
Author

DJArty commented Feb 16, 2021 via email

@DJArty
Copy link
Author

DJArty commented Feb 16, 2021 via email

@DJArty
Copy link
Author

DJArty commented Feb 16, 2021 via email

@DJArty
Copy link
Author

DJArty commented Feb 16, 2021 via email

@APerricone
Copy link
Owner

APerricone commented Feb 16, 2021

correct, the problem is that field T:5 , I am based on harbour code and that case is not contemplated. did you do it with Fox Pro? Can you send me an example with different values on time?

@DJArty
Copy link
Author

DJArty commented Feb 16, 2021 via email

@APerricone
Copy link
Owner

The column type T: 5 is filled with "0000 " (with a space at end), I added some code that if the data is in this form it parse it, but I am not sure that it parse them in the correct way, I think the correct values are between 0000 and 2359 like hours and minutes.
Now I see it in this way:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants