1. CJ Lai
  2. PowerBuilder
  3. Wednesday, 19 January 2022 14:12 PM UTC

Hi all

I have a question about the character encode types for (exported) DWObject srd files.

I opened 3 exported SRD files in Notepad++ straight from my application's target. What I noticed is those 3 files are of 2 different character encoding - ANIS and UTF-16 LE BOM.

Does anyone know why there are different encode types of the SRDs? 

How do I ensure that any more DWObjects that are created have the consistent character encoding (UTF-16 LE BOM)?

for those who are curious, I have bullet points in those DWOs but the one that is of ANSI format turns those bullet points into question marks after our final build process (would the build machine play a part in the character's transformation?).

Thank you for your input.

CJ

René Ullrich Accepted Answer Pending Moderation
  1. Wednesday, 19 January 2022 14:43 PM UTC
  2. PowerBuilder
  3. # 1

The question is how you have exported the srd files?

If you use the export function you can specify the encoding.

If the srd files are exported from a new PB IDE by using source control features all should have the same encoding (I think UTF-8 with BOM).

Comment
  1. CJ Lai
  2. Wednesday, 19 January 2022 15:00 PM UTC
Hi René

I did not specifically specify what text encode to export those DWOs as. I straight out exported those DWOs 'as is.' I was hoping those text encodes were truly what those SRDs are of.

If that's not a true statement, I would need to know how I can unify those so that they are consistent and those DWOs will not transform any characters as they are originally intended.
  1. Helpful
There are no comments made yet.
John Fauss Accepted Answer Pending Moderation
  1. Wednesday, 19 January 2022 14:32 PM UTC
  2. PowerBuilder
  3. # 2

Hi, CJ -

When was the DW data object that exports to ANSI last changed/saved? The version info at the top of the exported source file should indicate the PB major version number when the DW was last changed.

DW source does not get changed as a by-product of migrating to a new version of PB... this occurs only when the object is edited and saved.

As a test, copy it to a work PBL/library, make a change to it, save, and export the changed copy and see if it now uses Unicode 16LE encoding.

Comment
  1. CJ Lai
  2. Wednesday, 19 January 2022 14:41 PM UTC
Hi John

The ANSI file has release 17 noted on top of the file. I am not sure if it had been changed and saved back in. It would have been before my time with the application.

I will do the test you recommended and see what happens.

Thank you very much for your input.

CJ
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.