Hello,
when I edit text-files in PSS (such as concept help files, part of a module), the text is written in the system default encoding. On a German computer, that's ANSII. PowerShell however expects UTF8 for most if not all of its works. Sooooooo ...
Would you mind either ...
- Adding an option to allow choosing the Encoding used.
- Simply declare UTF8 as the encoding in use.
This would make writing help quite a bit easier.
Cheers,
Bosparan
P.s.:
To verify this behavior, just import an empty text file into a project on a German OS (or any other language that doesn't use UTF8 by default). Then write some text from within PowerShell Studio into that file. Finally open it in an encoding-aware editor (e.g.: Notepad++) and check the encoding.
P.p.s.:
On that note, let me reiterate my request to create those helpfiles from within PSS
[PSS 2016] Text Encoding
Forum rules
Do not post any licensing information in this forum.
Do not post any licensing information in this forum.
Re: [PSS 2016] Text Encoding
Do you want to change the encoding of an individual file? If so that's already supported, just simply select the encoding in the status bar and it gives you a box of choices:
DevinL
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: [PSS 2016] Text Encoding
Damn, that's been hiding in plain sight if ever a feature has
Thanks for pointing this out, can't believe I've never noticed that before ... probably because it's so rarely been an issue ...
Thanks for pointing this out, can't believe I've never noticed that before ... probably because it's so rarely been an issue ...
Re: [PSS 2016] Text Encoding
Not problem! As always, if you have any further issues, please don't hesitate to post again.
DevinL
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.