Encoding of dll.xml after install of FSUIPC

[B77X]

The default encoding of the dll.xml is UTF-8 the FSUIPC installer when adding the lines changes the encoding to Windows-1252

[Pete Dowson]

3 hours ago, B77X said:

The default encoding of the dll.xml is UTF-8 the FSUIPC installer when adding the lines changes the encoding to Windows-1252

That isn't true.

Check all the DLL examples in the FSX and P3D SDKs. They are have this first line:

<?xml version="1.0" encoding="Windows-1252"?>

If the file already exists the FSUIPC Installer (FSUIPC4 and FSUIPC5) merely reads the file, as a text file (not XML) and adds its own section then writes it back, as is, with no other change. It doesn't use any sort of XML editor or converter, just normal file I/O. The title line remains as it was when read. It has to!

Perhaps you've been using some other XML editor or installer which is misleading you?

Pete

 

[B77X]

16 hours ago, Pete Dowson said:

That isn't true.

Check all the DLL examples in the FSX and P3D SDKs. They are have this first line:

<?xml version="1.0" encoding="Windows-1252"?>

If the file already exists the FSUIPC Installer (FSUIPC4 and FSUIPC5) merely reads the file, as a text file (not XML) and adds its own section then writes it back, as is, with no other change. It doesn't use any sort of XML editor or converter, just normal file I/O. The title line remains as it was when read. It has to!

Perhaps you've been using some other XML editor or installer which is misleading you?

Pete

 

Did an addon change it? In the programdata the main dll.xml is empty but says

 

<?xml version="1.0" encoding="UTF-8"?>
<SimBase.Document Type="AceXML" version="3,0" id="dll">
    <Descr>AceXML Document</Descr>
    <Filename>dll.xml</Filename>
</SimBase.Document>

The encoding of the dll file in the userdata folder before installing FSUIPC is UTF-8 and after install it is Windows-1252 but I was sure it by default is UTF-8

[Pete Dowson]

4 hours ago, B77X said:

The encoding of the dll file in the userdata folder before installing FSUIPC is UTF-8 and after install it is Windows-1252 but I was sure it by default is UTF-8

Actually, as my colleague Thomas has pointed out, when FSUIPC does need to amend the DLL it will replace that line. And it's line is with 1252 because that has always beem to my knowledge, the default for FSX and L-M.

By all means, please check the Microsoft and L-M examples and defaults supplied in the SDK yourself. I didn't check them all, but all those I did check definitely had 1252. Not that I would know the difference in any case, to be honest. I didn't invent the number 1252, it was just the value I didn't want to change.

Is it a problem in some way?

Pete

 

Edited May 18, 2018 by Pete Dowson
Correction and clarification

[Pete Dowson]

Some examples:

From the P3D3 Traffic Toolbox SDK:

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>dll.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>Traffic Toolbox</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>SDK\Environment SDK\Traffic Toolbox SDK\traffictoolbox.dll</Path>
  </Launch.Addon>
</SimBase.Document>
 

From the P3D SimConnect SDK:
(Meant as the base example to start from for addons like FSUIPC)

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>DLL.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>True</Launch.ManualLoad>
  <Launch.Addon>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Name>Addon DLL</Name>
    <Path>C:\MyPath\Addon.dll</Path>
  </Launch.Addon>
</SimBase.Document>
 

And, to go back a lot longer, from the FSX Traffic Toolbox SDK

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>dll.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>Traffic Toolbox</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
  </Launch.Addon>
</SimBase.Document>

Quite honestly I think the vast majority of users have always had this 1252 setting, right back to 2006! It can't have done them any harm?

Pete

 

 

[Pete Dowson]

2 hours ago, Pete Dowson said:

Some examples:

My colleague Thomas has been hunting for examples where other than 1252 encoding is used in P3D. These are the only UTF-8 ones found so far (also a UTF-16!). Note that none are DLL.XML files:

for P3Dv3
DefaultRecordAndPlayback.xml
DISConfiguration.xml
LWcfg.xml  -->  <?xml version="1.0" encoding="UTF-16"?>
WaterConstantsV3.xml

for P3Dv4
LWcfg.xml
WaterConstants.xml

Thanks Thomas!

Pete