#20 Files generated are using an incorrent encoding format.

[Juan Montilla]

Hi, I'm testing this tool and until is now is working ok, but my .pcode files contain "errors" in comments (our developers team usually added comments in spanish).

If I open any .pcode file, words like 'Informática' is displayed as 'Inform�tica' .

I guess this is relating to the encoding used to generate the files, it should be generating using UTF-8.

I'll appreciated your help, thanks.

[Erik H]

As I don't have a way to test my code, it's not so easy for me to code a proper solution, but you may want to try this: add
-Dfile.encoding=UTF-8
to the line in your script in which you start the program (between 'java' and the rest of the line).

Incidentally, I'm always wondering why users want to generate .pcode files: I think the best use of this program is to commit files to SVN or Git.

[Jonathan Rehm]

Regarding why generate .pcode files, I use it to make migrating PeopleCode between environments easier. If a class has some changes that need to go forward and others that need to stay behind, DecodePcode makes it trivial for me to compare. Dump the project out of the two environments and then use Beyond Compare to diff the two. Copy the changes that I want, then copy/paste into App Designer.

So thank you for the awesome tool that makes my workflow possible.

[Juan Montilla]

Hi Erik, thanks for your response... Is working great using this option -Dfile.encoding=UTF-8 .. and in fact we are using your tool to generete a local git repository and automatically push the changes to a remote repository on gitlab, we also tested the ancestor option and it works perfect for us.. In my case, I created a custom script based on yours and I also using gitinspector to generate stats and complement your tool.. thanks you!

[Alexei Tetenov]

Hi Juan,
Can you share what options or commans that you used to do this?
Also, can you share your custom script?
Thanks!