161 compile no longer working

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
User avatar
Lembasts
Posts: 206
Joined: Thu Mar 15, 2012 9:47 am

Re: 161 compile no longer working

Post by Lembasts » Wed Apr 17, 2019 5:31 pm

So I went through and changed all my files to UTF-8 using Version 161.
I opened a project in Version 160 and its saying the encoding is Windows-1252 , not UTF-8????
At this point I would really, really like some advice as to what exactly I should be doing with this encoding business please.

User avatar
davidc
Posts: 5913
Joined: Thu Aug 18, 2011 4:56 am

Re: 161 compile no longer working

Post by davidc » Fri Apr 19, 2019 6:43 am

The v5.6.162 service build is now available and should resolve this issue.
David
SAPIEN Technologies, Inc.

User avatar
davidc
Posts: 5913
Joined: Thu Aug 18, 2011 4:56 am

Re: 161 compile no longer working

Post by davidc » Fri Apr 19, 2019 6:45 am

It is highly recommend to always use UTF-8 with a BOM. That ensures the application knows it is a true UTF-8 file.
David
SAPIEN Technologies, Inc.

User avatar
Lembasts
Posts: 206
Joined: Thu Mar 15, 2012 9:47 am

Re: 161 compile no longer working

Post by Lembasts » Fri Apr 19, 2019 5:04 pm

Thanks heaps!