We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
notepadd++: v7.7.1 32-bit HexEditor.dll : HexEditor_0.9.12_Win32.zip (32-bit )
see bin file in the attachment.
show in notepadd++: hex mode :
when i use hex in linux (as it shows by python program ), as follows :
hex db2/Db_field_Extractor_poly33.log 00000000 00 f0 f0 f1 f2 f4 00 f0 f0 f6 00 f0 f0 f0 f0 f0 ................ 00000010 00 f0 f0 f1 f2 f4 f0 f0 f6 00 f0 00 f3 f0 f0 f1 ................ 00000020 f2 f0 f2 f4 00 00 00 b1 08 00 00 00 b1 08 00 d5 ................ 00000030 00 f0 f0 00 f1 f2 00 f1 f1 00 f1 f1 00 f0 f9 f9 ................ 00000040 00 f0 f9 f9 ....
why 00 f0 f0 f1 f2 f4 00 f0 f0 f6 00 f0 f0 f0 f0 f0 becomes to 20 d7 a0 d7 a0 d7 a1 d7 a2 d7 a4 20 d7 a0 d7 a0 in notepadd++ ??
seems hex has no problem, is this a bug of BOM?
Db_field_Extractor_poly33.log
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
No branches or pull requests
notepadd++: v7.7.1 32-bit
HexEditor.dll : HexEditor_0.9.12_Win32.zip (32-bit )
see bin file in the attachment.
show in notepadd++: hex mode :
when i use hex in linux (as it shows by python program ), as follows :
why 00 f0 f0 f1 f2 f4 00 f0 f0 f6 00 f0 f0 f0 f0 f0 becomes to 20 d7 a0 d7 a0 d7 a1 d7 a2 d7 a4 20 d7 a0 d7 a0 in notepadd++ ??
seems hex has no problem, is this a bug of BOM?
Db_field_Extractor_poly33.log
The text was updated successfully, but these errors were encountered: