Community
Participate
Working Groups
Steps to reproduce 1) create an XML file, and use encoding="gb2312" (or encoding="UTF-16") 2) Observe from the properties view that the encoding is gb2312 3) Add a blank before the equals sign, e.g. encoding ="gb2312" 4) Observe from the properties view that the encoding has been ignored, that the encoding is now the default UTF-8 This is a regression from 3.0.2. The customer that I'm working with, felt that this defect should be a "major" defect, since they have a lot of these files.
This looks like it has been resolved in later releases via Bug 293773.
*** This bug has been marked as a duplicate of bug 293773 ***
We would like this fixed in 3.4.2 if possible for an adopter product.
Created attachment 179241 [details] Fix + test
The fix and test checked in to R3_4_maintenance.