Issue with Accented Characters in v3.1.27 and Windows 8.1

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 LICENSE NUMBERS, ACTIVATION 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.
This topic is 10 years and 3 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
  • Print view
    • User avatar
    oslerhoskinharcourt
    Posts: 1
    Last visit: Tue Sep 16, 2014 12:27 pm

    Issue with Accented Characters in v3.1.27 and Windows 8.1

    Post by oslerhoskinharcourt »

    I have recently upgraded to Windows 8.1 and PowerShell studio v3.1.27.

    I have many scripts that use a select-string which finds accented characters.

    Before upgrading to 8.1 I would open these scripts and see the accented characters correctly. Now when I open them, the characters appear garbled, with diamond characters instead of accents.

    Also, if I make a change to the script (not to the accented characters). Save --> Close --> Run the script. The select-string no longer finds the accented text.

    I have tried all the encoding available, but the text still appears garbled. See the attached.
    Attachments
    French Text
    French Text
    Untitled.png (1.3 KiB) Viewed 1559 times
    Top
    User avatar
    davidc
    Posts: 5913
    Last visit: Mon Jul 08, 2019 8:55 am
    Been upvoted: 2 times

    Re: Issue with Accented Characters in v3.1.27 and Windows 8.

    Post by davidc »

    Please zip and email the script to support@sapien.com, so that we can review it.

    Is this a US machine?

    It is possible that the file was saved as ASCII at one point and lost the original Unicode information.

    David
    David
    SAPIEN Technologies, Inc.
    Top
    This topic is 10 years and 3 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
  • Print view

    • Return to “PowerShell Studio”