ANSI Vs: UTF-8 encoding question

Hello all,

We're implementing the Next Generation Tagger GUI on our project. We have multiple metadata-rules configured and the appropriate *.cfg's within the /iw-home/local/config/tagui/rulesets60/ Everything seems to run fine except... the metadata-rules.cfg and their correspoding /tagui/rulesets60/*.cfg must be saved using ANSI encoding instead of UTF-8. The moment we save either file using UTF-8 encoding an error is generated if we attempt to tag a file.

"There was a problem with the metadata capture configuration. Merging rulesets for these files failed: path-to-the-dcr-file. Please contact your system administrator.

TeamSite 6.7.1 SP1, Win2K3, MT4.1.2

I was under the understanding that IWOV recommended UTF-8..
Any thoughts? Anyone else encounter this?

Find more posts tagged with

Comments

srinivasarao

can you post the entire exception stack trace so that it gives more idea to look into this issue?

- Srinivas

Migrateduser

Have you logged a case? I know they are pretty keen on shaking out ng tagui issues.

Keywil

Hey all,

I've been modifying files using Notepad. My colleague pointed out something called 'the bom' (byte order mark). Apparently Notepad will add some invisible characters to the start of a UTF-encoded file called the byte order mark. You can't seem them in notepad but they're there. If you open that same file in Eclipse using its text editor.. there they are.

http://en.wikipedia.org/wiki/Byte_Order_Mark

Removing 'the bom' from the metadata-rules.cfg and taggerGUI.cfg files removed the errors.