NetSetMan Support

bil

Member

Registered: 2023-01-19

Posts: 4

Problems with formatting in scan results export

Windows 10, 11
NetSetMan Version 5.1.1
1. When exporting a network scan as a .csv file, commas are expected as delimiters. They are actually semicolons.
2. When exporting a network scan as html, unexpected characters occur beside every "<" in the HTML code. They can't be seen in a text editor Using TextPad 7.6.4), but the page doesn't render properly (grab attached).

I had to copy all of the generated webpage into a text editor and replace what then shows as "<?" with "<" to fix and make a new readable HTML table.

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: Problems with formatting in scan results export

1. Although the C in CSV stands for "comma", there are different types of standardized delimiters, such as comma, semicolon or tab. Whenever numbers are involved, it is recommended to use a semicolon, because in some large parts of the world like in Europe, the decimal separator is a comma. You can read more about this topic at this Wikipedia page: https://en.wikipedia.org/wiki/Comma-separated_values
Are there any downsides for you if a semicolon is used? When you import the file, there should be an option to specify which character to use as the delimiter.

2. Apparently the file has been saved with Unicode encoding which can lead to your observation depending on the constellation. We have now modified it to be saved as a UTF8 file, so the file should now always open up correctly. The fix will be available in the next version.
You can test this by opening the exported file in Notepad, then File > Save as, and changing the encoding to UTF-8 before saving it.

Thank you for reporting this.

bil

Member

Registered: 2023-01-19

Posts: 4

Re: Problems with formatting in scan results export

1. Thanks, no issues choosing the delimiter for import and I can see how a semicolon would be preferable at times, just making sure you meant it.
2. Good stuff!