So PL.Net still works in ASCII ?...

Questions about MultiCharts .NET and user contributed studies.
Fabrice
Posts: 182
Joined: 14 Jun 2011
Has thanked: 44 times
Been thanked: 30 times

So PL.Net still works in ASCII ?...

Postby Fabrice » 15 Aug 2013

It would be nice if PL.Net editor would not killed accents and other language-specific characters, putting a mess in our comments... It is really strange that an editor, in 2013, gives the feeling of being working with a 1980's ASCII editor...
Regards.

User avatar
Henry MultiСharts
Posts: 9165
Joined: 25 Aug 2011
Has thanked: 1264 times
Been thanked: 2957 times

Re: So PL.Net still works in ASCII ?...

Postby Henry MultiСharts » 27 Aug 2013

Hello Fabrice,

PowerLanguage .Net editor works ok with language-specific characters. If you have a particular issue - please let us know.

Fabrice
Posts: 182
Joined: 14 Jun 2011
Has thanked: 44 times
Been thanked: 30 times

Re: So PL.Net still works in ASCII ?...

Postby Fabrice » 27 Aug 2013

Hello Henry,
You are right, as long as Import/Export is not used. For a while I have worked on several computers and needed to import/export my studies several times per week. And all the accents (I am French) were crashed. Here is an example :

Comments in the original indicator

Code: Select all

// Mot avec accent : épicéa (spruce)
// Mot avec cedille: français (french)
Then this indicator is exported, deleted and PL.Net Editor is closed. Then PL.Net Editor is opened, and the indicator is imported. And the result is... :

Code: Select all

// Mot avec accent : �pic�a (spruce)
// Mot avec cedille: fran�ais (french)
The "?" diamonds is exactly what is displayed in PL.Net Editor.

Regards.

User avatar
Henry MultiСharts
Posts: 9165
Joined: 25 Aug 2011
Has thanked: 1264 times
Been thanked: 2957 times

Re: So PL.Net still works in ASCII ?...

Postby Henry MultiСharts » 27 Aug 2013

Then this indicator is exported, deleted and PL.Net Editor is closed. Then PL.Net Editor is opened, and the indicator is imported.
On the same PC, without changing any system localization settings?

Fabrice
Posts: 182
Joined: 14 Jun 2011
Has thanked: 44 times
Been thanked: 30 times

Re: So PL.Net still works in ASCII ?...

Postby Fabrice » 27 Aug 2013

Yes. In the example above, both export and import were done on the same machine.

User avatar
Henry MultiСharts
Posts: 9165
Joined: 25 Aug 2011
Has thanked: 1264 times
Been thanked: 2957 times

Re: So PL.Net still works in ASCII ?...

Postby Henry MultiСharts » 28 Aug 2013

Fabrice, I was unable to replicate this situation using Import/Export of the study.
Do you add comments in French via PowerLanguage .Net editor or using any other editor?
What is your system language?

Fabrice
Posts: 182
Joined: 14 Jun 2011
Has thanked: 44 times
Been thanked: 30 times

Re: So PL.Net still works in ASCII ?...

Postby Fabrice » 28 Aug 2013

Hello Henry,
I have just done it again with a new indicator where I just add a comment on the 1st line. Here are the steps :
1. File -> New indicator in PL.Net Editor (PLNE). Compiled then closed (just the indicator - PLNE remains opened).
2. Open Visual Studio 2010 (VS) from PLNE. Open the new indicator and add "// Accentué". Then Ctrl+S. Compilation is ok.
3. Close VS. Save change ? Yes.
4) Back to PLNE. File export -> indicator in a file.
5) Close PLNE
6) Open PLNE -> File Import -> choose the file. PLNE asks to replace the existing indicator ? Yes.
Import is ok.
7) Open indicator with PLNE -> "// Accentu�"

I use only Visual Studio 2010 and PLNE. I have Windows 7 Professional configured to display everything in english (I don't like the french translation).

User avatar
Henry MultiСharts
Posts: 9165
Joined: 25 Aug 2011
Has thanked: 1264 times
Been thanked: 2957 times

Re: So PL.Net still works in ASCII ?...

Postby Henry MultiСharts » 30 Aug 2013

PowerLanguage .Net Editor works with Unicode encoding. Visual Studio saves the file not in Unicode and that causes this problem. Please set the Unicode encoding as the default one in your Visual Studio.


Return to “MultiCharts .NET”