As far as I'm aware NPP shouldn't add (or remove) a BOM unless this is requested by the user, ie the encoding of a file that already exists is preserved. New files created in NPP default to UTF-8 without BOM, but this can be adjusted in the settings.
What is the nature of the corruption Martin? How do the corrupt files appear in NPP? If you have access to the original files, or can reconstruct them, can you use the NPP Compare plugin to highlight the differences before and after the changes (note that this will not detect BOM related differences)?
------------------------------
Andrew Harfoot
GeoData
University of Southampton
------------------------------
Original Message:
Sent: 03-22-2019 07:17
From: Martin Dowler
Subject: Notepad++ wor files potential issue
It was worth a shot but I tried it and it didn't solve it Warren. There are about 8 files, all with the same modified date/time and 6 of them are corrupt. They were all bulk saved in NPP. I cant be sure which version of NPP it happened in either as I have different versions on the pc's I use (my work one is v7/32bit but the other is more recent). I think I may have to put it down to a blip. On the plus side all the files were template files, not actual project files so I can recreate them fairly easily. I was just worried that as I wanted to bulk edit a couple of hundred files I might be spreading corruption across my file structure like a virus. Also that is really useful to know too Bill. Thanks all.
------------------------------
Martin Dowler
CHESHIRE & WIRRAL PARTNERSHIP NHS TRUST
Original Message:
Sent: 03-22-2019 07:03
From: Bill Wemple
Subject: Notepad++ wor files potential issue
MIPro 15.2 (x64) & later has a system settings preference to encode workspaces and tab files. If that is checked then workspaces (and new TAB files) will be encoded as UTF-8 with BOM. This preference is unchecked by default so uses can share non-Unicode WOR\TAB files with earlier MIPro versions provided they aren't using newer features in them. FYI, MIPro writes to lowest possible version depending on features used (new MB syntax, new Projection or Datum#, etc.)
If editing & saving in NP++ then make sure you are encoding them (UTF-8 BOM) same way else you can corrupt these WOR\TAB files as well.
All that being said, manual editing of workspaces is always done at user's peril even though they contain only uncompiled MB syntax.
Cheers,
-Bill
------------------------------
Bill Wemple
Principal QA Engineer
Pitney Bowes
Troy, NY
Original Message:
Sent: 03-21-2019 12:22
From: Martin Dowler
Subject: Notepad++ wor files potential issue
Does anyone else use notepad++ to bulk edit .wor files and has anyone had occurrences where the edited files have corrupted.
Today I updated 200 plus files using the editor and I noticed some of them are corrupted.
I wondered if it might be just some of the files which have been opened in MIPro 17 as opposed to older workspaces but in fact it seems they are all from the same date and have not been edited in v17.
Notepad++ is set to auto-detect encoding and its encoding is set to UTF-8.
Anyone else experience something similar?
------------------------------
Martin Dowler
CHESHIRE & WIRRAL PARTNERSHIP NHS TRUST
------------------------------